Copyright: ©Aladdin Knowledge Systems Ltd.


Aladdin Diagnostics


Aladdin Monitor

Hardlock modules and HASP keys for a network can be connected to any computers in the network. They are managed there by the local HL-Server software or the NetHASP License Manager and are made available within the network.

Aladdin Monitor permits centralized administration of the various HL-Server programs and the Hardlock modules they provide and/or the NetHASP License Manager and the NetHASP keys. Refer to Editing Settings for information on program settings for Aladdin Monitor.

NetHASP

The following options are available for HASP:

•	Checking the Properties of the NetHASP License Manager.

•	Checking NetHASP Keys.

•	Starting and Stopping NetHASP License Manager as a Service.

Refer to the help for NetHASP License Manager for background information on NetHASP.

Hardlock

The following options are available for Hardlock:

•	Checking and Editing the Properties of HL-Servers in the Network.

•	Checking, Adding and Removing Hardlock Modules.

•	Collecting and Importing Information for a License Update.

•	Installing, Starting, Stopping and Uninstalling the Local HL-Server Service

Refer to the following help topics for background information on Hardlock:

Searching for the License File

HL-Server Types and Possible Protocols

Questions and Answers for Hardlock in a Network


NetHASP License Manager

The following information about the selected NetHASP License Manager is displayed here:

•	General information about the selected NetHASP License Manager.

•	Information about the NetHASP keys being managed.

Note: NetHASP License Managers listening to NetBios only are currently not recognized by Aladdin Monitor.

Information about the NetHASP License Manager

Box	Meaning
Name	Name of the computer on which NetHASP License Manager is running.
Version	Version of the NetHASP License Manager.
IP	IP address of the computer
IPX	IPX address of the computer
OS/ Driver Versions	OS version and version of the installed HASP driver.
TCP/IP, IPX	Here, you can see which protocols are used.
Information about the NetHASP keys

Box	Meaning
HASP #	ID of the NetHASP key
NetHASP Model	Maximum possible number of licenses.
Current Stations	Stations currently logged in.


NetHASP Key

The HASP Information window displays

•	general information about the NetHASP key,

•	an overview of the programs,

•	an overview of logins for the individual programs.

HASP information

Box	Meaning
HASP #	Cumulative number of the NetHASP key.
Program table

Box	Meaning
Program No.	Number of the protected program.
Current Stations	Stations currently logged in.
Maximum Stations	Maximum possible number of stations.
Activations	Maximum number of program activations.
Login table

Box	Meaning
No.	Cumulative number of the login.
Login ID	ID number under which the station logged in.
Protocol	Protocol used.
Timeout	Time which must elapse without activity until the login entry is deleted.


Checking NetHASP Keys

In the left-hand part of the window, click the NetHASP key for which you want to check the login information.

Note: If the key is not displayed, first double-click the NetHASP License Manager which is making the key available, or refresh the view by selecting File/Rescan.

The NetHASP information is displayed in the right-hand part of the window.

See also

NetHASP Key Dialog Box


Checking the Properties of the NetHASP License Manager

In the left-hand part of the window, click the NetHASP License Manager for which you want to check the login information.

Note: If NetHASP License Manager is not displayed, first double-click the NetHASP LM folder or refresh the view by selecting File/Rescan.

The NetHASP License Manager information is displayed in the right-hand part of the window.

NetHASP License Managers listening to NetBios only are currently not recognized by Aladdin Monitor.

See also

NetHASP License Manager Dialog Box


Starting and Stopping NetHASP License Manager as a Service

The NetHASP License Manager service makes it possible to administer NetHASP keys on an NT workstation. You can use the Aladdin Monitor to start and stop the NetHASP License Manager service on the local computer.

To do this, select the appropriate function in the NetHASP LM or Services/HASP menu. Alternatively, you can use the context-sensitive menu for the NetHASP LM folder.

Starting the service

•	Select Start NetHASP LM Service in the Services/HASP or NetHASP LM menu. Alternatively, you can use the traffic light symbol [image].

The service is started and can now make available locally connected NetHASP keys within the network.

Alternatively, you can start the service using the context-sensitive menu. To do this, right-click the NetHASP LM folder and select Start NetHASP LM.

Stopping the service

•	Select Stop NetHASP LM Service in the Services/HASP or NetHASP LM menu. Alternatively, you can use the traffic light symbol [image].

