Time Sync Issues - Windows 10 Edu Clients

[SimonInOz]

Hi,

 

I have an issue with 'some' W10 Edu clients (v1803) losing time sync with the domain. (Surface Pro 5th Gen)

 

In some cases, hours are gained or lost. A bit mystified, as this would be about half a dozen clients at most, but reasonably regular in occurrence.

 

Any pointers on troubleshooting this? Our NTP setup I believe is fine, and I have no other issues with time other than this one.

 

A problem in lots of ways, but mostly as Group Policy doesn't apply, etc.

 

Help?

 

PS. Timezone settings are correct

Edited September 12, 2019 by SimonInOz

[jthompson]

If it's hours being gained or lost but not minutes, that would suggest that the timezone settings are different.

[SimonInOz]

Hi, no it is not the timezone. It is correct.

[jthompson]

Is it the same clients each time, and do they self-correct after long enough?

 

The only thing that springs to mind is to check the time source on an affected system and see if it differs from what you're expecting.

w32tm /query /source

[Jawloms]

We had exactly this. We ran w32tm /unegister, and then w32tm /register from an elevated command prompt. Solved it.

 

Stuart

[Davit2005]

In a domain environment Windows clients by default should pick up time from the PDC emulator which is a role one of the DCs should hold.

[Jawloms]

In a domain environment Windows clients by default should pick up time from the PDC emulator which is a role one of the DCs should hold.

 

Yup, ours didn't. I still haven't figured out why but it is set properly before we sysprep, and then isn't after we download the image.

 

Stuart

[Michael]

If you have a Hyper-V setup, there's a Time Synchronization option which will override the PDC.

[SimonInOz]

In a domain environment Windows clients by default should pick up time from the PDC emulator which is a role one of the DCs should hold.

 

Yes, as I said the time setup is pretty regular. Not my first domain (netdom /query fsmo and w32tm /config /reliable:yes)

 

- - - Updated - - -

 

Is it the same clients each time, and do they self-correct after long enough?

 

The only thing that springs to mind is to check the time source on an affected system and see if it differs from what you're expecting.

 

Thanks, no different hardware, just random really. We have a stock of around 350 surface pro devices, all new. Yes, using w32tm regularly.

[SimonInOz]

We had exactly this. We ran w32tm /unegister, and then w32tm /register from an elevated command prompt. Solved it.

 

Stuart

Thanks, yes, I do know how to solve it, just trying to work out why

[SimonInOz]

If you have a Hyper-V setup, there's a Time Synchronization option which will override the PDC.

 

VMWare, I know how to fix the issue, just not sure of the cause. Cheers

[SimonInOz]

In a domain environment Windows clients by default should pick up time from the PDC emulator which is a role one of the DCs should hold.

 

Yes, the mystifying part of it all. I guess the time loss/gain is too much to pick up through increments.