JoinDomain VMExtensionProvisioningError when deploying WVD

%3CLINGO-SUB%20id%3D%22lingo-sub-1350387%22%20slang%3D%22en-US%22%3EJoinDomain%20VMExtensionProvisioningError%20when%20deploying%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1350387%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EI%20got%20the%20following%20error%3A%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%7B%22code%22%3A%22DeploymentFailed%22%2C%22message%22%3A%22At%20least%20one%20resource%20deployment%20operation%20failed.%20Please%20list%20deployment%20operations%20for%20details.%20Please%20see%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FDeployOperations%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FDeployOperations%3C%2FA%3E%20for%20usage%20details.%22%2C%22details%22%3A%5B%7B%22code%22%3A%22Conflict%22%2C%22message%22%3A%22%7B%5Cr%5Cn%20%5C%22status%5C%22%3A%20%5C%22Failed%5C%22%2C%5Cr%5Cn%20%5C%22error%5C%22%3A%20%7B%5Cr%5Cn%20%5C%22code%5C%22%3A%20%5C%22ResourceDeploymentFailure%5C%22%2C%5Cr%5Cn%20%5C%22message%5C%22%3A%20%5C%22The%20resource%20operation%20completed%20with%20terminal%20provisioning%20state%20'Failed'.%5C%22%2C%5Cr%5Cn%20%5C%22details%5C%22%3A%20%5B%5Cr%5Cn%20%7B%5Cr%5Cn%20%5C%22code%5C%22%3A%20%5C%22VMExtensionProvisioningError%5C%22%2C%5Cr%5Cn%20%5C%22message%5C%22%3A%20%5C%22VM%20has%20reported%20a%20failure%20when%20processing%20extension%20'joindomain'.%20Error%20message%3A%20%5C%5C%5C%22Exception(s)%20occured%20while%20joining%20Domain%20'fundapps.co'%5C%5C%5C%22%5C%5Cr%5C%5Cn%5C%5Cr%5C%5CnMore%20information%20on%20troubleshooting%20is%20available%20at%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fvmextensionwindowstroubleshoot%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fvmextensionwindowstroubleshoot%3C%2FA%3E%20%5C%22%5Cr%5Cn%20%7D%5Cr%5Cn%20%5D%5Cr%5Cn%20%7D%5Cr%5Cn%7D%22%7D%5D%7D%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20AD%20is%20in%20a%20resource%20group%20called%20WVD%20and%20so%20it%20the%20host%20pool%20being%20created.%20Just%20can't%20figure%20out%20why%20it%20won't%20join%2Fsetup%20The%20user%20is%20in%20the%20AAD%20DC%20group%20as%20well%20as%20a%20Tenant%20Creator%20group.%20Not%20sure%20what%20else%20to%20test.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1353953%22%20slang%3D%22en-US%22%3ERe%3A%20JoinDomain%20VMExtensionProvisioningError%20when%20deploying%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1353953%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F643141%22%20target%3D%22_blank%22%3E%40BachDSingh%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20I%20run%20into%20domain%20join%20problems%20with%20the%20extension%2C%20I'll%20typically%20RDP%20into%20a%20VM%20and%20try%20joining%20the%20domain%20manually%20to%20rule%20out%20networking%20or%20credential%20problems%2C%20which%20many%20times%20is%20either%20one%20causing%20the%20problem.%26nbsp%3B%20Be%20sure%20to%20configure%20a%20custom%20DNS%20for%20the%20VNET%20that%20is%20the%20IP%20for%20AADDS%2C%20otherwise%20the%20VM's%20in%20your%20host%20pool%20will%20not%20be%20able%20to%20resolve%20your%20domain%20name.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere%20is%20a%20good%20document%20to%20help%20with%20further%20troubleshooting%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory-domain-services%2Fnetwork-considerations%23name-resolution-when-connecting-virtual-networks%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory-domain-services%2Fnetwork-considerations%23name-resolution-when-connecting-virtual-networks%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-Jeff%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
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
Highlighted

@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