Limit Concurrent Logins on a Windows Server Based Network
UserLock allows organisations to prevent or limit concurrent logins to a Microsoft Windows Server based Network, per user or user group and per session type (workstation, terminal, interactive, VPN/RAS or IIS). Limitations can be set in a granular way and can vary from one user to another or one group to another.
Windows Concurrent Sessions Control
With UserLock you will be able to define and enforce the maximum number of:
- Concurrent workstations where a user can be logged on
- Terminal sessions that a user can open
- Simultaneous Wi-fi & VPN sessions that a user can open
- Simultaneous IIS sessions that a user can open
- Total sessions (of all kinds) that a user can open
Define a maximum limit for combinations of several kinds of sessions
You can for example set a custom limit to prevent the number of workstation sessions plus the number of Wi-fi & VPN sessions to being greater than one.
Administrators can also choose to either:
Allow users to remotely logoff an existing session
If the total number of allowed sessions has been reached, users can remotely close a previous session from the new login attempt. This forces an immediate logoff on the previous session but can mean unsaved documents are lost.
Grant users only a single (unlocked) active session
Distinguish between active and locked sessions. Here a user can open as many interactive sessions as they want but only one can be active at a time. With direct access to previous sessions protected through automatic locking, an administrator can increase the number of permitted user sessions whilst limiting or even preventing the number of concurrent logins allowed.