The service is stopped. The view is then refreshed. This may take some time since it involves searching through the entire network.

Alternatively, you can stop the service using the context-sensitive menu. To do this, right-click the NetHASP LM folder and select Stop NetHASP LM.


Hardlock Server

The following information about the selected server is displayed here:

•	General information about the selected HL-Server.

•	Information about the Hardlock modules it manages.

•	Statistics about the sent data.

The following options are available:

•	Changing the active protocols

•	Adding Hardlock modules

•	Removing Hardlock modules

HL-Server information

Box	Meaning
Name	Name of the computer on which HL-Server is running.
Version	Version of the HL-Server software.
IP	IP address of the computer.
IPX	IPX address of the computer.
OS/Driver Versions	OS version and version of the installed Hardlock driver.
TCP/IP, IPX, NetBios	Active protocols. Here, you can specify which protocols should be used.
Changing protocols

You can influence which protocols the HL-Server uses, for example in order to limit the group of users for certain Hardlock modules.

Do this by activating or deactivating the corresponding protocol options.

Refer to the following help topic for information about the possible protocols: HL-Server Types and Possible Protocols.

Hardlock information

Box	Meaning
Module address	Address of the Hardlock module
Max. Logins	Maximum possible number of logins
Current	Current logins
Peak	Maximum number of logins since HL-Server started
Adding a Hardlock module

1.	Make sure that the Hardlock module you want to add is connected to the selected computer. If necessary, check whether the license file with the ALF extension is located in the correct folder. Refer to the following help topic: Searching for the License File.

2.	Specify the module address and select Add.

The module is added to the server and displayed in the table.

Removing a Hardlock module

Important: Removal may make it impossible to continue running programs which are logged on to the Hardlock module, resulting in a loss of data.

1.	In the table, select the Hardlock module which you wish to remove.

2.	Select Remove.

The Hardlock module is now no longer made available within the network by the HL-Server.

Important: All logins are deleted when you remove a Hardlock module.

Statistics

The statistics show the transferred data categorized according to the protocol used and the transfer direction, as well as faults which have occurred.


Hardlock Information

The Hardlock Information window displays

•	general information about the Hardlock module,

•	which licenses are being made available by the selected Hardlock module and which logins are active.

Hardlock information

Box	Meaning
Module address	Address of the Hardlock module
Port	Port to which the Hardlock module is connected.
Login table

Box	Meaning
No.	Serial number of the license. The table contains as many numbers as there are possible logins.
Login ID	ID number with which a computer has requested a license.
Task ID	ID number of the process which has requested the license. By checking the task ID, it is possible to prevent several licenses from being used up when the process is started more than once on the same computer.
Timeout	Time which must elapse without activity until the login entry is deleted.
Login time	Time when the license was requested.
Deleting entries from the login table

If the login table is full and no new licenses can be requested, you can use the Aladdin Monitor to remove logins from the table and thus permit new logins to be made.

Important: Deleting logins may prevent the user whose login you delete from continuing to run the protected program. This will result in loss of data. Consequently, only delete inactive logins which are in zombie mode.

1.	Select the entry you want to delete.

2.	Select Delete Entry.

3.	Confirm the prompt with Yes.

The entry is deleted from the table.


Checking and Editing the Properties of HL-Servers in the Network

Access to a Hardlock module in the network is controlled by the HL-Server software. The HL-Server administers the Hardlock module. You can use the Aladdin Monitor to control how the modules and logins are administered on the HL-Server.

You can do the following things:

•	Add new Hardlock modules to a server.

•	Remove Hardlock modules from a server.

•	Check and edit logins to a Hardlock module.

Adding a Hardlock module

1.	In the left-hand part of the window, click the server to which you want to add a Hardlock module.

Information about the server is displayed in the right-hand part of the window.

2.	Make sure that the Hardlock module you want to add is connected to the selected computer. If necessary, check whether the license file with the ALF extension is located in the correct folder. Refer to the following help topic: Searching for the License File.

3.	Specify the module address and select Add.

The module is added to the server and displayed in the table.

Removing a Hardlock module

Important: Removal may make it impossible to continue running programs which are logged on to the Hardlock module, resulting in a loss of data.

1.	In the left-hand part of the window, click the server from which you want to remove a Hardlock module.

Information about the server is displayed in the right-hand part of the window.

