Troubleshooting Active directory users and computers mmc console on Entra (Azure AD) Joined devices

I have recently converted my hybrid Azure ad joined device to an Entra joined device (wipe the device and use autopilot) . While most tasks worked seamlessly, I encountered an issue with accessing the Active Directory Users and Computers MMC console.

This blog post outlines the problem and provides a simple solution.

After successfully converting my device to Entra join and ensuring it's connected to the corporate network, I faced an unexpected challenge when trying to access the Active Directory Users and Computers MMC console (you can also use dsa.msc from the run command. RSAT tools must be installed on the device).The Group Policy Management Console (GPMC) was functioning correctly, but attempts to open the MMC for Active Directory users and computers resulted in an error message:

"Naming information cannot be located because the specified domain either does not exist or could not be contacted."

Even though my device was successfully pinging the domain controller (line of sight to DC), the MMC console was refusing to launch.

To resolve this issue, follow the steps below:

1. Accessing Active Directory Users and Computers MMC:
   • Open the Run command (Win + R) and type dsa.msc.
   • Alternatively, launch the MMC console and add the Active Directory Users and Computers snap-in.
2. Error Resolution:
   • Upon encountering the error, in the MMC, right click and choose change domain, type the domain name (e.g., eskonr.com) or the domain controller name (e.g., dc01.eskonr.com) in the provided field.
   • If you try to browse, you will encounter the issue as listed below, instead, type the domain name or domain controller name.
   • Ensure that the setting 'This snap-in will always manage the following object types' is enabled.
3. Verify and Apply:
   • • Click "OK" to apply the changes.
   • Close the console.
4. Relaunch the Console:
   • Reopen the Active Directory Users and Computers MMC console.
   • Confirm that the console now loads correctly without any error messages.

This simple adjustment ensures that the MMC console recognizes the domain and functions as intended. If you encounter any further issues, consider closing and relaunching the console to confirm that the problem has been successfully resolved.

This solution proved effective in my case, and I hope it helps others facing a similar challenge after converting to Entra join on Azure AD.

If you have any additional insights or experiences, feel free to share them in the comments below.