Forum Discussion
Internal error occurred when connecting to RD
We have set up a WVD tenant but have not been able to logon to the VM. When connecting we get the error "Internal error occurred". Please see the output of the get-rdsdiagnosticsactivies belo...
Hi michawets ,
Is it mandatory to join the Virtual desktop to a Windows active directory domain?
I was under the impression that the setup of virtual desktop joins the VD to Azure AD and users in that Azure AD can logon to it.
There is no mention of an on-prem AD requirement in the documentation.
Hi Hermanbonnie ,
Yes, I'm afraid your Sessionhost(s) needs to be in a Windows AD, which syncs with Azure AD
This can be
- a Azure VM with Windows AD role installed, and Azure AD Connect
- Azure AD DS
It is mentioned in the Requirements from WVD:
https://docs.microsoft.com/en-us/azure/virtual-desktop/overview#requirements
Your infrastructure needs the following things to support Windows Virtual Desktop:
- An https://docs.microsoft.com/azure/active-directory/
- A Windows Server Active Directory in sync with Azure Active Directory. This can be enabled through:
- Azure AD Connect
- Azure AD Domain Services
- An Azure subscription, containing a virtual network that either contains or is connected to the Windows Server Active Directory
The Azure virtual machines you create for Windows Virtual Desktop must be:
- https://docs.microsoft.com/azure/active-directory-domain-services/active-directory-ds-comparison or https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan. Virtual machines can't be Azure AD-joined.
- Running one of the following https://docs.microsoft.com/en-us/azure/virtual-desktop/overview#supported-virtual-machine-os-images.