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
Luis_Farinango"occured while joining Domain 'orbid365.be'"
1. First thing to validate is does the vnet that has your WVD have access to the vnet that has your ADDS?, you'll need to ensure that peering and the subsequent DNS change is completed so that vnetA (wvd vnet) can resolve names on vnetB (ADDS vnet).
2. Secondly validate if the domain admin account that you are using has the necessary permissions required to carry out a domainJoin task, typically the domain admin or any priviledge user should be able to. Remember the name should be mailto:username@localDomain.ext (IE' mailto:domainJoinerAdmin@dummyDomain.local)
3. As others have mentioned, keep in mind the character limit on the domain name on Azure.
4. Also what you can do, setup a testVm, place it on the same vnet as the WVD, try to do a standalone domainJoin, this will assisting testing the domain account permissions, vnet-vnet communication and help troubleshoot anything before deploying WVD, at least by then you will have tested the minor hurdles.
Refer to these articles:
https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/join-a-computer-to-a-domain
https://docs.microsoft.com/en-us/azure/virtual-network/tutorial-connect-virtual-networks-portal