Forum Discussion
Domain Join Error while deploying HostPool
MicrosoftThe VM's in the host pool must be Standard domain-joined or Hybrid AD-joined. Virtual machines can't be Azure AD-joined (in the future, AAD joined will be supported). You will need to either deploy or use an existing Domain Controller, or leverage the Azure Active Directory Domain Services (AADDS, not to be confused with AAD) in order to do a Standard domain-join.
Please review the requirements for WVD:
https://docs.microsoft.com/en-us/azure/virtual-desktop/overview#requirements
To learn more about the different identity solutions used with WVD:
https://docs.microsoft.com/en-us/azure/active-directory-domain-services/compare-identity-solutions
-Jeff
Sometimes its working fine as i tried to deployed it yesterday and it got executed successfully, But again i am getting the same error related to domain join. Is there any restriction for the azure test account which is causing the issue.
Regards,
Pratik
Attaching error for you reference once again.
Error: Code="VMExtensionProvisioningError" Message="VM has reported a failure when processing extension 'testext'. Error message: \"Exception(s) occured while joining Domain 'rupni.onmicrosoft.com'\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/vmextensionwindowstroubleshoot "
on virtual_machine_extensions.tf line 1, in resource "azurerm_virtual_machine_extension" "domainJoin":
1: resource "azurerm_virtual_machine_extension" "domainJoin" {- Jeff_Bryant
1. Did you deploy AADDS or did you create a VM to be your DC?
2. Are you specifying the domain name and/or OU in the host pool template? This is an optional step, but if the information entered is not correct, the domain join extension can fail even though you have confirmed the user account and password is correct.
3. Is the host pool VM on the same subnet as where the ADDS/DC is running?
3. Are you able to join a VM to the domain manually? (create a VM, RDP to VM, join to domain from system properties)
4. The link in the error message below has some good steps to follow, including a review of the domain join logs which are on the VM.
I would focus on making sure you can join a VM to the domain manually and consistently before trying to troubleshoot the domain join extension. This will confirm that there are no networking related issues between the VM and the DC as well as confirm we are entering the correct domain name, username/password.
Jeff_Bryant I'm getting this error in spite of having Azure Active Directory + Azure AD Domain Services deployed and peer networked with my vnet in which the host pool vms are being provisioned. I verified classic domain join works by establishing a point-to-site vpn connection into the vnet, using virtual network gateway setup, and was able to join a localhost hyper-v windows 10 desktop setup that i have. So not sure what to do in order to get wvd host pool template deployed vms to successfully join.
q1. Is there a localhost user account you can connect to the host pool vms that fail to successfully join the domain so you can manually join them?
q2. Is there some permissions pre-provisioning that has to be done for the wvdadmin@myazureaddomain.com account which i specify for wvd host pool tenant group access given the default tenant group and host pool tenant group objects don't seem to exist in my azure ad environment or in my azure resource group before a wvd host pool deployment or after one that failed due to this vm domain join error?
