Troubleshoot AD Join and Install AD Extension Error

Troubleshoot AD Join and Install AD Extension Error

When adding a host, Azure Files, or a server, you may encounter an error during the task. You can find the details of this task by selecting Details in the Nerdio Manager 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:

Within this error is some very useful information, including an error code. You can find this code near the bottom of the error message:

These error codes are not specific to Nerdio Manager nor Azure/AVD. They are Windows-based errors. Please see this Microsoft document for details.

Common Errors and Resolutions

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

  • Error Code 2242: This refers to an expired password for the Domain Admin account being used. You want to update the password for your domain admin account and update this in Nerdio Manager under Settings>Integrations and selecting the directory.

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

  • Error Code 1326: The password is incorrect for the Domain Admin account designated in Settings>Integrations for the directory in Nerdio Manager.

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

Cleanup of a Failed Attempt to Add a Host

If an AD Join error occurred, you can see a cleanup option available in Nerdio Manager. Selecting Cleanup attempts to remove any remnants of this failed attempt:

If you find an "orphaned" VM with an "AVD Session Host Not Found" message in your host pool, you should delete this VM with the option below selected. This skips the un-join process from AD, as this will likely run into an issue again if the AD Join failed initially:

If further support is needed with errors related to AD Join, please reach out to our support team at nmm.support@getnerdio.com.

Was this article helpful?

1 out of 1 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Article is closed for comments.