Forum Discussion
Error deploying WVD to a subscription
I've tried three different deployments in the Azure portal for WVD. I keep getting the same error after VM creation and domain join:
{"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 'dscextension'. Error message: \\\"DSC Configuration 'FirstSessionHost' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_ScriptResource failed to execute Set-TargetResource functionality with error message: One or more errors occurred. The SendConfigurationApply function did not succeed.\\\".\"\r\n }\r\n ]\r\n }\r\n}"}]}
Has anyone seen this? I have tried using the AAD credentials method for tenantAdminUPN (instead of using a service principal) for all three. Has anyone had success using this method? Or should I just try the route of SPN instead. Thanks in advance for any suggestions.
jaycrumpgp : The Azure Marketplace offering is now resolved and you should be able to test again!
- Christian_Montoya
Microsoft
jaycrumpgp : We've heard similar feedback of folks trying to deploy. We recently update the documentation to suggest the service principal route, as it will work in all cases. You can see the updated steps/guide over at https://aka.ms/wvdpreview . Please let us know if that ends up working for you and your environment.
Thanks, I'll give it a shot. Although now I'm seeing the same 'template URL' error that others are seeing and have posted here:
- Christian_Montoya
jaycrumpgp : The Azure Marketplace offering is now resolved and you should be able to test again!
and......a different error trying to create pool via shell now. What is up with the random errors.
When I try to run 'new-rdsregistrationinfo' cmdlet and point to a path on my desktop I am getting 'access to the path c:\users\blahblah\desktop is denied'.
- Christian_Montoya
jaycrumpgp : I'm uncertain on the "New-RdsRegistrationInfo" error...if you have personal information, I'd be happy to follow up on private messages.
Regarding the URL error, we are actively working on resolving the Azure Marketplace offering. In the meantime, you can use our GitHub ARM Template to create and provision the host pool: https://github.com/Azure/RDS-Templates/tree/master/wvd-templates/Create%20and%20provision%20WVD%20host%20pool
I'm seeing this today, trying to create a Windows Virtual host pool for the first time
The template deployment 'rds.wvd-provision-host-pool-20191007144940' is not valid according to the validation procedure. The tracking id is '0819cb7e-5b53-4901-87cf-a0548d9f7d4a'. See inner errors for details.
Any one who can help?
- Christian_Montoya
sth_zantio : In Azure, when you try to search for Windows Virtual Desktop, can you complete the search, then choose the selection from the results. For some reason, we sometimes see 2 offerings in the Azure Gallery.
