We recently switched from an ancient VMWare View implementation that gave our shop floor access to a piece of software to a more modern Server 2016 powered RDP/remote app version (running the same acient software). We replaced all of our old thin clients with new ones (HP t420) and, generally speaking, things are working well - with one exception.
Here's what works:
1) The thin client automatically connects to the RDP server and logs in as the right user/launches the program, logs in as the right user to the program
2) If the thin client is rebooted it automatically reconnects to the existing session when it comes back up
3) If the remote app is closed, the thin clients automatically reconnects, starts the program, logs in, etc
4) Nightly, both the remote apps server and thin clients automatically reboot so everything has a fresh start in the morning
Here's what doesn't work:
If the program is minimized, I need to manually sign out the remote user for the terminal to be useful again. When the program minimizes, there is no indication on the desktop of the thin client of how to bring it back up (or at least what you'd expect to work, the pop-out task-bar, doesn't work). If you reboot the thin client, it reconnects to the minimized session, still in the minimized state. The server still sees the connection as active, so it never times/signs out. This issue is resolved by the overnight reboot, but I can't in good conscience tell people to wait for that. So, a few times a day, from the RDP server, I need to manually sign out a couple users because one of the ~100 people on the shop floor accidentally[?] minimized the program. This isn't a big deal, just takes a few seconds, but it's massively frustrating that it happens at all. Product documentation and Googling have failed me so far. Maybe I'm not using the right terms?
Any help from fellow gerbils would be greatly appreciated. Thanks!