@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.