Question regarding the new Fog Agent (FOG 1.6.x) prior to syspreppping
-
We are using VMWare Workstation Pro 26H1u1 to create VM’s for upload to our FOG servers. We’ve upgraded one of our FOG servers to v1.6.x, and on the image we have removed the old FOG client and installed the FOG agent. Prior to sysprepping the image, do I need to stop and disable the FOG Agent like we needed to do on with the old FOG client? (The client on the old image was restarted using SetupComplete.cmd in C:\Windows\Setup\Scripts using the command “sc config FOGService start= delayed-auto”). If the agent service does needs to be stopped and disabled I would need to change the command to “sc config fog-agent start= delayed-auto”, correct?
Lastly, do I need to make a firewall exception for the agent, i.e. "netsh advfirewall firewall add rule name=“Fog Agent” dir=in action=all program=“C:\Program Files\FOG\fog-agent.exe”, in the C:\Windows\Setup\Scripts\SetuComplete.cmd file?
Thanks for the great support as usual guys! -
@JYost With agent 0.1.23 or later, you do not need to stop or disable it before Sysprep, and you do not need the SetupComplete.cmd line. The agent waits until Windows setup has finished before it enrolls, checks in, or reboots. It starts on its own after OOBE completes.
On an older agent, update it on the reference machine first. Or use the same steps as before with the new service name:
sc config fog-agent start= disabledbefore Sysprep, thensc config fog-agent start= delayed-autoandsc start fog-agentin SetupComplete.cmd.You also do not need to clear the agent’s key before capture. Each deployed machine has different firmware IDs, so the agent drops the captured key and enrolls as itself. A deploy from your server approves it automatically.
No firewall rule is needed. The agent opens no listening port. It only connects out to the FOG server over HTTPS.
