Forum Discussion
Reconnected RemoteApp session not showing locked session password prompt
alvinlau Good day!
I published Command Prompt, and when running the specified command, the lock screen appears as expected. Password entry is seen and once confirmed, I'm returned to the command prompt.
Then, attempting the same steps described in my initial write-up, Disabling and enabling the network adapter on the local machine, the same symptom is seen on with the Command Prompt window. The remote screen seems to shift up and to the left slightly exposing black border in the right and bottom.
Clicking out off the RemoteApp and clicking it again will re-render the Title bar, showing old school themeless title bar, with (Reconnecting) in the title, and again, the window cannot be moved, minimized, or closed as none of the interface buttons work. Blindly entering my password and hitting return will return me to a working command prompt after 3-5 seconds and the command prompt window is no longer skewed and no longer has the additional border.
If you need anything else, please let me know.
Kind regards,
Sean
Microsoftsberens Thank you for your reply!
To help me understand the issue, I have couple more questions.
Did you wait for 10 minutes to trigger the session idle timeout before disabling the network adapter on the local machine? Did you try entering something other than the password when the RemoteApp window could not be moved, minimized, or closed?
Regards,
Alvin
alvinlau No waiting, at any time I can attempt the network adapter flip and see this behavior.
Interestingly, taking your advice and trying to enter something else, it seems that the ENTER key is doing the magic and bringing the session back to usable! I had assumed the lock screen was simply not rendering, but there must be something something else going on behind the scenes.
Any idea how we further understand what's happening in this scenario?
Thanks for your help so far Alvin, it's really appreciated.
- alvinlau
Hi sberens! Do you have the WVD side-by-side stack installed on your session host? If so, what is the version? Meanwhile, let me set up a Windows Server 2016 and see if I can reproduce the issue on my side.
Thanks,
Alvin
alvinlau Good day!
When running qwinsta, there's a sessionname of rdp-sxs200326004 on the two Session hosts configured for the Host pool publishing the Apps used in our scenario.
An FYI that the Server 2016 instances were deployed from the Azure portal gallery, and are not custom images, if that helps.
Thanks again, and if you need anything else, please reach out.
Kind regards,
Sean
