Forum Discussion
Solved
Azure AD Connect & WVD
Hey all Im setting up WVD (Windows Virtual Desktop) for a client. From what ive read on docs i either need Azure AD Connect (with my on premise enviorment) or Azure AD Domain Services. Im ...
I managed to fix this myself.
I want to share the issue and what solution worked for me, and also give a big thanks to all the people that had engagement in this thread.
my on prem AD had the same domain name as my Azure AD tenant.
Also, my on prem AD join user had the same UPN as one of my Office365 users (which is a part of Azure AD Tenant)
So I suppose wvd deployment was trying to authenticate with the wrong catalog, and since I don't have Azure ADDS deployed it failed.
Hope someone troubleshooting this same issue will find this thread.
The Domain Join account does not need to by synced with AD Connect. The domain administrator account is a protected account and not replicated by default. I’ve used domain admin accounts many times to join session hosts.
Be sure to set the VNet DNS servers to your DC, or domain DNS if they are different. Also, if you have deployed session hosts with the same prefix in the past, you may need to delete the old session hosts from AD or reset the computer account. They can’t join the domain if there are existing computer accounts with the same name.
I have a new version of that video, link in the Fall 2019 version comments. There were some registrations that required an Azure AD global admin account for that version. Now that WVD is ARM, that’s not needed.
For the second host pool error with “Changing property ‘adminUsername’, did you use the back button after the failed deployment and update the domain join account? If so, it looks like you will need to start the deployment over without going back.
-Travis
I'm Super thankful for your respons TravisRoberts
DNS Settings on VNET are costum and this is the IP of the Domain Controller that is on premise.
Note that if I create a new VM in Azure within this VNET I can manually (within windows) join the domain without any problem what so ever.
It is just when I try to do it from the WVD Deployment Portal.
I have tried different prefix names just in case of that reason also.
You mention that the administrator account does not need to be synced to azure ad. Sure.
But, Do i need Azure AD Connect at all at this point then?
As I said earlier in this thread, I have ONLY synced a few users that will use thisI managed to fix this myself.
I want to share the issue and what solution worked for me, and also give a big thanks to all the people that had engagement in this thread.
my on prem AD had the same domain name as my Azure AD tenant.
Also, my on prem AD join user had the same UPN as one of my Office365 users (which is a part of Azure AD Tenant)
So I suppose wvd deployment was trying to authenticate with the wrong catalog, and since I don't have Azure ADDS deployed it failed.
Hope someone troubleshooting this same issue will find this thread.
