Forum Discussion
Requirement to have an on-prem AD
- Mar 25, 2019
HandA
on-prem AD is not required.
AD requirements:
Option 1: Domain controller that is synchronized with Azure Active Directory. The domain controller can be on-prem or in cloud. To synchronize with Azure Active Directory install Azure Active Directory Connect.
Option 2: Azure AD Domain Services domain in Azure (automatically synced with Azure Active Directory)
HandA
on-prem AD is not required.
AD requirements:
Option 1: Domain controller that is synchronized with Azure Active Directory. The domain controller can be on-prem or in cloud. To synchronize with Azure Active Directory install Azure Active Directory Connect.
Option 2: Azure AD Domain Services domain in Azure (automatically synced with Azure Active Directory)
- HandAApr 15, 2019Brass Contributor
Thanks. I have this working now using Azure ADDS. Documentation seemed a bit unclear when I first looked at it
- Alberto RodriguezMay 02, 2019Copper Contributor
HandA Did you get it to work without need of on-premise AD or AD Connect?
- Alberto RodriguezMay 02, 2019Copper ContributorI keep getting the following deployment fail error:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"VMExtensionProvisioningError\",\r\n \"message\": \"VM has reported a failure when processing extension 'joindomain'. Error message: \\\"Exception(s) occured while joining Domain 'mnetpr.com'\\\".\"\r\n }\r\n ]\r\n }\r\n}"}]}
- tommy_barnesApr 18, 2019Brass Contributor
How were you able to get the machine to connect to the domain mine failed on domain join wondering If i can somehow do it manually
- Ron HoweMar 27, 2019Copper Contributor
I don't understand your response. Per https://docs.microsoft.com/en-us/azure/virtual-desktop/overview:
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/microsoft-desktop-optimization-pack/appv-v4/domain-joined-and-non-domain-joined-clients 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 supported OS images:
- Windows 10 Enterprise multi-session
- Windows Server 2016
I would like to avoid any and all on-premises requirements and simply have an Azure Active Directory with Azure Active Directory Domain Services enabled with Windows Virtual Desktop virtual machines automatically domain-joined to that instance. Completely cloud. Nothing physical.
Is this possible ?