2.	In the table, select the Hardlock module which you wish to remove.

3.	Select Remove.

The Hardlock module is now no longer made available within the network by the HL-Server.

Alternatively, you can remove the Hardlock module using the shortcut menu. To do this, right-click the Hardlock module you want to remove and then select Remove from Server.

Checking login information

If the login table is full and no new licenses can be requested, you can use the Aladdin Monitor to remove logins from the table and thus permit new logins to be made.

Important: Deleting logins may prevent the user whose login you delete from continuing to run the protected program. This will result in loss of data. Consequently, only delete inactive logins which are in zombie mode.

1.	In the left-hand part of the window, click the Hardlock module for which you want to check the login information.

Note: If the module is not displayed, first double-click the HL-Server which is making the module available, or refresh the view by selecting File/Rescan.

The login information is displayed in the right-hand part of the window.

2.	Select the entry you want to delete and then select Delete Entry.

3.	Confirm the prompt with Yes.

The entry is deleted from the table.


Checking, Adding and Removing Hardlock Modules

Access to a Hardlock module in the network is controlled by the HL-Server software. The HL-Server administers the Hardlock module. You can use the Aladdin Monitor to control how the modules and logins are administered on the HL-Server.

You can do the following things:

•	Add new Hardlock modules to a server.

•	Remove Hardlock modules from a server.

•	Check and edit logins to a Hardlock module.

•	If necessary, gather information for updating a Hardlock module and load updates.

Furthermore, if you encounter problems, you can reset the server thread for individual Hardlock modules.

Adding a Hardlock module

1.	In the left-hand part of the window, click the server to which you want to add a Hardlock module.

Information about the server is displayed in the right-hand part of the window.

2.	Make sure that the Hardlock module you want to add is connected to the selected computer. If necessary, check whether the license file with the ALF extension is located in the correct folder. Refer to the following help topic: Searching for the License File.

3.	Specify the module address and select Add.

The module is added to the server and displayed in the table.

Removing a Hardlock module

Important: Removal may make it impossible to continue running programs which are logged on to the Hardlock module, resulting in a loss of data.

1.	In the left-hand part of the window, click the server from which you want to remove a Hardlock module.

Information about the server is displayed in the right-hand part of the window.

2.	In the table, select the Hardlock module which you wish to remove.

3.	Select Remove.

The Hardlock module is now no longer made available within the network by the HL-Server.

Alternatively, you can remove the Hardlock module using the shortcut menu. To do this, right-click the Hardlock module you want to remove and then select Remove from Server.

Checking login information

If the login table is full and no new licenses can be requested, you can use the Aladdin Monitor to remove logins from the table and thus permit new logins to be made. You can only delete logins on slot 0, the global license.

Important: Deleting logins may prevent the user whose login you delete from continuing to run the protected program. This will result in loss of data. Consequently, only delete inactive logins which are in zombie mode.

1.	In the left-hand part of the window, click the Hardlock module for which you want to check the login information.

Note: If the module is not displayed, first double-click the HL-Server which is making the module available, or refresh the view by selecting File/Rescan.

The login information is displayed in the right-hand part of the window.

2.	Select the entry you want to delete and then select Delete Entry.

3.	Confirm the prompt with Yes.

The entry is deleted from the table.


Collecting and Importing Information for a License Update

If you have Hardlock modules with different grades of license (HL-LiMaS), you can use the Aladdin Monitor for

•	gathering information for a license update (CTV data) which you can send to your software companies,

•	importing license updates (VTC data) received from the software company onto your Hardlock module.

Collecting information for a license update

1.	In the left-hand part of the window, click the Hardlock module for which you want to gather the update information.

Note: If the module is not displayed, first double-click the HL-Server which is making the module available, or refresh the view by selecting File/Rescan.

The login information is displayed in the right-hand part of the window.

2.	Select Update.

The Update dialog box opens.

3.	Select whether you want to export the CTV data into a file with the extension CTV or onto the clipboard.

4.	If you want to export the data into a file, select a folder in which you want to save the file.

Note: The default name contains the unique serial number of the Hardlock module. The manufacturer can use this number for definitively allocating the file. As a result, you should only change this name after contacting the software company.

5.	Click Create Update Information to store the data as a file or onto the clipboard. You can now pass the data on to the software company.

Importing a license update

