Overview
This article describes how to address the symptoms that suggest that while a computer wakes from a low power state, the Group Policy object (GPO) is not applied and an event error ID 1054 occurs.
When a user wakes a Windows XP-based computer from a low power state and logs on to Windows, symptoms such as the following occur.
- Mapped drives do not connect, or they lose their connection shortly after establishing them.
- The Windows system clock does not display the correct time.
- Active Desktop background does not appear when applied with a Group Policy object (GPO).
- GPOs do not apply to the computer in other ways. Symptoms reported by the users can vary depending on the GPO.
When you view the event logs, you will see the following event.
| Event ID | 1054 |
| Source | Userenv |
| Type | Error |
| Description |
Windows cannot obtain the domain controller name for your computer network. (A socket operation was attempted to an unreachable host.) Group Policy processing aborted. |
You may also see errors related to the Network Time Protocol (NTP) or Win32Time services, other Userenv errors, or Group Policy failure entries.
Conditions
These issues can occur only if all of the following conditions are met.
- The computer's operating system is Windows XP (so far the issue has not been related to a particular hotfix or service pack).
- The PC is a member of a domain.
- The PC has been in standby for over one hour. Most users report this issue when logging on at the start of their workday.
- The PC is set so that the user is required to log on when resuming from standby.
- When presented with the Windows XP login screen, the user must log on right away. If the user waits over 10 seconds, the issue will not occur. In testing, the typical threshold is 8 seconds.
Environment
Product
- All Surveyor versions
Operating system
- Windows XP
Root Cause
As implied in the event log descriptions, it appears that the network card is not fully initialized when the user logs on to Windows.
Resolution
Microsoft has addressed the problem in subsequent Windows versions. It will not be addressed in Windows XP.
There is no definite solution that exists for Windows XP. However, in most cases, we have been successful working around it by modifying the registry setting, GpNetworkStartTimeoutPolicyValue.
Some customers have also found that disabling the Windows XP Professional Fast Logon Optimization feature resolved the issue.
Important: As always, modify the registry with caution and make sure to back it up before you make any changes.
Comments
0 comments
Article is closed for comments.