Anchor | ||||
---|---|---|---|---|
|
...
Install CHARON-VAX / CHARON-PDP together with Sentinel run-time (Sentinel run-time is an essential part of CHARON-VAX / CHARON-PDP for Windows distribution).
Reboot host system
- Connect HASP dongle to host system (in case of update of a license in a dongle)
Collect CHARON-VAX / CHARON-PDP host fingerprint file ("*.c2v"):
Open "License Update Service" utility:
Send the ".c2v" file ("Fingerprint.c2v" in the example above) to STROMASYS
STOMASYS will send you a ".v2c" file in return. Put it somewhere on the CHARON-VAX / CHARON-PDP host.
Open up the "License Update Service" utility the way described above and open the "Apply License File" tab:.
- In case of Software License installation and if there are already installed network-wide SL's in local network disable access to network licenses in the following way:
- Go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (ACC).
- Select "Configuration" option at the left panel, then "Access to Remote License Managers" tab.
- Uncheck the highlighted options:
- Press "Submit" button to apply settings
- Select "Network" tab.
- Switch "Network visibility" to "None":
- Press "Submit" button to apply setting.
- Do not forget to return these settings back after SL installation.
- Connect HASP dongle to host system (in case of update of a license in a dongle).
Collect CHARON-VAX / CHARON-PDP host fingerprint file ("*.c2v"):
Open "License Update Service" utility:
In the utility dialog popup open the "Collect Status Information" tab, then select:
"Installation of new protection key" (in case of Software License if no Software License has been installed on the host):
Example:
"Update of existing protection key" (in case of HL/HASP dongle or Software License that has been already installed on the host and needs updating):
Example:Note In case of HASP dongles use only "Update of existing protection key" option!
In case of Software License use "Installation of new protection key" option if host does not have Software License installed and "Update of existing protection key" option if already installed Software License has to be updated.
Press "Collect Information". In the popup dialog choose the place to store the "Fingerprint.c2v" file and press "Save":
Div class pagebreak A message should appear similar to this example, confirming the fingerprint has been collected successfully.
Send the ".c2v" file ("Fingerprint.c2v" in the example above) to STROMASYS
STOMASYS will send you a ".v2c" file in return. Put it somewhere on the CHARON-VAX / CHARON-PDP host.
Open up the "License Update Service" utility the way described above and open the "Apply License File" tab:
Div class pagebreak Press "..." button beside the "Update File" edit-box. In the popup select the license file received from STROMASYS:
Press the "Open" button and apply the license.Start any web browser on this system and go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (ACC).
Ensure that the license appears in the “
” menu.
In the utility dialog popup open the "Collect Status Information" tab, then select:
"Installation of new protection key" (in case of Software License if no Software License has been installed on the host):Example:
"Update of existing protection key" (in case of HL/HASP dongle or Software License that has been already installed on the host and needs updating):
Example:
Note |
---|
In case of HASP dongles use only "Update of existing protection key" option! In case of Software License use "Installation of new protection key" option if host does not have Software License installed and "Update of existing protection key" option if already installed Software License has to be updated. |
Press "Collect Information". In the popup dialog choose the place to store the "Fingerprint.c2v" file and press "Save":
Div | ||
---|---|---|
| ||
|
A message should appear similar to this example, confirming the fingerprint has been collected successfully.
Div | ||
---|---|---|
| ||
|
...
Disable remote keys access A helpful feature of Sentinel Admin Control Center is the ability to disable access to remote keys. If the network key is installed locally, access to the key from remote hosts can be disabled. The following examples demonstrate how this can be done.
To disable access to remote keys switch to the "Access to Remote License Managers" tab and uncheck the "Allow Access to Remote Licenses" checkbox. Then press the "Submit" button to apply this change:
To disable access to the locally installed license key from remote hosts switch to the "Access from Remote Clients" tab and uncheck the "Allow Access from Remote Clients" checkbox. Then press "Submit" button to apply this setting:
Back to Table of Contents
Div | ||
---|---|---|
| ||
|
...
Collect the specific information about the "RecipientHost" to issue a transfer license: run the "License Update Service" utility on the "RecipientHost" (see above), choose the "Transfer License" tab and pressthe "..." button adjacent to the "Save Recipient Information" edit-box:
In the popup choose a directory an file name for the recipient information.
Press the "Collect and Save Information" button to create the recipient information file.Div class pagebreak Copy the recipient file to the "SourceHost".
Info The recipient file is an ASCII file, so use "ascii" option in case of FTP transfer. On "SourceHost", run "License Update Service" utility, select "Transfer License" tab and the particular license to transfer in the big edit-box.Press the "..." button adjacent to the "Read the recipient information from file" edit-box, choose the just transferred recipient file, press the "Open" button.
Press the "..." button adjacent to the "Generate the license transfer file to" edit-box, choose the target directory and enter the desired name of the transfer file (*.h2h), then press the "Save" button.
Press the "Generate License Transfer File" button to create the license transfer file in the specified folder.Copy the resulting "*.h2h" file to the "RecipientHost".
Info "*.h2h" file is an ASCII file, so use the "ascii" option in case of FTP transfer. - On the "RecipientHost", apply the license transfer file ("*.h2h") the same way as a regular software license (see above).
- Start any web browser on the "RecipientHost" and go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (ACC).
- Ensure that the license appears in the “Sentinel Keys” menu.
Software License RemovalIt is also possible to remove a Software License completely from a host, the license will then be stored in a specific transfer license file "*.h2h", so it can be re-applied if needed.To remove a Software License completely from a host, follow the license transfer procedure described above. It is possible to use the fingerprint of the "SourceHost" (instead of the one from the "RecipientHost") for the transfer procedure"*.h2h", so it can be re-applied if needed.To remove a Software License completely from a host, follow the license transfer procedure described above. It is possible to use the fingerprint of the "SourceHost" (instead of the one from the "RecipientHost") for the transfer procedure.Back to Table of Contents
Cloned Software License Removal
In certain situations Software License may become "Cloned" (disabled). In this case the following procedure must be applied to remove the cloned license:
- Go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (ACC).
- In the "Sentinel HASP Admin Control Center" (ACC), locate the target "Sentinel SL AdminMode" license.
- Press the "Certificates" button at the right side of the SL description:
- Note the name of the correspondent certificate and path to the certificates base in the "Certificates" section:
- Remove the certificate file. In the example above the file to remove is "C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel LDK\installed\68704\387285561437702475_base.v2c".
- Reboot CHARON host
- Start "Sentinel HASP Admin Control Center" (ACC) again to ensure that the SL has been removed.
License Deinstallation
To completely remove a CHARON-VAX / CHARON-PDP license from a host, it is enough to remove the Sentinel run-time driver using the following procedure:
...