1.	In the left-hand part of the window, click the Hardlock module into which you want to import an update.

Note: If the module is not displayed, first double-click the HL-Server which is making the module available, or refresh the view by selecting File/Rescan.

The login information is displayed in the right-hand part of the window.

2.	Select Update.

The Update dialog box opens.

3.	Select whether you have obtained the data from a VTC file or if you want it taken from the clipboard.

4.	Make sure that the license file with the ALF extension is in the correct folder because otherwise it cannot be updated. See the following help topic: Searching for the License File.

5.	Select Write License Update.

The data are applied to the Hardlock module and the license file, and the license data are updated.


Installing, Starting, Stopping and Uninstalling the HL-Server Service

The HL-Server Service makes it possible to administer Hardlock modules on an NT workstation. You can use the Aladdin Monitor to install, uninstall, start and stop the HL-Server service on the local computer.

To do this, select the corresponding option from the Service menu. Alternatively, you can use the shortcut menu for the HL-Server folder.

Installing the service

•	Select Install HL-Server Service in the Services/Hardlock or HL-Server Service menu.

The service is installed into the System folder of the local computer.

Alternatively, you can install the service using the shortcut menu. To do this, right-click the HL-Server folder and select Install HL-Server.

Starting the service

•	Select Start HL-Server Service in the Services/Hardlock or HL-Server Service menu. Alternatively, you can use the traffic light symbol [image].

The service is started and can now make available locally connected Hardlock Server modules within the network.

Note: If necessary, check whether the license file with the ALF extension is located in the correct folder. Refer to the following help topic: Searching for the License File.

Alternatively, you can start the service using the shortcut menu. To do this, right-click the HL-Server folder and select Start HL-Server.

Stopping the service

•	Select Stop HL-Server Service in the Services/Hardlock or HL-Server Service menu. Alternatively, you can use the traffic light symbol [image].

The service is stopped. The view is then refreshed. This may take some time since it involves searching through the entire network.

Alternatively, you can stop the service using the shortcut menu. To do this, right-click the HL-Server service and select Stop Server.

Removing the service

1.	Stop the service with Stop HL-Server Service in the Services/Hardlock or HL-Server Service menu.

2.	Select Remove HL-Server Service in the Services/Hardlock or HL-Server Service menu.

The service is removed from the System folder.

Alternatively, you can remove the service using the shortcut menu. To do this, right-click the HL-Server folder and select Remove HL-Server.


Searching for the License File

HL-Server searches for the license information in the folder in which HL-Server is itself located, usually the system folder. If the Hardlock module is searched locally first, the file is searched in the same folder as the protected application. The search behavior can be altered by specifying an environment variable.

Under Windows NT/2000

You need to be logged in as an administrator to set system variables.

1.	Select System/Environment (Windows NT) or System/Advanced/Environment Variables (Windows 2000) in the Windows Control Panel.

2.	Enter HL_LICENSEDIR as the Variable and the required folder as the Value.

Note: You can only specify local folders for the service because the HL-Server service cannot access other folders via the network.

3.	The changes take effect next time the service is started.

HL-Server then searches the specified folder looking for files with the ALF extension (Aladdin License File). It detects the correct license by means of the correlation with the serial number.

Under Windows 95/98/ME

Under Windows 95/98/ME you can set the environment variable in the file AUTOEXEC.BAT. This file is usually in the root directory C:\.

1.	Open the AUTOEXEC.BAT file.

2.	Specify the environment variable as follows:

SET HL_LICENSEDIR=[directory]

Example

SET HL_LICENSEDIR=C:\MYAPP\LICENSE

3.	Save the changes.

The changes take effect next time the computer is started.

HL-Server then searches the specified folder looking for files with the ALF extension (Aladdin License File). It detects the correct license by means of the correlation with the serial number.

See also

Questions and Answers for Hardlock in a Network


Editing Logins

If the login table is full and no new licenses can be requested, you can use the Aladdin Monitor to remove logins from the table and thus permit new logins to be made. You can only delete logins on slot 0, the global license.

Important: Deleting logins may prevent the user whose login you delete from continuing to run the protected program. This will result in loss of data. Consequently, only delete inactive logins which are in zombie mode.

1.	In the left-hand part of the window, click the Hardlock module for which you want to check the login information.

