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

    FOG Agent on new image PC not communicating with server

    Scheduled Pinned Locked Moved Unsolved FOG Problems
    2 Posts 2 Posters 14 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.
    • rogalskijR
      rogalskij
      last edited by

      Recently upgraded to FOG 1.6, most things working correctly, but trying to get the new Agent to work rather than the legacy client.

      Created a new windows box on brand new hardware, got it where we want it with Windows 11 and software, and installed the 0.1.24 agent. Next approved the agent and host, but the device in FOG is not pinging or gathering any information. Is there something I need to do on the device to make it viewable and read by our FOG server?

      Is there a cooldown waiting period for it to be seen? I have rebooted several times, and added the fog agent to windows firewall. We were going to wait to enroll it for secure boot as that is our next step. Our existing on campus devices show up when we install the agent by itself, what are we missing? Thank you for any guidance you can provide!

      63aa39b7-b193-430a-bece-4e09473e561e-image.png

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

        @rogalskij The host shows the agent enrolled, but it has not checked in since you approved it. On 0.1.24, two things cause that.

        • Audit mode. If this PC is a reference machine in audit mode, or has not finished OOBE, the agent waits on purpose. It does nothing until Windows setup finishes. Check HKLM\SYSTEM\Setup\State\ImageState. Any value other than IMAGE_STATE_COMPLETE means the agent is waiting. It starts by itself after Sysprep and OOBE complete. You can capture the image with the agent in it. On each deployed PC, the agent sees a different hardware identity. It drops the reference machine’s certificate and enrolls as itself.
        • An http:// server address. The server knows the agent only by its client certificate, and that works only over https. With an http:// address, enrollment works, but every check-in after approval fails. Install the 0.1.25 MSI by hand: it switches an http:// address to https:// on its own. Or reinstall with SERVER=https://your-server/fog.

        C:\ProgramData\FOG\fog-agent.log tells you which one it is. “Windows setup has not finished” means the first. “server refused this certificate” means the second. Please post that log if neither line is there.

        Two side notes. The agent opens no listening port, so it needs no firewall rule. The “No such device or address” ping status is the server failing to resolve the host name. It is not related to the agent.

        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
        • 1 / 1
        • First post
          Last post

        21

        Online

        12.8k

        Users

        17.7k

        Topics

        157.5k

        Posts
        Copyright © 2012-2026 FOG Project