Forum Discussion
JoinDomain VMExtensionProvisioningError when deploying WVD
Thank you for the reply.
I had another error when trying to do this again and eventually I was adviced to deploy the host pool manually with the virtual machines. This workaround can be found under this post: https://techcommunity.microsoft.com/t5/Windows-Virtual-Desktop/Validation-failed-upon-creating-the-host-pool/m-p/924184
MicrosoftLuis_Farinango : By default, we do not create a Public IP address for the VM since we want it to remain locked down. However, you can manually add a Public IP address to the VM, then connect to it that way. Then, you should be able to follow the various troubleshooting steps here to see what the error was: https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-vm-configuration#vms-are-not-joined-to-the-domain .
Ashley_YangHi Christian_Montoya ,
When I used an external email account with activated azure benefit by my MS FTE account to sign in Azure, and it will generate a domain like this:
However, when I create a AAD Domain Service, the DNS domain name can't be set as the same above, since it told the "yangjiajia325gmail" is too long, it should be 15 char or less. So I create the ADD DS with a different DNS domain name.
Then I want to create a WVD hostpopl, it failed in deployment with domain join conflict like this:
Do you have any idea how can I solve this problem?
- Christian_Montoya
Ashley_Yang : You would need to use the user's UPN for the actual domain. What was the name of the Azure AD DS that got stood up? Make sure to use user@<aadds-domain> .
- Ashley_Yang
The name of the Azure AD DS is "yangjiajiagmail.onmicrosoft.com", the automatically generated "domain" name is "yangjiajia325gmail.onmicrosoft.com". Do you mean I should use the UPN like user@yangjiajiagmail.onmicrosoft.com?
If yes, a little concern is the user account I created in AAD is use@yangjiajia325gmail.onmicrosoft.com. Why do I should do like that?
Thank you for the reply.
I had another error when trying to do this again and eventually I was adviced to deploy the host pool manually with the virtual machines. This workaround can be found under this post: https://techcommunity.microsoft.com/t5/Windows-Virtual-Desktop/Validation-failed-upon-creating-the-host-pool/m-p/924184