Understanding User Sessions and Remote Desktop on Windows

When you use Remote Desktop to log in to a remote computer using the same account you would use if you were standing in front of it, how does that affect the user's session and login status?

Windows Logon and Remote Desktop

If you log into a remote computer using Remote Desktop with the same account you use to log in locally, the result is that your local computer will lock up and display the login screen, similar to what happens when you press the Win L keys. This is a default behavior for most versions of Windows, where only one user can be logged in at a time.

Windows Server and Remote Desktop

On Windows Server, however, it's possible to log in with a different account, keeping the local account logged in as well. This is an important point for IT administrators who need to manage multiple users or multiple sessions simultaneously. It's a functionality not available on non-server versions of Windows, which are designed to support only a single active user session.

Effects on User Sessions

Session Locking

When you close a Remote Desktop session, the desktop will be locked. This locking effect is consistent with the behavior of locking the local screen with the Win L keys. On Windows Server, there is the possibility to connect to the console session even if you have closed the remote desktop session. However, on desktop versions of Windows, your actions will not be visible to anyone watching the physical console.

Security Implications

It's important to understand that if you close a Remote Desktop session, anyone who walks up to the physical console can assume the user's identity, as long as the local computer is not locked. This highlights the importance of locking the local screen when you're not in use, whether you're using Remote Desktop or not.

Modifying User Session Behavior

It is possible to make changes to the user session behavior of Remote Desktop, but doing so would violate the Windows license agreement. This is another reason why such modifications are not recommended and could lead to system instability or security vulnerabilities.

Conclusion

When you use Remote Desktop to log in with the same account as the one logged into the physical console, the local session will lock. The server versions of Windows allow for more flexible session management, enabling multiple user sessions simultaneously. Closing a Remote Desktop session will lock the desktop and any actions you perform on the remote session are not visible on the physical console.

Keywords

Remote Desktop Windows Logon User Sessions Security Lock Screen

Note: This article is intended for educational purposes and should not be used to circumvent the Windows licensing terms.