Forum Discussion

John Quile's avatar
John Quile
Brass Contributor
Jan 24, 2020

'joindomain' error with Windows Virtual Desktop

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 onlin...
  • knowlite's avatar
    knowlite
    Jan 24, 2020

    John Quile 

    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

knowlite's avatar
knowlite
Iron Contributor

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)

John Quile's avatar
John Quile
Brass Contributor
Jan 24, 2020

knowlite 

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? 

Resources