You could enforce this limitation using the Technet scriptLimit concurrent logins in Active Directory,further detailed in the articleActive Directory: Limit concurrent user logins,using logon and logoff scripts with a file used as lock.
There is no default option in active directory let you to avoid a user to logon on many machine in same time. you can create a custom solution to trace the user logon and logoff by creating a shared file when a user logon. Then you create a GPO to launch a a script when user logon and another script when he logoff to update this file and check if the user is already logged when he try to logon:
Hi, As @BOURBITA Thameur and @udara peiris mentioned , to Limit concurrent user logins, the logon script should be considered. For deploying this step by step, refer to the link provided by udara. Please feel free to let us know if you need further assistance. Best Regards,
This process creates in the C:\program files\limitlogin folder the LimitLoginMMCSetup.exe utility, which, when run, integrates LimitLogin directly into the AD Users and Computers snap-in, providing a new LimitLogin Tasks context-menu option. This option opens the LimitLogon configuration for the user, which displays the current sessions, as the figure shows. (You'll need LimitLogin installed on each machine that runs Active Directory Users and Computers. To do so, execute the LimitLoginADSetup.msi file and during the setup options, select the "Install LimitLogin Active Directory MMC snap-in integration tools on this machine" option).
LimitLogin also provides a script--Bulk_LimitUserLogins.vbs--that lets you define quotas for all users in the domain. If you want to use this tool simply to see logged-on sessions, give users a high quota limit (without quotas enabled no user-session tracking occurs) that they'll never reach.
Limiting concurrent logins is not currently supported in Azure Active Directory. One workaround is that you could limit the login hour for the user, or you could enable Multi-Factor Authentication(MFA) to enhance the login security level and reduce the login risk. For example, once you enable MFA, you could require the user who is logging in to confirm by using a phone call or text code after entering the user password. This will have the same effect of restricting multiple users from sharing an account. (It won't prevent this fully, but it will make it more tedious to do.)
The ability to prevent or limit concurrent or multiple logins, averts one of the most potentially dangerous situations for a Windows Active Directory network. UserLock controls concurrent sessions and sets limitations in a granular way according to user, user groups, organizational units and session types.
There are legitimate reasons why concurrent logins are desirable, however, both from a user experience (UX) and an educational perspective. The student may find it more convenient to use two or more devices. They could be using a second device to look at the course materials for their work on a given research project, workshop, or assignment. For example, a language course may offer supplementary documents, like conjugation tables, that they can access from the app handily.
Safeguarding the integrity of a learning environment is a multi-pronged exercise that may be spearheaded by an LMS admin or a security manager, but one that only has realistic odds of success through a community approach. It consists of an active process that keeps design and development, rules and procedure, user education, and auditing steps up to date.
To enable the feature, uncheck Unlimited session per user checkbox, which is checked by default. In the Maximum per user Sessions field configure number of sessions specific user can have on each PSN. In this example, it is set to 2.Users from External Identity Sources (for example Active Directory) are affected by this configuration as well.
Bob is the username of an account from the Active Directory Domain which is connected and joined to ISE server. User Maximum Sessions is configured with value 2, which means that any session for same user beyond this number is not permitted (per PSN). As shown in the image, user Bob connects with Android Phone and Windows machine with the same credentials:Both sessions are permitted because maximum sessions limit is not exceeded. As per the detailed Radius Live log, shown in the image:
In order to limit the Guest Access, you can specify the Maximum simultaneous logins in the Guest Type configuration.Navigate to Work Centers > Guest Access > Portal & Components > Guest Types and change Maximum simultaneous logins option, as shown in the image:
As per the Radius Live-logs, the Guest1 is always correctly authenticated in terms of the portal authentication, once WLC sends the RADIUS request with the second session for the Guest1, ISE denies the access because of exceed user limit:
This failure reason indicates that Group User Max Sessions limit is exceeded for this session/user.The check of MaxSession cache happens after Authorization Profile selection:Success:Failure:
EZproxy can limit the number of times that a single username can be used to log in. When a user logs in more than the specified number of times, the new user session is allowed access, but the oldest user session is locked out from further access. By locking out the oldest session instead of the newest session, EZproxy avoids locking out a user who logs in, closes all browser windows, relaunches, and logs in again.
If a user tries to access EZproxy from a session that has been disabled due to excessive logins, EZproxy sends the file limit.htm from the docs directory to the user. There is no template for this file. See Error Pages for information on special variables that can appear in this file to customize the error sent to the user.
If you use CGI authentication, your script must provide EZproxy with usernames either through the loguser mechanism or in the user mechanism of a ticket. If your script does not provide a username, EZproxy will see all users as accessing from the same username and will impose the limit across all users.
In this example, guest and those users that appear in the extra.usr file have unrestricted logins, FTP users of ftpserv.yourlib.org have only a single login, and IMAP users of imapserv.yourlib.org have five logins.
In large domains, using the LogonWorkstations user attribute to restrict user access to computers is inconvenient because of limitations and lack of flexibility. You can use Group Policy to implement a more flexible way to allow or deny local logins.
For Maximum session duration in minutes, choose the maximum amount of time that a streaming session can remain active. If users are still connected to a streaming instance five minutes before this limit is reached, they are prompted to save any open documents before being disconnected. After this time elapses, the instance is terminated and replaced by a new instance. The maximum session duration that you can set in the AppStream 2.0 console is 5760 minutes (96 hours).
For Idle disconnect timeout in minutes, choose the amount of time that users can be idle (inactive) before they are disconnected from their streaming session and the Disconnect timeout in minutes time interval begins. Users are notified before they are disconnected due to inactivity. If they try to reconnect to the streaming session before the time interval specified in Disconnect timeout in minutes has elapsed, they are connected to their previous session. Otherwise, they are connected to a new session with a new streaming instance. Setting this value to 0 disables it. When this value is disabled, users are not disconnected due to inactivity.
After you select Enable Google Drive, type the name of at least one organizational domain that is associated with your G Suite account. Access to Google Drive during application streaming sessions is limited to user accounts that are in the domains that you specify. You can specify up to 10 domains. For more information about requirements for enabling Google Drive, see Enable Google Drive for Your AppStream 2.0 Users.
After you select Enable OneDrive, enter the name of least one organizational domain that is associated with your OneDrive account. Access to OneDrive during application streaming sessions is limited to user accounts that are in the domains that you specify. You can specify up to 10 domains. For more information about requirements for enabling OneDrive, see Enable OneDrive for Your AppStream 2.0 Users.
More than one authentication plugin may be enabled. Any authentication plugin can be used to find a username/password match. Once found, a user is logged in and alternative plugins are not used. Therefore the plugin which handles the most logins should be moved to the top of the page in order that less load is put on authentication servers.
By default, there is no limit to the number of concurrent browser logins. (If a user is concerned about this, they can view their Browser sessions page.) This setting allows you to specify how many concurrent browser logins are allowed. Once the limit is reached, the oldest session will be terminated. Note that this does not work with Single sign on plugins.
If a user exceeds this limit, they receive an HTTP 429 error response without affecting other users in your org. A message is written to the System Log that indicates that the end-user rate limit was encountered.
API endpoints that take username and password credentials, including the Authentication API and the OAuth 2.0 resource owner password flow, have a per-username rate limit to prevent brute force attacks with the user's password:
The values in this article indicate the limits of a single Citrix DaaS (formerly Citrix Virtual Apps and Desktops service) instance. When the number of concurrent users exceeds 125,000, Citrix can scale and combine multiple Citrix DaaS instances, to deliver a unified experience at any scale. 2b1af7f3a8