Please note that in an organization with a very high quantity of users (for example greater than 10000) it is unlikely to have that many connections during the same minute. You can authenticate 6,000 users in one minute. UserLock can process up to 100 logon events/s. The required hardware for a UserLock server depends on the number of userĪ medium-sized server should be sufficient in most cases - a server withĪ 2 GHz dual core CPU, 2 GB of RAM available and a recent hard drive shouldīe able to manage up to 10,000 simultaneous sessions.
In the registry key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters", the two following values (REG_DWORD) should be set to 1: "AutoShareWks" and "AutoShareServer". The following registry change is required in order to activate this share: The Impersonation account must be able to access the administrative share of each machine "\\machinename\admin$" where the Desktop agent is installed. Sharing' protocol (SMB TCP 445) must be authorized both waysīetween the UserLock server and the machines protected by UserLock. Must be authorized both ways between the UserLock server and the machines For some operations, the UserLock service needs to impersonate with an account having administrative privileges on target machines ( see here). To logon by default as the 'Network Service' account. Registry service must be enabled and started on machines protected ** 9.8.2.0 is the latest version for the Desktop UserLock agent with the GINA technology. The ability to remotely close sessions (if session limit is reached).* The following features are not available (as they require a desktop displayed during the session): Any terminal servers using RDP sessions (Microsoft) or ICA sessions (Citrix)
0 kommentar(er)
