Problems deploying/managing new windows host...
-
@george1421 Ok I got that correct.
-
@bogle So from the linux command prompt on your FOG server can you ping the devices by their windows host names? Not the FQDN name?
-
@george1421 yes
-
@bogle Even though windows firewall was disabled for domain, I added fog client to exclusion list for all network profiles, then opened inbound/outbound traffic on port 445. Can see the newly deployed computer now.
I had to do a “reset this pc” after deployment to fix make the computer run right though…
-
@bogle I did a “reset this pc” and can see the host online. I created a task to reboot the computer and it didn’t do anything.
-
@bogle The FOG server talks to the target computer via the FOG Client/service. That service has a check in interval that is set in the fog settings. So the default may be 5 minutes (300 seconds), so if you issue a task to the target computer it could take up to 5 minutes before the target system reacts.
Also on the fog up/down indicator it doesn’t use a ping, but a connect to port 445 to confirm the system is up or not. If your windows firewall is blocking connections to port 445 then fog will assume its down.
