Windows 10 clock is always off after imaging
-
Is there a way to update the clock on windows 10 machine with FOG server remotely?
-
We recently had an issue where the time zone wasn’t being set correctly/updating on imaged machines. We edited the registry with a script on those machines to set the correct time zone.
-
@tesparza said in Windows 10 clock is always off after imaging:
Is there a way to update the clock on windows 10 machine with FOG server remotely?
If it is the clock being off an hour, I had a similar issue which I fixed through my unattend script. It would automatically disable daylight savings time which would set it an hour back. Once I fixed that, my time is correct on each image.
-
You may need to explain this a bit more since the windows clock is set by the hardware clock on the workstation. Is it off by minutes or hours such as the time zone not being set correctly (still not a fog issue). Domain members should have their time sync’d to your AD domain controller because users will not be able to login to the domain if the time between the DC and the workstation is off more than by 5 minutes.
Now, I can say that you can sync your DC with the FOG server, or the other way around if you want to harmonize all of the computer clocks.
