Windows Server

Error code 0x801c001d: Automatic registration failed, failed to look up the registration service information from Active Directory with exit code unknown HResult

Microsoft’s identity solutions span across on-premises and cloud-based capabilities. These solutions create a common user identity for authentication and authorization to all resources, regardless of location. This is referred to as a “hybrid identity”. With hybrid identity to Azure AD and hybrid identity management, these scenarios become possible.

Here are some contents that I have written relating to Pass-Through Authentication: Azure Active Directory integration with on-Premise AD using PTA, Pass-Through Authentication Authentication and Active Directory Federation Services (PTA/ ADFS): VM environment setup on Hyper-V for Windows Server Active Directory, Azure Active Directory Integration, Pass-Through Authentication: AD Connect Tool status displays inactive, and “Pass-Through Authentication sign-in issue, non-routable domain, Invalid username and password for Single Sign-On“.

To achieve hybrid identity with Azure AD, one of three authentication methods can be used, depending on your scenarios. The three methods are:
– Password hash synchronization (PHS)
– Pass-through authentication (PTA)
– Federation (AD FS)

When prompted with the following error as shown in the figure below "Automatic registration failed. Failed to lookup the registration service information from Active Directory. Exit code: Unknown HResult Error code: 0x801c001d. See"

This error occurs when the infrastructure is not prepared for Hybrid join. When the device tries to do Hybrid join, the registration fails, and the events are logged.
– Therefore, the Automatic Device Join runs as a scheduled task whenever someone logs into a server. This can cause a lot of event errors as shown below.

Here is a suggestion:
- You can disable the task from Task Scheduler as it is just basically for Azure AD device join, but this may not work!

Or basically, if the infrastructure is in a non-Hybrid join environment, these event IDs are expected during Windows 10 deployment. They can be ignored! So they are therefore ignored by me. 🙂

If you have a Hybrid environment and you wish to fix this issue, kindly visit this link.

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Notify of
Inline Feedbacks
View all comments
j. Sleuth
j. Sleuth
2 months ago

Defining what a hybrid join is would greatly improve this pose.

Would love your thoughts, please comment.x