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

@bogle Ah ok. I don’t know how the cloning would affect the intricacies of a web server. Please feel free to start a new thread if you run into any troubles with the windows imaging later.

@bogle

Solved it…

yum reinstall ca-certificates curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | bash

@bogle No model specific drivers are copied to the target computer during image push and then inserted into the windows environment using pnputil utility.

https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

I probably should update it for 2019 / Win10 specifically, but everything is in there.

I do have MDT add in the WinPE10 standard drivers so the golden image has at least the core network and disk drivers, but most of the windows 10 built in drivers are good enough to get to at least the point where the pnputil program is used.

@bogle said in Newbie getting started:

Do you guys use sysprep in the process of creating your golden image

Yes you need it, if you want to have one image for multiple hardware platforms.

@bogle SSL enabled this time or not? Where did you put the certificates?