• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Imaging Log for unregistered hosts

    Scheduled Pinned Locked Moved Feature Request
    3 Posts 2 Posters 25 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      DBCountMan
      last edited by

      It seems that currently on Version 1.5.10.1629 FOG only logs imaging activity (deploy and capture) for hosts that are registered. When I go to Reports>Imaging Logs and hit Search I only see activity for registered hosts only.

      In my environment, we don’t register every device that an image deploys to since it is not necessary (we use SCCM for device management).

      Can I modify a setting somewhere that will log imaging for unregistered devices or is this something that must be implemented in a future release?

      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @DBCountMan
        last edited by

        @DBCountMan It’s most likely somethign that might be implemented in a future release, but isn’t really on the focal point.

        Why?

        Basically when imaging log was initially created it was entirely built to be tied to registered hosts, and most likely (at that time) the only way to DO anything imaging wise was purely by registered hosts.

        What might make mroe sense is a separate imaging log that simply tracks ALL imaging tasks but is linked to “images” as images must always be registered. Just my thoughts.

        This is just me spitballing, it is in no way being worked on currently.

        Basically I want to create a new table that would track (similarly) all tasks, regardless of host registered or not, and simply use the MAC address as the linkage of “who”. Not pretty but better than assuming all hosts must also be registered. (Since we did add that feature effectively removing the requirement of Capone Plugin)

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • D
          DBCountMan
          last edited by DBCountMan

          @Tom-Elliott Really for the purposes of user tracking. It is helpful for us to keep track of who is deploying and capturing. This is purely for transparency and accountability. I can instruct my team to always register devices they are imaging but I cannot force it.

          EDIT: Is there a way to force full reg prior to image deployment? Like a prereq for deployment.

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post

          144

          Online

          12.5k

          Users

          17.5k

          Topics

          156.1k

          Posts
          Copyright © 2012-2026 FOG Project