Forum Discussion
Need help with Virtual Host deployment
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug 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 '********'\\\".\"\r\n }\r\n ]\r\n }\r\n}"}]}
4 Replies
May be the issue, if you've not done it.
If you are using Azure ADDS for the domain join of your VM, you need to make sure that you change the password of the account that is being used for the domain join (and it also needs to be in the correct group). That password change will then sync from Azure AD to AADDS.
If your organization has cloud-only user accounts, all users who need to use Azure Active Directory Domain Services must change their passwords. A cloud-only user account is an account that was created in your Azure AD directory using either the Azure portal or Azure AD PowerShell cmdlets. Such user accounts aren't synchronized from an on-premises directory.
https://docs.microsoft.com/en-us/azure/active-directory-domain-services/active-directory-ds-getting-started-password-sync
Hi, looks like we're missing a bit of the error there but we know it is breaking at the "joindomain" stage. Do you have an on-prem AD? The gotcha I had on here was that the admin account I was using didn't comply with Azure complexity requirements and therefore wouldn't allow the system to connect to the AD....
Thanks for the answer
I am trying to create a Host Pool for the Windows Virtual Desktop
when he gets to the stage of adding the machine to the domain he stuck at that error
I have a DC in the Azure and not on-prem
Yossi Vizel that may well be the problem then! I am seeing a lot of comments saying that you need on-premise AD for this preview - I don't know if that is true or not as I have an on-prem so hopefully someone else can help you....
