Situation
Our engineering group generates new Windows VMs from a template that uses a generic admin user. Through the course of a project that user is used in multiple, parallel sessions by several engineers that are making modifications to code or configuration.
Most engineers utilize the old Microsoft RDP Terminal (mstsc) or the new Windows 10 Microsoft Remote Desktop Application (version 10.2.1810.0). Some use VMware Remote Client.
Issue
When sessions are left open another user may log in and inadvertently take over another person's active session with in progress changes and notes.
Note: This issue is observed from all methods.
Workarounds
- When it's 2 people, one user disconnects and the other launches task manager to connect over to their desired session. More than 3 people means a discussion determining who is on what session.
- Save their active files and continue using the session as is.
Desired Solutions
- Locking down sessions by client name or prioritize client name for session re-entry. Users tab of Windows Task Manager with same user for multiple sessions
- Ability to create ad-hoc new sessions when landing in to someone else's session inadvertently.