Jan 23 2020 10:42 PM
Jan 23 2020 10:42 PM
I have a single vnet with a subnet that has gateway and a subnet that has a Domain Controller successfully joined to our on-prem domain via VPN tunnel.
I went through all the steps I've found online to getting Windows Virtual Desktop going.
Esssentially I've gotten to the deploy of the VM part however it fails with joindomain error:
VM has reported a failure when processing extension 'joindomain'. Error message: \"Exception(s) occured while joining Domain....
What could be causing this? A credential? I know it has permissions. Do I need to change the subnet that this WVD Host Pool is on to the DNS server of the Domain Controller in the same VNet?
Jan 23 2020 11:42 PMSolution
Is the VM in the same vnet as the DC?
What is the DNS server in the subnet where the WVD VM is created? The domain needs to be resolvable.
Another option is that the account used for joining the WVD VM to the domain is incorrect.
Looking forward to your feedback!
Jan 24 2020 06:05 AM - edited Jan 24 2020 06:07 AM
Jan 24 2020 06:16 AM
Jan 24 2020 06:30 AM - edited Jan 24 2020 06:33 AM
You mention that you do not have special DNS settings on the Vnet (which is pointing to azure dns instead then).
Make sure that your DC is acting as the DNS server in the WVD vnet so your domain is resolvable inside the vnet itself. I would retry deploying the VM if you have made that change.
The vnet does not know that you have a DC installed in it which is acting as a DNS server.
The reason why these things aren't mentioned in the WVD tutorials is because this is not related to WVD (same behavior on every azure vm)
Jan 24 2020 07:43 AM
Well I set the DNS of the VM DC to a DC on-prem.
But I don't know if I want to set the entire VNET to the same DNS, that seems a bit much.
And I can't set the DNS on a NIC for WVD because they can't provision for me to get to their NIC properties?
Since this deployment fails, what do I do? The resource group is incomplete do I just delete it and start over?
Jan 24 2020 08:35 AM
Ok so I manually created a VM in the subnet. I can ping the IP addresses of my on-prem and the Azure DCs. But not the host names.
So I need to set DNS server to my Dc in Azure for the VMs in azure, but can i do that upon provisioning of the WVD? Or I have to literally set the DC as THE DNS server for the entire VNet just so this one subnet can allow WVD's to join the domain?
Jan 24 2020 12:03 PM
So I think it's working now, at least with a one-off VM I deployed.
I'm not sure if that's the best route or not.
But I believe that will fix the WVD Host Pool deployment.
Jan 24 2020 02:04 PM
Jan 24 2020 02:07 PM
Jan 24 2020 02:20 PM
Jan 24 2020 03:43 PM
Jan 27 2020 03:20 AM