Operating system

 

Windows Server 2003

 

Problem

 

When we resume the computer from standby mode, the computer may stop responding. Sometimes it may also see the "Applying Personal Settings" message box for up to an hour before the desktop appears.
Typically, when you resume a Windows Server 2003-based computer from standby, the computer is locked. Therefore, you must log on to the computer before you can access the desktop. However, when this problem occurs, the computer is not locked, and the Windows Server 2003 logon screen does not appear.

 

Solution

 

We found the following event messages may be logged in the application event log on the domain controller after restart the Windows Server 2003-based computer:

Event Type: Error 
Event Source: Userenv 
Event Category: None 
Event ID: 1058 
Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=com. The file must be present at the location <\\domain\sysvol\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Access is denied. ). Group Policy processing aborted. For more information, see Help and Support Center at http://support.microsoft.com.
 
or
Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=com. The file must be present at the location <\\domain\sysvol\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (The network path was not found. ).

Event Type: Error 
Event Source: Userenv 
Event Category: None 
Event ID: 1030 
Description: Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine. For more information, see Help and Support Center at http://support.microsoft.com.

When we turn on user environment (Userenv) logging, domain Distributed File System (DFS) services may not work after the computer resumes from standby. Additionally, you may receive messages that resemble the following messages in the %SystemRoot%\Debug\UserMode\Userenv.log file.
According to Microsoft this problem may occur if the Winlogon process tries to process group policies before other components are running. However, there are several other scenarios that may cause this problem. Make sure that the following components are started and that they are configured correctly Netlogon and DFS services are started.

  • Domain controllers have the read and apply rights to the Domain Controllers Policy.
  • NTFS file system permissions and share permissions are set correctly on the Sysvol share.
  • DNS entries are correct for the domain controllers.

 

Method 1

 

Microsoft released one Fix Microsoft Fix it 50615 for the above problem. The download link available from the below

http://go.microsoft.com/?linkid=9763079

 

Method 2

 

Update latest Service Pack for the server operating system.

 

Method 3

 

Open the registry editor and locate the below path

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Create the DWORD value If the WaitForNetwork, if the value is not exists. Set the value to 1.

Close the registry editor and restart the computer