Windows XP time keep changing after reboot

  • Thread starter Thread starter Q
  • Start date Start date
Q

Q

Hi there,

We have 90 classroom computers, half of them just had their image updated
using Ghost. The updated computers are having an issue with the clock being
set back 3 hours before local time every time a reboot occurs. When you log
in you can actually see the time update it's self in about 15 to 30 sec. If
you set the clock and reboot, you are back to incorrect settings for about 30
sec before it syncs with the DC. This is giving us errors saying it can't
find the machine account, the clock on the client and server machines are
skewed.

The main issue is that "Deepfreeze" doesn't let go of its maintenance period
until 3 hours after it is due out, leading to unusable classroom computers.

* Bios clock displays the correct time.
* Windows xp (with all updates) has the correct time zone and it is being
synced with the DC.
* A fresh base image install reports correct time, so it isn't a battery issue
* HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
has the type set to NT5DS

I'm not sure where else to look, what is setting the clock back 3 hours
before local time? Anyone have any ideas?

Thanks
Quinton
 
Can you be more specific? As I stated, the timezone is set correctly (In the
Date and Time Properties)
 
Move the machine out of its time zone into another zone and click on
Apply & OK. Then move the machine back into its time zone. Does the
problem persist?

If yes compare the values and data at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

Is the information identical for both the good and not good machines?
All the values and data should be *identical* .

John
 
The Ghost Image may have the flaw with the time zone.

If you have a PC that works perfectly then:
1) Ghost it and save the image.
2) Then use the Ghost image that you rolled out to the system
that have the time zone issue to the known good PC.
3) Now see if the problem occurs,
if it does then you know the Ghost image is the problem.

You can always restore the test PC using the backup you
made in step #1.
 
Hi there,

We have 90 classroom computers, half of them just had their image
updated using Ghost. The updated computers are having an issue
with the clock being set back 3 hours before local time every time
a reboot occurs. When you log in you can actually see the time
update it's self in about 15 to 30 sec. If you set the clock and
reboot, you are back to incorrect settings for about 30 sec before
it syncs with the DC. This is giving us errors saying it can't
find the machine account, the clock on the client and server
machines are skewed.

The main issue is that "Deepfreeze" doesn't let go of its
maintenance period until 3 hours after it is due out, leading to
unusable classroom computers.

* Bios clock displays the correct time.
* Windows xp (with all updates) has the correct time zone and it
is being synced with the DC.
* A fresh base image install reports correct time, so it isn't a
battery issue *
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parame
ters has the type set to NT5DS

I'm not sure where else to look, what is setting the clock back 3
hours before local time? Anyone have any ideas?

Thanks
Quinton
Click to expand...

IMHO, the first step is to see if something external on the network is
providing this erroneous time. Try disconnecting the network cable,
set the time correctly, then try a reboot and see if this problem is
still there.

If Windows Time is changing the time by as much as 3 hours, then you
will see an entry in the System Event Log noting the discrepancy and
pointing to the source of the time. Check your System Logs...
Start->Run->eventvwr.msc

Do you have Netware installed? ... It just loves to time-sync with
just any old server out there. Also, check for other applications that
might try to time-sync at startup.

HTH,
John
 
John John, Thanks for the tip. I compared the values in the good image and
bad image and came across this value
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\ -
realtimeisuniversal) I removed realtimeisuniversal and everything is working
as it should be now.

I've talked with my co-workers and no one knows how it got there.
Once again thanks for your tip.

Regards
Quinton
 
Q said:
John John, Thanks for the tip. I compared the values in the good image and
bad image and came across this value
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\
-
realtimeisuniversal) I removed realtimeisuniversal and everything is
working
as it should be now.

I've talked with my co-workers and no one knows how it got there.
Once again thanks for your tip.
Click to expand...

That registry key fixes a bug in Windows Vista that is sems to be the
reverse of the problem that you have. It should not be present on an XP
machine.
 
Back
Top