10.2.8. Installing HASP License Manager

<< Prev   Next >>

10.2.8.1. On Windows

The 1C:Enterprise application includes the lmsetup.exe utility used to install the HASP License Manager. The utility is located on the 1C:Enterprise installation disk. You can start it either directly from the command line or through the 1C:Enterprise installer menu.

You can install HASP License Manager on any computer on a local network running Microsoft Windows operating systems. At the same time, you can install HASP License Manager in any of these systems as an ordinary application. In Microsoft Windows 2000 or later, you can also install it as a Windows service.

To install the HASP License Manager, start the lmsetup.exe installation program (the following is an example of installing the HASP License Manager version 8.32).

Fig. 68. Language selection

Then select English for the installation (see fig. 68).

Next, confirm that you accept the proposed license.

Fig. 69. License acceptance

If you install the HASP License Manager on a computer running Windows 2000 or later, you will be offered two options for installing the HASP License Manager: as an application (Application) or as a service (Service). If you install the HASP License Manager on a computer running Windows 98/Me, this dialog box will be skipped since only the application can be installed on these operating systems.

Next, you will be prompted to select a directory where the HASP License Manager executable files and the help file will be placed. If you install the HASP License Manager as a Windows service, the executable files will be placed in the Windows system directory, and only the help file will be installed in the selected directory.

At the next step of the installation, you will be prompted to select a group in which the shortcuts for starting the HASP License Manager and the help file will be placed. By default, a new group is created with the name HASP License Manager, but you can select an existing group or change the name of the group being created.

If you install the HASP License Manager as a Microsoft Windows application, you will be prompted to place the HASP License Manager shortcut in the Startup directory. In this case, the HASP License Manager will start automatically when the operating system boots. If you choose the other option, you will have to start the HASP License Manager manually.

At the next step, it is proposed to install the HASP Device Driver, which is necessary for the normal operation of the HASP License Manager. Using this driver, the HASP License Manager interacts with the HASP4 Net USB dongle. If the HASP Device Driver has already been installed on the computer, then reinstalling the HASP License Manager is not required.

After the installation process is complete, you will be prompted to start the HASP License Manager. If you refuse, you can start it later manually. Procedures for starting the HASP License Manager for various installation options are described below.

10.2.8.1.1. Starting HASP License Manager as Microsoft Windows application

If the HASP License Manager was installed as a Microsoft Windows application, it is started by running the program file nhsrvw32.exe, which is placed on the hard drive of the computer by the HASP License Manager Setup program.

When you run nhsrvw32.exe from a command line, you can set the parameters, by which HASP License Manager can be more “instructed” about using a particular network protocol for interaction with the protected programs.

Note that configuring network protocols makes sense only when the default mode of using the network protocols causes unstable operation or there are serious delays in running protected programs.

Each parameter is preceded with "-" or "/". Example:

nsrvw32 -tcpip

Or:

nsrvw32 /tcpip

When you start the nhsrvw32.exe program, the following parameters can be used.

Specifies where to save the haspaddr.dat file. By default, the file is saved in the directory where the HASP License Manager was downloaded.

Instructs the HASP4 Net application to use the IPX protocol with SAP.

Instructs the HASP4 Net application to use the IPX protocol without SAP. When using the HASP License Manager for Win32, other protocols can be loaded using the-tcpip or -netbios commands. In this case, the HASP License Manager creates a newaddr.dat file that contains the address of the station where the HASP License Manager is running. When you download the HASP License Manager with one of these keys, only those protected applications that have access to the newaddr.dat file will be able to exchange data with it.

Use this parameter if you want to change the socket that is used to exchange data with HASP License Manager. The default socket is 7483 (hex value).

Use this parameter if you want the HASP License Manager to serve the stations exclusively on the local network. If the HASP License Manager receives requests from workstations that are not on the local network, they get error code 140.

Assigns a NetBIOS name to the HASP License Manager. The parameter action is identical to -nethaspnb name.

This parameter allows you to use the HASP4 Net application only with NetBIOS protocol. When using the HASP License Manager for Win32, other protocols can be loaded using the -tcpip or -ipxnosap commands.

If you use TCP/IP, this parameter allows you to specify a network port that will use the HASP License Manager. The default port is 475.

Assigns one or more IPX, TCP/IP, or NetBIOS names to the HASP License Manager. A maximum of 6 names can be assigned.

This parameter allows you to use the HASP4 Net application only with TCP/IP protocol. When using the HASP License Manager for Win32, other protocols can be loaded using the -ipx or -netbios parameters.

Instructs HASP License Manager to operate with specific communication channel numbers.

Limits the number of users serviced by the HASP License Manager. The default value is 250.

10.2.8.1.2. Running HASP License Manager as a Microsoft Windows service

You can start HASP License Manager as a Microsoft Windows service only if it was installed to operate as a service. As noted above, this is possible only in the environment of Microsoft Windows 2000 or later.

When you install HASP License Manager as a Microsoft Windows service, it is installed as a startup, that is, HASP License Manager will start every time you start Microsoft Windows.

If necessary, you can change the startup settings of the service and start and stop it manually.

To start, stop, and configure HAPS License Manager manually, click Start – Setup – Control Panel – Administrative Tools – Service (Start – Control Panel – Administrative Tools – Services). In the list of services that appears, find the HASP Loader service and right-click it. Through the context menu that appears, you can perform all the necessary actions with the service.

10.2.8.2. On Linux

Download HASP License Manager for Linux before proceeding with the installation. For the download hyperlink, see article General information. HASP License Manager also requires you to install HASP Device Driver. For the download hyperlink, see article General information.

To install the HASP License Manager, perform the following steps (actions must be performed as administrator):

• Copy the downloaded file to the directory where the HASP License Manager will be located (for example,/opt/hasplm).
• Unpack the archive by executing the command:

tar xzf hasplm_linux_8.30.tgz

• Add the HASP License Manager starting command (before exit 0 command) to the /etc/rc.local file from the directory where it was unpacked:

/opt/hasplm/hasplm

Adding a command to the rc.local file will cause the HASP License Manager to start automatically when the system restarts.

• Start HASP License Manager by executing the command:

hasplm

If you want to configure the HASP License Manager using the nhsrv. ini configuration file (see article nhsrv.ini), specify the path to the configuration file in the HASP License Manager command line:

/opt/hasplm/hasplm -c /etc/nhsrv.ini

10.2.8.3. Configuring the HASP License Manager with a configuration file

You can specify some HASP License Manager settings using the nhsrv.ini configuration file (see article nhsrv.ini).

If you are using keys with a lot of user licenses (for 300, 500, and 1,000 users), please pay attention to the NHS_USERLIST parameter when configuring HASP License Manager.

<< Prev   Next >>