When you upgrade to Windows 2000 Server, or Windows Server 2003, group policies are NOT applied to some users, and the Application event log contains:

Source: Userenv
Category: None
Type: Error
Event ID: 1053
Description: Windows cannot determine the user or computer name. (No mapping between account names and security IDs was done). Group Policy processing aborted.

Event Type: Error
Event Source: Userenv
Event ID: 1058
User: NT AUTHORITY\SYSTEM
Description: Windows cannot access the file gpt.ini for GPO <CN=\{31B2F340-016D-11D2-945F-00C04FB984F9\},CN=Policies,CN=System,DC=lcds,DC=lab> <The file must be present at the location>\\server name\Policies\\{31B2F340-016D-11D2-945F-00C04FB984F9\} (Access is denied). Group Policy processing aborted.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
User: N/A
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.


When you upgrade to Active Directory, some user accounts are renamed.

This behavior occurs because, unlike Windows NT 4.0, Windows 2000 Server and Windows Server 2003 DO NOT distinguish between non-ASCII and ASCII characters in account names, so account names with non-ASCII characters, like ö and é are treated as if they contain o and e, causing possible duplication.

The only workaround is to rename, or delete, the conflicting accounts.