Forum Discussion
JoinDomain / Conflict
Reference:
2. https://docs.microsoft.com/en-us/azure/virtual-desktop/tenant-setup-azure-active-directory
Following these two sets of instructions I end up like this post:
https://techcommunity.microsoft.com/t5/Windows-Virtual-Desktop/Azure-Windows-Virtual-Desktop-Provision-Host-Pool-JoinDomain/m-p/727794
With the following Errors:
- Can you check the paths here and share the lgos from here
C:\Packages\Plugins\Microsoft.Compute.JsonADDomainExtension
C:\WindowsAzure\Logs\Plugins\Microsoft.Compute.JsonADDomainExtension\1.3.6
Latest run that errors out also the version might be different
Also reading the error what is your DNS server setup on the VNET?
- evasseMicrosoft
- myusrnBrass Contributor
evasse thanks for this response. I've been trying repeatedly to setup a windows virtual desktop host pool in an azure subscription where i only have azure AD and azure AD domain services gc/dc deployed, i.e. not cloud diy vm gc/dc or vnet exposed on-premises classic AD gc/dc setups.
The wvd host pool template processing kept failing on the host pool vm domain joining step and the fix was https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-set-up-issues%C2%A0 -> "Cause 3: Your virtual network (VNET) DNS configuration is set to Default." defined fix.
Seems like there should be some wvd host pool template wizard or walk through documentation on this scenario for companies that want wvd but are 100% azure active directory based with their IAM environment.
Now the wvd host pool template is failing at point with this message:
"VM has reported a failure when processing extension 'dscextension'. Error message: "DSC Configuration 'CreateHostPoolAndRegisterSessionHost' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_ScriptResource failed to execute Test-TargetResource functionality with error message: Windows Virtual Desktop Authentication Failed . . ."- AllenVisserJhbCopper Contributor
Howzit, so i eventually got my WVD vms to domain join after many frustrating hours.
I have a lab with a Windows AD DC vm and an AD Connect server (and even built Azure AD DS out of frustration!)
I had repeatedly tried deploying the WVD vms using the Azure Global Admin account and each time it failed.
I then went and created a different account on Windows AD with Enterprise Admins and used this account. The vms successfully joined using this Windows AD based Enterprise Admin account.
Good luck.
- jonmcwilliamsCopper Contributor
I'm having the same issues as Eric, I have a new Azure AD DS domain, and I'm trying to setup WVD ARM. Once I create the VM, I cannot seem to get it to successfully join the domain. I have tried the DNS fix, validated the credentials of the vmjoiner account (global admin). No matter what I do - it fails
"properties": {"statusCode": "Conflict","statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceDeploymentFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"VMExtensionProvisioningError\",\"message\":\"VM has reported a failure when processing extension 'joindomain'. Error message: \\\"Exception(s) occured while joining Domain 'dquin.onmicrosoft.com'\\\"\\r\\n\\r\\nMore information on troubleshooting is available at https://aka.ms/vmextensionwindowstroubleshoot \"}]}}","eventCategory": "Administrative","entity": "/subscriptions/b45ab268-91f4-412c-bc14-5d899771b190/resourcegroups/RG01/providers/Microsoft.Compute/virtualMachines/DQ-0/extensions/joindomain","message": "Microsoft.Compute/virtualMachines/extensions/write",- Stefan GeorgievMicrosoft
jonmcwilliams when you setup Azure AD DS can you check if the DNS is setup to Azure or to the IP of Azure AD DS? It must be the later
- Stefan GeorgievMicrosoftCan you check the paths here and share the lgos from here
C:\Packages\Plugins\Microsoft.Compute.JsonADDomainExtension
C:\WindowsAzure\Logs\Plugins\Microsoft.Compute.JsonADDomainExtension\1.3.6
Latest run that errors out also the version might be different
Also reading the error what is your DNS server setup on the VNET?