Apr 04 2019 01:29 AM
Apr 04 2019 01:29 AM
when running a deployment i received the flowing error even after enabling AD service endpoint.
should the vnet have a vpn connection to on premise DC?
Apr 23 2019 10:21 AM
@saarc @tommy_barnes : Yes, the virtual machine needs to domain-join to an Active Directory that is synchronized with Azure AD. This is so the service can resolve the "on-prem" user when connecting them to a session on the VM.
One alternative to a VPN is using Azure AD Domain Services, since the users created in Azure AD Domain Services also exist in Azure AD. This would satisfy that requirement.
May 02 2019 03:48 PM
@Alberto Rodriguez : If you are using Azure AD Domain Services, can you try providing credentials of a user in the "AAD DC Administrators" group for the credentials?
Also, adding my response to a different thread, for more visibility:
Do you have access to those VMs? If you can RDP into them, please look at C:\Packages and navigate down to the JsonADDomainExtension folder, you should be able to find a "status" file (or equivalent). If you open it up, it will typically give you the reason that it errored out. Unfortunately, I do not have too many details at the moment because the documentation on the extension is fairly light.
May 08 2019 08:08 AM
Same here, site-to-site connectivity is working fine. Plenty of other VMs living in this subnet without issues contacting local AD. Something is broken in the extension or deployment process. I've tried dedicate service account and super users (Domain Admin, Enterprise Admin, etc.) no luck.
May 16 2019 11:32 AM
@Christian_Montoya I've come across the same error while evaluating WVD preview. When the error occurs after the domain join extension fails, the VM instance are not accessible. Tried connecting to the VM's to resolve the domain issue, but it looks like the VM that is created does not have a Public IP address assigned.
I see the comment about "One alternative to a VPN is using Azure AD Domain Services, since the users created in Azure AD Domain Services also exist in Azure AD. This would satisfy that requirement". Is there some tutorial on how to set this up as part of following the the WVD tutorial? Looking for tutorial that will allow evaluation of WVD from scratch, no current use of Azure services.
May 16 2019 12:34 PM
@hankchi95 : to address your first question, that is correct in that the template does not create a Public IP address for the VMs, since all connections are completed using reverse connect. To connect to the VM through a public IP address, you'll first need to do this by:
To address your 2nd question on "if there's a tutorial to set up Azure AD Domain Services", here is the link to get started: https://docs.microsoft.com/azure/active-directory-domain-services/active-directory-ds-getting-starte... .
Sep 06 2019 09:25 AM
Sep 12 2019 08:27 AM
@Bionicjoe : It depends on which domain you are attempting to join. If you are attempting to join the "on-prem" AD, then yes, there would need to be some line of site back to that DC.
Just for full clarity, Azure AD DS stands up a brand new domain controller that is independent of any possible existing ones, just that it has the logic to create users based from your Azure Active Directory.