Forum Discussion
Domain Join Error while deploying HostPool
Microsoft1. 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.
wrt q1 . i deployed aadds
wrt q2. i'm specifying <domainname>.onmicrosoft.com should i just be specifying netbios<domainname> and not the fully qualified dns domain name?
wrt q3. i'm deploying hostpool to a separate vnet that has peer to peer network connection with aadds_vnet
wrt q4. i've successfully establishted a point to site vpn connection to vnet that wvd host pool vms are being deployed to and then successfully joined a localhost hyper-v hosted win10 install to that cloud aadds_vnet hosted azure ad domain services gc/dc pair using the sam vmjoiner@mydomain.onmicrosoft.com account i provided the wvd host pool template.
given all that not sure what i do differently next to get my first wvd host pool deployment to succeed past the vm domain join step.