Note: If the module is not displayed, first double-click the HL-Server which is making the module available, or refresh the view by selecting File/Rescan.

The login information is displayed in the right-hand part of the window.

2.	Select the entry you want to delete and then select Delete Entry.

3.	Confirm the prompt with Yes.

The entry is deleted from the table.


HL-Server Types and Possible Protocols

HL-Server can be run under various operating systems. Refer to the following table to see which type of HL-Server you need for which operating system and which protocols are supported.

Possible server protocols

Operating system	HL-Server software	Protocols
DOS	HLSERVER.EXE	IPX, NetBios
OS/2	HLSERVER.EXE	IPX, NetBios
Netware 3.1x, 4.xx	HLSERVER.NLM	IPX, TCP/IP
Windows 3.1x	HLSERVER.EXE	IPX, NetBios
Windows 95/98	HLS32.EXE	IPX, TCP/IP, NetBios
Windows NT 3.51, 4.0, 2000	HLS32SVC.EXE	IPX, TCP/IP, NetBios
Possible client protocols

The following protocols are possible for the client which wants to access the Hardlock module via HL-Server:

Protocol	DOS	W16	W32
IPX	x	x	x
NetBios	x	x
TCP/IP		x	x


Questions and Answers for Hardlock in a Network

Search sequence for protocols

When using the 32-bit HL-Server for Win95 or Windows NT, please bear in mind that the search sequence of the protocols (if you are not using HL_SEARCH) depends on the client. Thus:

• 16-bit search sequence: IPX, NetBios, IP

IP is searched last in order to change the former behavior as little as possible.

• 32-bit search sequence: IP, IPX

IP is searched first since this search is generally considerably faster than via IPX or NetBios.

Search sequence for IP addresses

•	Environment variable HLS_IPADDR

•	If no environment variable has been defined, the search takes place via DNS or HOSTS for the station HLSERVER.

•	If no address has been found, the search takes place via broadcast (255.255.255.255) in the local sub-network.

To transfer IP packets, Winsock calls are used with a corresponding (16 or 32 bit) WINSOCK.DLL. Please note that during installation many Internet clients install their own WINSOCK.DLL (CompuServe, AOL, T-Online). In this case, accessing IP can cause the Internet service provider to be dialed if the HL-Server is not found via IPX and NetBios. You then need to exclude IP from the search with the following command:

SET HL_SEARCH=IPX,NetBios

The environment variable HLS_IPADDR has been introduced in order to optimize the search via the TCP/IP protocol. With it, one or more IP addresses or names can be specified. However, if several addresses are specified at the same time – in contrast to HL SEARCH – you cannot predict which of the specified HL-Servers will ultimately be used.

Example

SET HLS_IPADDR=192.9.209.17,luzie.aladdin.de

HLS IPADDR can also be used to specify broadcast addresses if required:

SET HLS_IPADDR=192.9.209.255,192.9.201.255

Since IP networks generally have considerably greater differences in propagation time than IPX networks (e.g. WAN routes), the limits for timeouts and retries for the clients must be set fairly generously. The default values are set so that the HL-Server should be found with an existing 64 kbit connection.

• SET HLS_WAIT=

Sets the waiting time between two retries, in milliseconds

Default TCP/IP: 1000, IPX: 200

min. 200

max. 30000

• SET HLS_RETRIES=

Sets the number of retries until the DONGLE_NOT_FOUND message is returned

Default 5

min. 2

max. 30

Note: The defaults vary, however SET HLS_WAIT changes the values for both IPX and TCP/IP.


Hardlock Information (Slots)

The Hardlock Information window displays

•	general information about the Hardlock module,

•	which licenses are made available by the selected Hardlock module,

•	which logins are available for the individual slots.

Here, you can

•	collect and import information for a license update,

•	delete login entries.

Hardlock information

Box	Meaning
Module address	Address of the Hardlock module.
Port	Port to which the Hardlock module is connected.
RUS ID	Serial number of the Hardlock module.
License information

Box	Meaning
Slot	Slot number. Slot 0 designates the global license.
Licenses	Number of possible licenses for this slot.
Used	Number of currently used licenses for this slot.
Peak	Maximum number of licenses which can be used for this slot.
Exp. Date	Expiration date for this slot.
Counter	Current counter value for this slot (only slot 0).
Max. Counter	Maximum possible counter value for this slot (only slot 0).
Collecting information for a license update

