The Event ID 304 in the Microsoft-Windows-User Device Registration/Admin log on a Windows Server, as shown in the provided text, indicates that automatic device registration failed during the join phase.
Let's break down the information in the event log:
- Log Name: Microsoft-Windows-User Device Registration/Admin - This clearly identifies the area where the error occurred, which is related to the process of registering devices with the system.
- Source: Microsoft-Windows-User Device Registration - The specific component within Windows responsible for this event.
- Date: 13/05/2025 11:31:03 - The exact timestamp when the error occurred (which aligns with today's date as per your prompt).
- Event ID: 304 - The unique identifier for this specific type of event, indicating a failure in automatic registration during the join phase.
- Task Category: None - No specific sub-category is assigned to this event.
- Level: Error - This clearly indicates a problem occurred.
- Keywords: - No specific keywords are associated with this event in this log entry.
- User: SYSTEM - The operation was attempted under the context of the system account.
- Computer: rdserv.domain.local - The hostname of the server where this error occurred. This suggests the server might be related to Remote Desktop Services (RDS) given the "rdserv" prefix, although it's not definitive.
- Description: Automatic registration failed at join phase.
- Exit code: Unknown HResult Error code: 0x801c001d - This is a crucial piece of information. The HResult error code 0x801c001d typically translates to "The device is not enrolled into mobile device management." This suggests the device or the user context attempting registration is not properly enrolled or configured for Mobile Device Management (MDM).
- Server error: (empty) - No specific server-side error message is provided in this log entry.
- Tenant type: undefined - The type of the Azure AD tenant or organizational context is not identified.
- Registration type: undefined - The specific method of registration being attempted is not specified.
- Debug Output: This section provides more granular details about the registration attempt:
- joinMode: Join - Indicates the device was attempting to join something (likely Azure AD or a workplace join).
- drsInstance: undefined - The Device Registration Service instance is not identified.
- registrationType: undefined - Again, the specific type of registration is not defined.
- tenantType: undefined - The tenant type remains undefined.
- tenantId: undefined - The unique identifier of the Azure AD tenant is missing.
- configLocation: undefined - The location of the configuration settings being used for registration is not specified.
- errorPhase: discover - The failure occurred during the discovery phase, which is usually the initial step where the device tries to locate the registration service.
- adalCorrelationId: undefined - A correlation ID for Azure Active Directory Authentication Library (ADAL) is not present. ADAL is often used for authentication and authorization.
- adalLog: undefined - No specific ADAL logs are available in this entry.
- adalResponseCode: 0x0 - The response code from ADAL is 0, which usually indicates success at that specific stage, but the overall registration failed later.
- Event Xml: This is the raw XML representation of the event log data.
In summary, Event ID 304 indicates a failure during the automatic device registration process, specifically at the "join phase." The error code 0x801c001d strongly suggests that the device or user attempting registration is not properly enrolled or recognized by the Mobile Device Management (MDM) system.
Possible Causes and Troubleshooting Steps:
Based on this information, here are some potential causes and troubleshooting steps you might consider:
- Device Not Enrolled in MDM: The most likely cause is that the device attempting to join is not properly enrolled in the organization's Mobile Device Management (MDM) solution (e.g., Microsoft Intune). Ensure the device has gone through the enrollment process.
- Incorrect MDM Configuration: Verify the MDM settings and policies are correctly configured within your organization's MDM platform.
- Azure AD Join Issues: If the "joinMode: Join" refers to Azure AD Join or Hybrid Azure AD Join, there might be issues with the Azure AD Connect configuration, synchronization, or the device's ability to communicate with Azure AD.
- Workplace Join Issues: If it's a Workplace Join attempt, ensure that Workplace Join is enabled and properly configured in your Active Directory Federation Services (AD FS) or Azure AD.
- Network Connectivity Problems: While the error points to an enrollment issue, basic network connectivity problems could prevent the device from reaching the registration service.
- Time Synchronization Issues: Ensure the server's time is synchronized with a reliable time source, as time discrepancies can sometimes cause authentication and registration failures.
- User Permissions: Verify that the user attempting the registration has the necessary permissions to enroll devices.
- Firewall or Proxy Issues: Check if any firewalls or proxy servers are blocking communication between the device and the device registration service endpoints.
To resolve this issue, you would typically need to investigate the MDM enrollment status of the device and the configuration of your MDM solution and Azure AD (if applicable). Examining the device itself for any enrollment errors might also be necessary.
