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 that error, there is some useful information, including an error code. You can find that code near the bottom of the error message:

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 error refers to an expired password for the Domain Admin account 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 defined under Settings>Integrations is locked. You need to unlock this account.

• Error Code 2732: Failed to join the domain while provisioning hosts. This error is related to Windows updates from October 2022 (for details, see KB5020276—Netjoin: Domain join hardening changes). It occurs when a device is joined to a domain by one admin account, and another account attempts to reuse the same host name to rejoin the host to the domain.

  This can typically happen during the AVD host re-imaging process when the domain admin credentials, initially defined in Nerdio Manager, have changed since the time the host was originally created.

  To resolve this issue, remove the computer objects from Domain Services (either AD or Microsoft Entra Domain Services), and then attempt to re-image or replace the host again.

  

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.