1.	Select Update.

The Update dialog box opens.

2.	Select whether you want to export the CTV data into a file with the extension CTV or onto the clipboard.

3.	If you want to export the data into a file, select a folder in which you want to save the file.

Note: The default name contains the unique serial number of the Hardlock module. The manufacturer can use this number for definitively allocating the file. As a result, you should only change this name after contacting the software company.

4.	Click Create Update Information to store the data as a file or onto the clipboard. You can now pass the data on to the software company.

Importing a license update

1.	Select Update.

The Update dialog box opens.

2.	Select whether you have obtained the data from a VTC file or if you want it taken from the clipboard.

3.	Make sure that the license file with the ALF extension is in the correct folder because otherwise it cannot be updated. See the following help topic: Searching for the License File.

4.	Select Write License Update.

The data are applied to the Hardlock module and the license file, and the license data are updated.

Login table for a slot

Box	Meaning
No.	Number of the login. The table contains as many numbers as there are possible logins.
Login ID	ID number with which a computer has requested a license.
Task ID	ID number of the process which has requested the license. By checking the task ID, it is possible to prevent several licenses from being used up when the process is started more than once on the same computer.
Slot	Number of the license. In this case, slot 0 stands for the global license.
Timeout	Time which must elapse without activity until the login entry is deleted.
Login Time	Time when the license was requested.
Deleting entries from the login table

If the login table is full and no new licenses can be requested, you can use the Aladdin Monitor to remove logins from the table and thus permit new logins to be made. You can only delete logins on slot 0, the global license.

Important: Deleting logins may prevent the user whose login you delete from continuing to run the protected program. This will result in loss of data. Consequently, only delete inactive logins which are in zombie mode.

1.	Select the entry you want to delete.

2.	Select Delete Entry.

3.	Confirm the prompt with Yes.

The entry is deleted from the table.


Settings

Note: All changes only become active after the program is restarted.

Box	Meaning
Language	Select which language is used.
Dialog refresh cycle	Select how often the view should be updated  (1-300 seconds).
Server scan cycle	Select how often the server information should be updated (1 - 60 minutes).
Use Hardlock mode	This option is grayed out if Hardlock mode is not possible. If it is possible, you can select whether to use it or not.
Use HASP mode	This option is grayed out if HASP mode is not possible. If it is possible, you can select whether to use it or not.
Use NETHASP.INI	Use this option to optimize searching for the NetHASP key by using NETHASP.INI. Refer to the help for NetHASP License Manager for information on NETHASP.INI.
See also

Editing Settings


Editing Settings

You can adapt the following program settings to meet your requirements:

•	The language used (German or English).

•	The refresh frequency for the dialog box (default setting every 2 seconds).

•	The frequency of network queries (default setting every 3 minutes).

•	If you want to use the Hardlock mode, the HASP mode or both.

You can make the changes in File/Settings. They only become active after the program is restarted.

See also

Settings Dialog Box


Resetting the Server Thread

You can reset the server thread if you are having problems with individual Hardlock modules and you are unable to understand what has happened.

Note: All logins are deleted when you reset the server thread. This can lead to users losing data. As a result, you should only use this option as a last resort.

1.	Right-click the Hardlock module for which you want to reset the server thread and select Remove Server Thread.

2.	Confirm with Yes.

The server thread is reset.


Update

If you have Hardlock modules with different grades of license (HL-LiMaS), you can use the Aladdin Monitor for

•	collecting information for a license update (CTV data),

•	importing license updates (VTC data) received from the software company onto your Hardlock module.

Collecting information for a license update

1.	Select whether you want to export the CTV data into a file with the extension CTV or onto the clipboard.

2.	If you want to export the data into a file, select a folder in which you want to save the file.

Note: The default name contains the unique serial number of the Hardlock module. The manufacturer can use this number for definitively allocating the file. As a result, you should only change this name after contacting the software company.

3.	Click Create Update Information to store the data as a file or onto the clipboard. You can now pass the data on to the software company.

Importing a license update

1.	Select whether you have obtained the data from a VTC file or if you want it taken from the clipboard.

2.	Make sure that the license file with the ALF extension is in the correct folder because otherwise it cannot be updated. See the following help topic: Searching for the License File

3.	Select Write License Update.

The data are applied to the Hardlock module and the license file, and the license data are updated.