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 short survey which is meant to capture your rating and comments. This will help me and feature team to drive further improvements: https://forms.office.com/r/SRHMS8DVWk
39 Replies
Hi, the documentation states we need Windows Client version "1.2748" or later.
https://docs.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect
Following the link in the article downloads, the latest public build 1.2.2061.0
The latest insider build is 1.2.2127
Where is "1.2748" build at?
I have installed the insider build and upon launching a personal desktop I don't get any status message saying "starting / waiting remote pc" as I've seen in screenshot posted in other blogs.
https://www.terminalworks.com/blog/post/2021/04/04/windows-virtual-desktop-start-virtual-machine-on-connect
Looking forward to testing this feature in our environment thanks for this addition.
byertjames : Looks like there was a mix-up with the build numbers. We will fix this. When you look at your screen shot the info message is there. See here emphasized:
Thanks unfortunately I still get the message "There was a problem connecting to the remote resource."
evasse Hey, has been working so far for us, specifically with the pooled host pools. However it only works when the desktop experience is a remote desktop - we have host pools setup specifically for RemoteApp deployment and in these scenarios, the VM's do not start when a user tries to launch a RemoteApp.
Was this functionality not intended to work? It is not listed anywhere as not supported.
- Works in both scenarios. We haven't had issue reports for remote apps. Can you open a support case if it is a consistent scenario for you? It might need more troubleshooting.
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
- 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 debuggingNo, 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.
