Jawloms Posted June 19, 2019 Posted June 19, 2019 Most of our Windows 10 devices (some running LTSC 1809 and some running Edu 1709) gain an hour every now and then. As far as I can tell it only occurs on a reboot, but not at every reboot. The bigger problem is that after a couple of weeks the PC has obviously been booted a number of times so is several hours out, throwing out Impero logs etc. None of my Windows 7 devices do this and seem to quite happily pick up their time from the DC. Any thoughts, or anyone else getting this? Thank you Stuart
Jawloms Posted June 19, 2019 Author Posted June 19, 2019 Timezone? Can students change it themselves? Timezone is correct, and no they can't. Even the staff can't! It's the fact it increments slowly over time that gets me. It doesn't suddenly become 8 hours out, it will be one hour, then two, then three.......
jthompson Posted June 19, 2019 Posted June 19, 2019 How old are the systems having the problem? Could it be their clock batteries going flat? If they're habitually switched off at the mains, the battery will become flat more soonly. I'd check the time source on an affected system: w32tm /query /source I believe that should return one of your DCs. Restarting the Windows Time service should set Windows on a path to bringing its clock back in line with the rest of the domain over the course of the next hour or so.
Jawloms Posted June 19, 2019 Author Posted June 19, 2019 dc giving out the wrong time perhaps? Presumably not as it varies on different machines as to how far out they are, and not all machines are wrong. How old are the systems having the problem? Could it be their clock batteries going flat? If they're habitually switched off at the mains, the battery will become flat more soonly. Some are brand new, oldest affected are only a couple of years. Some are laptops which are permanently kept charged in their trolleys. I'd check the time source on an affected system: w32tm /query /source I'll give that a go, thanks. I believe that should return one of your DCs. Restarting the Windows Time service should set Windows on a path to bringing its clock back in line with the rest of the domain over the course of the next hour or so. Shouldn't restarting the machine do that too as it's effectively restarting the service? Happy to be told 'not the case'. Stuart
howartp Posted June 19, 2019 Posted June 19, 2019 Have a look in Event Viewer. The most recent "Time Service" entry should say "...now receiving valid data from .... " I have this script which I run if I find a PC/server not behaving: @echo off echo Setting NTP source to 192.168.3.30... w32tm /config /syncfromflags:manual /manualpeerlist:192.168.3.30 /update net stop w32time && net start w32time w32tm /resync 1
bald_pig Posted June 19, 2019 Posted June 19, 2019 How old are the systems having the problem? Could it be their clock batteries going flat? If they're habitually switched off at the mains, the battery will become flat more soonly. I'd check the time source on an affected system: w32tm /query /source I believe that should return one of your DCs. Restarting the Windows Time service should set Windows on a path to bringing its clock back in line with the rest of the domain over the course of the next hour or so. That's the command I was trying to think of! Are the machines exactly x hours out? ie not 37 minutes or 154 minutes etc. keep checking the time source of the machines, and check some that are good as well, see if there's any links to be made. 1
Jawloms Posted June 19, 2019 Author Posted June 19, 2019 That's the command I was trying to think of! Are the machines exactly x hours out? ie not 37 minutes or 154 minutes etc. keep checking the time source of the machines, and check some that are good as well, see if there's any links to be made. They are virtually on the hour, just a couple of minutes off. Do you have multiple DC's or just one? Two, both have the correct time.
bald_pig Posted June 19, 2019 Posted June 19, 2019 They are virtually on the hour, just a couple of minutes off. Two, both have the correct time. Do they both have the same timezone as well? stab in the dark thought.
Jawloms Posted June 19, 2019 Author Posted June 19, 2019 Do they both have the same timezone as well? stab in the dark thought. Yarp..
RLR Posted June 19, 2019 Posted June 19, 2019 I had this with some Macs. I think it was something to do with them using UTC timezone instead of GMT?
TechMonkey Posted June 19, 2019 Posted June 19, 2019 Another out there idea, the "set time zone automatically" option isn't on is it? Could be some weird geolocation going on and W10 changing it's clock accordingly? Is SNTP set up properly? Maybe the PCs aren't looking at your DCs to pick up the time?
mavhc Posted June 19, 2019 Posted June 19, 2019 Gaining 1 hour on reboot sounds like you're saving local time to BIOS, but reading it as UTC. https://superuser.com/questions/975717/does-windows-10-support-utc-as-bios-time
Jawloms Posted June 21, 2019 Author Posted June 21, 2019 I'd check the time source on an affected system: w32tm /query /source I ran this it said the time service wasn't running!! I think I may have found the issue........... Thanks for eveyones input.
chazzy2501 Posted June 21, 2019 Posted June 21, 2019 basic things I remember, set the PDC to use an external NTP source, (I use the RM one ntp.swgfl.ifl.net) but there are others especially do this if you use a VM (as they can't keep time). You can specify a time server in DHCP option 42, this is nice if you haven't domained a PC (and other non-MS devices)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now