Forum Discussion
What is your experience with Start VM on connect. Share your voice!
Hi Community :)!
If you remember I announced a while ago public preview of start VM on connect. As you had some time to explore the feature, let me know what you think.
Please answer this...
My assumption is you have missed the pre-requisites section in the documentation: https://docs.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect#create-a-custom-role-for-start-vm-on-connect.
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
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.
