Note: This issue appears to correct itself if you wake the machine 3+ minutes before a user logs into the system. Customers have found that waking the systems from standby prior to user interacting with the system has resolved the issue.
This article refers to two Microsoft hotfixes that can solve this issue on Windows XP computers.
When a client wakes from a low power state, the Windows time is incorrect.
The conditions that cause this issue are the same as for Symptoms indicating failed GPO process occur when waking PC device.
It appears that the network is not fully initialized when the user logs on to Windows.
Microsoft has addressed the problem in subsequent Windows versions. It will not be addressed in Windows XP.
For Windows XP, potential solutions include the following hotfixes created by Microsoft.
- A Windows XP based-computer may not synchronize the clock with an Internet time server
Note: Microsoft does not specify whether this hotfix requires a reboot. In addition, this hotfix is included in Windows XP SP3.
- Microsoft Knowledge Base Article 944043
This hotfix requires Windows XP SP2 or SP3. It also requires a reboot to take effect.
Neither solution seems to be related to a specific environment. But the key .dll files that control the system clock are updated, so applying one of them is a recommended first step in solving this issue.
- All Verdiem SURVEYOR versions
- Windows XP Professional