| Event Id | 1053 |
| Source | Userenv |
| Description | Windows cannot determine the user or computer name. (%1). Group Policy processing aborted. |
| Event Information | Explanation : A network connectivity or configuration problem exists. Group Policy settings cannot be applied until the problem is fixed. User Action : To troubleshoot the network connectivity or configuration problem, try one or all of the following: In Event Viewer, click System, and check for any networking-related messages, such as Netlogon messages, that indicate a network connectivity issue. At the command prompt, type netdiag, and note any errors. Those errors usually have to be resolved before Group Policy processing can continue. At the command prompt, type gpupdate, and then check Event Viewer to see if the Userenv 1053 event is logged again. To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where mydomain.com is the fully qualified DNS name of your domain. Verify that you can access the domain controller by using tools such as the Active Directory Users and Computers snap-in. Check to see whether other computers on your network are having the same problem. If this computer is a part of a cross-forest domain, verify that the forest for the user account is currently available and can be contacted by the computer on which the Group Policy processing failed. |
| Reference Links | More Information How to troubleshoot RPC Endpoint Mapper errors Event ID 1053 and 1058 appear in the Application log after you upgrade to Windows 2000 Server or Windows Server 2003 with Active Directory Information From Chicagotech.com |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.