JoinDomain VMExtensionProvisioningError when deploying WVD

Occasional Visitor

I got the following error:

 

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations 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 'fundapps.co'\\\"\\r\\n\\r\\nMore information on troubleshooting is available at https://aka.ms/vmextensionwindowstroubleshoot \"\r\n }\r\n ]\r\n }\r\n}"}]}

 

The AD is in a resource group called WVD and so it the host pool being created. Just can't figure out why it won't join/setup The user is in the AAD DC group as well as a Tenant Creator group. Not sure what else to test. 

 

1 Reply

@BachDSingh

 

When I run into domain join problems with the extension, I'll typically RDP into a VM and try joining the domain manually to rule out networking or credential problems, which many times is either one causing the problem.  Be sure to configure a custom DNS for the VNET that is the IP for AADDS, otherwise the VM's in your host pool will not be able to resolve your domain name.

 

Here is a good document to help with further troubleshooting

https://docs.microsoft.com/en-us/azure/active-directory-domain-services/network-considerations#name-...

 

-Jeff