FOG Agent on new image PC not communicating with server
-
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!

-
@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 thanIMAGE_STATE_COMPLETEmeans 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 anhttp://address, enrollment works, but every check-in after approval fails. Install the 0.1.25 MSI by hand: it switches anhttp://address tohttps://on its own. Or reinstall withSERVER=https://your-server/fog.
C:\ProgramData\FOG\fog-agent.logtells 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.
- 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