Forum Discussion
What is your experience with Start VM on connect. Share your voice!
We have never been able to get the experience to work.
Web client: We couldn’t connect because your VM failed to start. Try again later or contact your tech support for help if this keeps happening.
Desktop client: Something went wrong when we tried to connect. If this keeps happening, ask your admin or tech support for help. Error code: 0x83886179
When debugging error messages focus on the messages the service gives you and not the RDclients. An easy way to do this is using Azure Monitor: https://docs.microsoft.com/en-us/azure/virtual-desktop/azure-monitor - those messages will be more meaningful for debugging
No, we setup the pre-reqs. But, when we search for "Windows Virtual Desktop" when assigning members to the Start WVD VM on Connect role, there are TWO instances of "Windows Virtual Desktop" apps listed with different application IDs (both are listed under Enterprise Applications but one is a Microsoft Application for ARM WVD and the other is an Enterprise Application for legacy/classic WVD). The person that setup the assignment only added the first instance/the Enterprise Application for classic WVD to the role.
Once the "Windows Virtual Desktop" app with the app id that is from the Microsoft Application/ARM WVD was added to the role in IAM, Start VM on Connect started working.- For us its giving us issues with some specific VMs where it works and then stop working telling the end users that there is no resource available....again this when VMs are in the same Pool, some works and some not.
- Please troubleshoot issues on the VMs. You have the option to work with support if you can't resolve the issue.
