Forum Discussion
'joindomain' error with Windows Virtual Desktop
Hi John,
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!
BR,
Dirk
Hi John,
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!
BR,
Dirk
So I think it's working now, at least with a one-off VM I deployed.
- Created new VNet and subnet for the WVD network
- Setup peering between it and the VNet that has the Domain Controller VM
- Set the WVD Vnet DNS server to the IP of the Domain Controller VM in the other VNet
- Added on-prem Firewall static route to the new WVD subnet
- I can join it to the domain.
I'm not sure if that's the best route or not.
But I believe that will fix the WVD Host Pool deployment.
- And actually I just realized now I wonder if it’s because my on-prem firewall doesn’t have a static route to this WVD subnet. Also I wonder if I need to add it to the Azure DC site in AD.
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)
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?
- Hi ,
Yes the WVD VM subnet is in the same VNET as the DC.
From on prem I can connect to other servers (like a print server) that are in other subnets (within the same vNET) that do not have any special DNS settings (they’re just set to default).
The only place I have a DNS setting pointing to an on-prem Domain Controller is on the NIC properties of the DC virtual machine in Azure (and that’s not in Windows it’s in the Azure DNS settings for the VM).
I’m not reading anywhere beyond that to need DNS settings for WVD or the WVD subnet. But do I need to? Because the subnet for it I created during the create WVD pool pool wizard.
