Forum Discussion
evasse
Microsoft
Mar 31, 2021Start VM on connect starts Public Preview!
For all early birds who want to start testing, keep in mind that we have the following limitations:
You can configure the setting on validation pool only (we will update this post when you can en...
Jason_Parker
Microsoft
Apr 06, 2021evasse Spent some time today testing the Start VM On Connect feature with little success. It may be due to my customers unique configuration, but can't seem to get it to work.
WVD Spring Release (v2)
Personal Host Pool = check
Validation Host Pool = check
Custom Role = check
Azure Public = check
Updated Host Pool with StartVMOnConnect:$True = check
The session host was initially stopped (deallocated). Started the VM from PowerShell and logged in to the VM using RD Client (1.2.1844.0). Shutdown the VM from inside the Session and confirmed via PowerShell the VM was stopped (not deallocated). Tried to Connect to the VM and got the error below:
[Window Title]
Remote Desktop
[Content]
An internal error has occurred.
[^] Hide details [OK]
[Expanded Information]
Error code: 0x0
Extended error code: 0x0
Timestamp (UTC): 2021-04-06T20:46:42.414Z
Activity ID: b574ca6f-a0cb-4717-a7d2-f2606dd50000
Press Ctrl+C to copy.
Thanks,
Jason Parker
evasse
Microsoft
Apr 07, 2021Hi Jason! Please try the following:
- review the error messages in diagnostics for this activity ID. https://docs.microsoft.com/en-us/azure/virtual-desktop/diagnostics-log-analytics . You can use as well: https://docs.microsoft.com/en-us/azure/virtual-desktop/azure-monitor
- The issue your are running into most likely is missing permissions. Please review carefully this section of the docs: https://docs.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect#use-the-azure-portal
Thank you!
- review the error messages in diagnostics for this activity ID. https://docs.microsoft.com/en-us/azure/virtual-desktop/diagnostics-log-analytics . You can use as well: https://docs.microsoft.com/en-us/azure/virtual-desktop/azure-monitor
- The issue your are running into most likely is missing permissions. Please review carefully this section of the docs: https://docs.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect#use-the-azure-portal
Thank you!