Azure/OpenShift

Enter connection information for your on-premise directory or forests: Azure AD connect unable to connect directory, forest not available

This error was prompted when I wanted to install Azure AD connect on another server for high availability, should in case one of the servers the agent is running on fails, we can as well have access to our applications. But this was not possible due to domain related errors as I will be discussing below.

Let’s simulate the error! As you can see below, if everything is working correctly with the domain, the forest should appear by default and all you need to do is click on Add Directory as shown below.

Let me manually inout the domain name (forest) as shown below. This will also fail because the root issue has not been fixed yet.

Now you will be requested to enter your credentials.
Note: You cannot use your Enterprise or Domain administrator account for your AD Forest account. It is recommended to let Azure AD Connect or you can specify a synchronisation account with the correct permission.
– I will be using an existing account I have in AD.
– Click on “OK” as shown below

This will run and try to validate the forest credentials but will fail as shown below. This is the error!

Without this, you cannot proceed as the option to continue is greyed out. This Error is as a result of the following domain issues below.

To fix this issue, simply remove the device from the domain and have it joined to the domain again.
-Note: From experience, This might not be the desired fix for your own scenrio, but further troubleshooting you might be able to resolve this issue.

See the following articles below for similar fixes on how to remove the device and have it joined to the domain
– How to join a computer (PC) to the Domain.
-Error: An Active Directory could not be contacted / Cannot find domain: Non-existent domain.
-See post OS installation for more details https://techdirectarchive.com/2020/03/19/post-os-installation-configure-windows-server-2019-properties/
– We can’t sign you with this credential because your domain isn’t available – Why Can’t I Connect with a 169.254 IP Address?

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

Buy me a coffeeBuy me a coffee

Advertisements
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x