Q: How do I install Limit Logins?
A: Do the following to setup Limit Logins:
  1. First, find an available Server which will store the Administrator Console files (a central location where all Net Admins can access). Any computer running Windows 98 or higher will work. We recommend using a Windows 2000 or higher computer.
  2. Create a share on the server (preferably a hidden share for extra security).
  3. Make sure you as the administrator has full rights to this directory and subdirectories. Everyone else who wishes to use the Administrator Console will also need full rights to this directory and subdirectories for information on setting the correct rights, see the Installation Instructions.).
  4. Download limitsetup.exe.
  5. Execute limitsetup.exe
  6. Specify the UNC path to the directory you created in step 2.
  7. After setup has completed, run LimitLogins.exe from the directory created in step 2.
  8. A setup box should appear if setup has not yet been run.
  9. Enter in all domains in your organization here.
  10. Save a policy for your desired groups and/or users.
  11. Each client will need to run RunLogins.exe from the server share you created each time they login. This can be achieved from executing RunLogins.exe from a group policy.

Q: How does Limit Logins enhance security?
A: The following are just some of the many security benefits of Limit Logins:
  • Allows the administrator to set the number of concurrent logins for each user.
  • A user can view every computer that he/she is logged into.
  • Administrators can view every computer that the users are logged into.
  • Ability to LogOff/Restart/Shutdown any computer from a central Console.
  • Can view logs of past user activity.
  • Ability to send email alerts when specified users Login, LogOut, reach their limit, etc.
  • Can set security sensitive user accounts to automatically logoff after a specified amount of time of being logged in.
  • Can set user accounts to LogOff, Restart, or Shutdown at any specified time.

Q: Can I test Limit Logins on only a few users?
A: Yes
Q: Does Limit Logins support multiple domains?
A: Yes
Q: What are the system Requirments for the Client Side?
A: On the client side, Limit Logins will run on any machine that has dotnet 2.0 installed. This includes newer operating systems such as Windows 7 and Windows Server 2008 R2 64 bit.
Q: Is there limited functionality on Windows 98 Machines?
A: Just one. When you send a Force LogOff command to a Windows 98 machine, it will force a restart instead of forcing the user to logoff. This is because Windows 98 can not handle a "Force LogOut" like the newer operating systems. Everything else works just fine.
Q: When the Administrator Console loads, I don't see any usernames in the list.
A: Please double check your DNS settings. Make sure you have a proper DNS entry on your computer. Also make sure you have a DNS suffix entry for each domain you administer. Also make sure you have administrative rights to the domain. If all of your settings are correct, try hitting the refresh button a couple of times.
Q: How long is my trial good for?
A: Your trial will be good for 30 days.
Q: One of my users can't log into a machine because it tells her that she is logged into another machine. That other machine is currently logged out. How can I fix this?
A: You have three options of fixing this problem. You can choose either one:
  • The user has the option (configurable) of clicking a remote logout to clear the connection.
  • Have the user log into the other machine, then logout. This will clear the connection for that user.
  • Using the Administrator Console, click the user, then click the computer account, then click the "clear connection" button to clear the connection.

Q: The client software wont run when specific users login.
A: Usually, when the client software wont run on a specific client, it is because a policy has not been defined in the Administrator Console. To do this, open the Administrator Console, click on the group or user you want the client software to run on, select the desired options, and click save. The client software should then run on the client computer when logging in.

Also the client software trial could be expired. Refresh your logs in the Administrator Console to see if your clients are reporting the trial has expired.
Q: When using the Administrator Console, clicking a user or all users does not show any computers being logged in.
A: If you clicked on a user or all users, and you know that they are logged in, then try the following steps to fix the problem:
  • Make sure the speedy use option is disabled (red shoes next to the user list).
  • Click the user, or all users button multiple times.
  • Close and restart the application, and try again.
  • Make sure that you saved a user policy for the user who is logging in. (ie. Click on the user in the admin console, configure settings, then click Save)
  • Make sure your clients execute the RunLogins.exe on the server in the same directory that is specified in the Admin Console.
  • Make sure that the clients have the proper rights to each directory in the server share. The rights can be found on the last page of the Install Guide. If they don't have rights exactly as it is specified, the computer will not show in the list.

Q: My email server requires a username\password in order to send email? Can I still send email notifications?
A: Yes
SonarWare.com - Frequently Asked Questions