Submit a request

Nerdio Help Center

AD Join and Install AD Extension Error Troubleshooting

Applies to: Nerdio Manager for MSP (NMM)

During a host, Azure Files or server add in Nerdio Manager for MSP (NMM) you may run into an error during the task.  You can find the details of this task by clicking "Details" in the NMM logs:


In these details, you may see an error that looks like this regarding the "Join AD", "Join VM to AD" or "Install AD Extension" step:


Obtaining the Error Code

Within this error is some very good information, including an error code.  You'll find this code near the bottom of the error message:
These error codes are not specific to NMM nor Azure/AVD, and are Windows-based errors.  You can find details in Microsoft documentation on these errors  HERE.

Common Errors and Resolutions

Error Code 1355: This error indicates the domain controller could not be contacted.   You'll want to ensure your domain controller is up and running and accessible.  If running and accessible, you'll want to ensure your vNET in which the host is being added to is pointing to the Domain Controller IP.  If this is after an account has been added in NMM, you can adjust this via the NMM portal:

Error Code 2242: This refers to an expired password for the Domain Admin account being used.   You'll want to update the password for your domain admin account and update this in NMM under Settings>Inegrations and clicking on the directory.

Error Code 1332: This error is typically associated with an incorrect username/domain for the Domain Admin account under Settings>Inegrations for the directory in NMM.

Error Code 1326: The password is incorrect for the Domain Admin account designated in Settings>Integrations in NMM.  

Error Code 1909:  The Domain Admin account designated under Settings>Integrations is locked.  You'll want to unlock this account.

Cleanup of a Failed Attempt to Add a Host

You will see a cleanup option available in NMM if an AD Join error occurs.  Clicking this will attempt to remove any remnants of this failed attempt:

If you do find an "orphaned" VM with an "AVD Session Host Not Found" message in your hostpool, you'll want to delete this VM with the option below checked.  This will skip the disjoin process from AD, as this will likely run into an issue again if the AD Join failed initially:

If any further support is needed with errors related to AD Join, please reach out to our support team at  Thank you!!
Was this article helpful?
0 out of 0 found this helpful
Important Notification for NFA Partners Only
  • Microsoft is sunsetting Azure Classic (not Azure Virtual Desktop (AVD)) - Microsoft Article
  • NFA sunset occurs February 20th, 2023
  • NFA will be fully supported until the official sunset -


Please sign in to leave a comment.