Forum Discussion
sberens
May 05, 2020Copper Contributor
Reconnected RemoteApp session not showing locked session password prompt
The issue below was observed in v1.2.945 (x64) Windows, I'm unsure if this worked properly in a prior version, or on any other platforms. In this example, Calculator is shared as a RemoteApp on a...
sberens
May 21, 2020Copper Contributor
alvinlau Good day!
I was able to validate that my sandbox environment exhibits the same behavior as your environment. Reconnect popup appears, then shortly after reconnecting, the window theme bounces to classic, then it returns to normal and I can interact with the App, and the UI controls (Min/Max/Close). No key presses required! (I also learned that the space bar will return the session to usable, in the original scenario)
I don't know that it would make a difference, but my production host pool has 2 session hosts, but my sandbox only has one.
I'll continue to troubleshoot and compare the two environments for differences, but if you have any recommendations, please don't hesitate to reach out.
Thank you again for your time.
Kind regards,
Sean
alvinlau
Microsoft
May 21, 2020Hi sberens!
Thanks for trying it out in your sandbox environment.
I didn't know you had two session hosts in your production host pool. Are you seeing the same issue from both of session hosts? Have you tried connecting to your production session hosts from another local machine?
I'm thinking maybe the network connectivity between your local machine and the production host pool triggered some timing issue in the WVD Client app (msrdc.exe).
If possible, can you please collect Time Travel Trace for me to investigate?
- Install WinDbg Preview from Microsoft Store.
- Kill any running instance of msrdc.exe.
- Make a RemoteApp connection to the production host pool. To make things simpler, better have only one RemoteApp window running.
- Follow the instruction here to attach WinDbg Preview to msrdc.exe and start Time Travel recording.
- Disable and re-enable your network adapter to reproduce the issue.
- Wait for about 10 seconds and then press [space bar] to let the session return to stable.
- Stop the Time Travel recording.
Since Time Travel Trace is actually a memory dump, it may contain private information. So, please do NOT share it publicly.
Regards,
Alvin