Forum Discussion
saarc
Apr 04, 2019Copper Contributor
failed to join to the domain
hi All 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? {"code":"DeploymentFailed","messa...
ChristopherB2175
May 08, 2019Copper Contributor
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.
Christian_Montoya
Microsoft
May 15, 2019ChristopherB2175 : If you go to these VMs after the domain join extension fails and you provide the same domain join credentials and the same "domainToJoin", does it then join the domain correctly?
- hankchi95May 16, 2019Copper Contributor
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.
- Christian_MontoyaMay 16, 2019
Microsoft
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:
- Creating a public IP address
- Assigning it to the VM
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-started .
- BionicjoeSep 06, 2019Copper Contributor
Was there ever a final resolution to this. I'm in the same boat.
On-prem AD and I got AADDS working with password hash enabled.
My error says exceptions occurred during the joindomain.
Do I still need a site/point-to-site VPN to Azure?
DC VM on Azure?