When you use the Gpupdate /force command on a Microsoft Windows Server 2003-based domain controller, or you restart a Windows Server 2003-based domain controller, the following error message may be logged in the Application log:
Event Type: Error Event Source: Userenv Event Category: None Event ID: 1053 Date: Date Time: Time User: NT AUTHORITY\SYSTEM Computer: Computername Description: Windows cannot determine the user or computer name. (Not enough storage is available to complete this operation. ). Group Policy processing aborted. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Additionally, if you enable USERENV logging, the following entries may be logged in the Userenv.log file:
USERENV(1b4.eb4) 13:30:54:531 MyGetUserName: GetUserNameEx failed with 14. USERENV(1b4.eb4) 13:30:54:531 MyGetUserName: Retrying call to GetUserNameEx in 1/2 second.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To resolve this problem, add the MaxTokenSize registry entry and the MaxUserPort registry entry on the affected domain controllers. To do this, follow these steps:
Click Start, click Run, type regedit, and then click OK.
Locate and then right-click the following registry subkey: