Create your own win 2003 system login management tool

For the system, management needs to be done more than the application. Of course, we can manage the login or system by ourselves. But now there are software to help you achieve it. Why not? LimitLogin is Microsoft specifically for Windows Server. A tailor-made login management tool in 2003, which is very powerful, including limiting the number of user logins in the domain, classifying the login information of any user in the domain, integrating into AMD (Active Directory MMC) for management configuration, generating CSV and XML. Formatted login information, these functions are not very meaningful to ordinary users, but have a wide range of needs for business users, such as banks, libraries, ISP and other industries.

Download and Installation

At present, Microsoft has not provided an official website. The basic configuration requirements of this software are windows xp+.NET Framework 1.1 or Windows Server 2003. The advice given by Microsoft is Windows 2003 Domain. Controller and at least one Windows 2003 Domain Controller in the domain.

The installation process of LimitLogin is very complicated and is divided into the following steps:

1.Install LimitLogin Web Service

The name of the Web Service needs to be customized during installation. The default is WSLimitLogin. If you need to change, please be sure to remember, because this name will be used in Active Directory Setup, and you can also customize the port number for accessing the Web Service here.

2. Install LimitLogin Active Directory

After the LimitLogin Web Service starts running, you need to continue to install LimitLogin's Active Directory Setup and run the downloaded LimitLoginADSetup.msi. There are three checkboxes. If you are installing for the first time, please select all.

(1) Prepare your Active Directory Forest for LimitLogin. This option will do the following: update the configuration, join the LimitLogin AD MMC control menu; extend the Forest schema, including the LimitLogin class and properties.

Here, you need to have the Schema Administrator permission, then a dialog box will appear, click the "OK" button to confirm, the system will be in \\%windir%\\system32\\ and \\program files\\Limitlogin\\ A detailed log is created under the directory. After this step is completed, you can start configuring the domain to LimitLogin.

(2) Pepare your Active Directory Domain for LimitLogin. This option will perform the following operations: create and configure llogin.vbs, llogoff.vbs, limitlogin.wsdl and other files; create an application directory area for LimitLogin.

In the "Domain Setup" window shown in Figure 3, we need to provide the following three parameters: Scripts Share Folder name, shared area save script and wsdl file, all authenticated users will run under Limitlogin Must be able to access the shared area; IIS Server name, IIS machine name running LimitLogin Web Service; Name of LimitLogin Web Service, you know the reason you need to remember in the past!

This check box at the bottom of the window was originally configured for system installation. It is recommended to check it as well. Next, we need to create the LimitLogin application directory area. A dialog box will pop up. You can select the Domain Controller that needs to establish the LimitLogin application directory area in the drop-down list box. After successfully completing this step, it will display the installation of the Domain setup. The last tip.

(3) Install LimitLogin AD MMC add-in tools on this machine. This option will only run at the end, mainly to copy some files to the \\%windir% directory, where you can only run LimitLogin machines from Active Directory MMC. Later, if you want to run the LimitLogin AD MMC add-on tool, simply select "LmitLogin Tasks" in a user, machine or OU/Container right click.

It should be noted that you can run LimitLoginADSetup.msi to choose to install on the computer you want to use AD MMC integration function, or you can also click on "\\program files\\limitlogin\\LimitLoginADSetup.exe" Set with “/ForestPrep” and “/DomainPrep”.