Event ID 307 and 304 with error code 0x801c001d on Windows 10 device

Event ID 307 and 304 with error code 0x801c001d on Windows 10 device

In today’s publication, we will identify the cause and then suggest possible solutions to the issue Event ID 307 and Event ID 304 with error code 0x801c001d are saved after deploying Windows 10 on a device.

Error code 0x801c001d – Event IDs 307 and 304

When you deploy Windows to a device, the following events are logged:

Log Name: Microsoft Windows User Device Registration / Administrator
Source: User device registration
Event ID: 307
Level: error
The description:
Automatic registration failed. Active Directory failed to find registration service information. Exit code: unknown HResult Error code: 0x801c001d. See http://go.microsoft.com/fwlink/?LinkId=623042

Log Name: Microsoft Windows User Device Registration / Administrator
Source: Microsoft-Windows User Device Registration
Event ID: 304
Level: error
The description:
Automatic registration failed during the join phase. Exit code: unknown HResult Error code: 0x801c001d. Server error:. Debug output: r n not defined.

You will experience this problem because these event IDs 307 and 304 occur when the Active Directory infrastructure is not prepared for Hybrid join. When the device attempts to perform a hybrid join, registration fails and events are recorded.

Typically, organizations with a local footprint rely on imaging methods to provision devices, and Control panel or Group Policy (GP) to manage them.

If your environment has a local AD footprint and you also want to take advantage of the capabilities provided by Azure blue Active Directory, you can implement devices joined to Azure AD Hybrid. These devices are devices joined to your local Active Directory and registered with your Azure Active Directory.

To resolve this issue, Microsoft in a support article points out that these event IDs 307 and 304 can be safely ignored because if the AD infrastructure is in a non-hybrid join environment, these event IDs are expected during Windows 10 deployment.

However, if you encounter this problem in a hybrid join environment, refer to this Microsoft document for troubleshooting steps.

I hope this message guides you in the right direction.

See also:

Leave a Reply