Hello guys,
We consistantly encounter this effect on Windows 10 machines connecting to Windows Server 2016 Terminal Servers using the RDWEB gateway. When the client screen turns off the monitor to save power and the user comes back and presses a key, the last thing
on the screen of the RDS session is displayed and everything is frozen for a good few seconds before displaying the login screen of the Terminal Server. Very nice when people are doing back transfers or paying salaries.
This only happens on 2016 Terminal Servers when connecting through RDWEB and using a W10 client. Domain joined or not, it does not matter. Nothing is displayed in the logging of the RDS host, gateway, broker or client.
Also, this is not a limit by the Terminal Server policies, the auto logoff after disconnect and auto lock times are set to at least 10 minutes while I can reproduce this after 1 minute when setting the screen energy saving settings to 1 minute.
Can someone please point me into a direction? I seem to be the only person on earth who can consequently reproduce this. Also, we know that simply locking your session is the way to go, especially when leaving sensitive data on screen but you know how users are.
We have updates all our servers and W10 clients (1809) and have this on multiple, totally different locations using totally different internet connections, locations, policies etc. Nothing fancy but a simple RDS deployment and some Office apps are everything they have in common.