JoinDomain VMExtensionProvisioningError when deploying WVD

[Luis_Farinango]

Hi guys

When I'm trying to deploy a Windows Virtual Desktop environment, I get this error message below:

{ "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/WVDResourceGroup/providers/Microsoft.Resources/deployments/rds.wvd-provision-host-pool-20191018100922/operations/F7935445F31FE2F2", "operationId": "xxxxxxxxxxxxxxxx", "properties": { "provisioningOperation": "Create", "provisioningState": "Failed", "timestamp": "2019-10-18T08:15:24.3354336Z", "duration": "PT3M11.2589953S", "trackingId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "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 'orbid365.be'\"." } ] } }, "targetResource": { "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/WVDResourceGroup/providers/Microsoft.Compute/virtualMachines/wvdtest-0/extensions/joindomain", "resourceType": "Microsoft.Compute/virtualMachines/extensions", "resourceName": "wvdtest-0/joindomain" } }}

It seems like my VM isn't able to join my domain which is configured with Azure Active Directory Domain Services.

The setup I'm using to get this working is:

• AADDS synced with Azure AD
• Virtual Network with 2 subnets
• 1 subnet for AADDS
• 1 subnet for the virtual machines

When trying to deploy, I also tried to use UPN and Service principal but both don't work either.

When deployment fails, the VM has been created but I'm not able to connect with it.

Does anyone know the solution for this? Have been looking through the other posts but they all don't seem to help for my setup.

Thanks in advance

[#2]

@Luis_Farinango : By default, we do not create a Public IP address for the VM since we want it to remain locked down. However, you can manually add a Public IP address to the VM, then connect to it that way. Then, you should be able to follow the various troubleshooting steps here to see what the error was: https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-vm-configuration#vms-are-not-joi... .

[#3 · Accepted solution]

@christianmontoya 

Thank you for the reply.

I had another error when trying to do this again and eventually I was adviced to deploy the host pool manually with the virtual machines. This workaround can be found under this post: https://techcommunity.microsoft.com/t5/Windows-Virtual-Desktop/Validation-failed-upon-creating-the-h...