Errors deploying a WVD Host Pool

Copper Contributor

We have an onprem Windows Server Essentials that as AD Azure Sync (not AD connect as it is not supported). I have deployed Azure AD services and can see all the onprem users.

I now want to deploy Azure Virtual Desktop but I continue to get deployment errors.

 

We have an onprem Windows Server Essentials that as AD Azure Sync

I have deployed Azure AD services

and now want to deploy Azure Virtual Desktop but I continue to get deployment errors;

 

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

 

Have tried;

- specifiying OU / domain off and on

- same Subnet as Azure AD host

 

Please help

1 Reply

@nicknz  one of a few things that typically cause this in my experience. 

 

1) The user account specified for domain join does not have permission to join the vm

2) The domain name specified in the deployment is not correct

3) The OU specified has an issue in the syntax

4) DNS settings are missing from the VNET

5) There are issues with firewall rules on the DC

 

let me know what you find after checking these items.