Forum Discussion
What is your experience with Start VM on connect. Share your voice!
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."
- Ensure you haven't missed pre-requisites and set-up custom RBAC role that allows to power manage the VM: https://docs.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect#create-a-custom-role-for-start-vm-on-connect
Review diagnostic messages from backend using either Log Analytics or Azure Monitor for Azure Virtual Desktop which include better messaging for the administrator. In the screenshot you have an activity ID which you can reuse to query data on the backend:
- https://docs.microsoft.com/en-us/azure/virtual-desktop/azure-monitor
- https://docs.microsoft.com/en-us/azure/virtual-desktop/diagnostics-log-analytics
The client message might hint at networking issue. If you can't progress beyond this point reach out through support for deep dive trouble shooting.- In my case it looks like it's a back end issue; permissions are set, start vm on connect is enabled.
Today I have collected logs with MS support via the webclient and we got this message in the log.
2021-06-25T19:38:04.308Z OrchestrationState(NORM): Requesting orchestration from service URL https://afdfp-rdgateway-r1.wvd.microsoft.com:443/api/arm/v2/connections?CorId=%7B53defa59-ae5e-4cc3-8cec-23e63c160000%7D
2021-06-25T19:38:04.310Z Core telemetry event: eventName=OrchestrationState, traceMessage=The client made a orchestration http POST request to afdfp-rdgateway-r1.wvd.microsoft.com
2021-06-25T19:38:05.385Z OrchestrationState(WARN): The session host failed to start, code: E_PROXY_ORCHESTRATION_LB_SESSIONHOST_FAILED_TO_START, message: "Session Host with ID = '<computername>' has failed to be woken up. Please contact your admin."
2021-06-25T19:38:05.387Z Connection(ERR): The connection generated an internal exception with disconnect code=SessionHostResourceNotAvailable(10012), extended code=<null>, reason=Orchestration failed - session host failed to start, error E_PROXY_ORCHESTRATION_LB_SESSIONHOST_FAILED_TO_START message: Session Host with ID = '<computername>' has failed to be woken up. Please contact your admin.
Thrown in thread 544008 at:
gateway/orchestrationstate.cpp(380)
Call Stack:
Callstacks are currently disabled