Hi @Chris Parker ,
is it possible that I somehow created both a regular Azure VM and a Windows Virtual Desktop of the same name?
This could be possible ... not sure what you have done so far.
If both VMs with the same computer name
(in OS) are in the same vNet, it won't work properly (same like 2 computers in the same on-premises network)
If both VMs with the same computer name
(in OS) are joined to the same domain, it won't work because the second VM joined to the AD domain will destroy the first computer account in the AD domain.
A WVD host is technically nothing else than a normal Azure VM with a OS Disk, a NIC, a VM Sku, connected to a subnet of an Azure vNet.
The special thing of a WVD Host VM is:
- The VM is related/associated to one WVD Host Pool (during deployment)
- The VM is AD joined (during deployment)
That's it with the VM.
Maybe this is helpful as well:
https://learn.microsoft.com/en-us/azure/architecture/example-scenario/wvd/windows-virtual-desktop
----------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
You should check the DNS name resolution as well.
In your screenshot it is a ping to the DC IP?
What happens if you ping the AD Domain Name? Name if the AD Domain will be resolved to the IP of a AD DC?
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
Sorry I did both. when using the dns name (aadds.abc.com it responds with the proper DNS IP.)
Than it should hopefully work to add the VM to the AD :-)
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
For this option you mentioned earlier, does this mean I am unable to login with the azure ad credentials on the virtual desktop?
"If the second option: At the moment it's not possible to use an AAD user account for login. You need a synced on-premises domain or Azure AD DS to login. Which option do you have?"
Sign in to comment