Beruflich Dokumente
Kultur Dokumente
The new V10 security has a new physical security key (SafeNet HL DL) and a different way of applying
license updates compared to previous versions of AccuMark Family software. Security updates have
been made for AccuMark, AccuNest, AccuScan and MTM family of products.
Refer to the document AccuMarkV10Security for details about standalone
licensing. Briefly standalone (single user) and Network keys are available. The
standard green key is for the single user.
Network licensing allows you to have one key on a system and have your users use the license server for
their security access for AccuMark applications. The network key can be used instead of having
standalone keys on each users workstation.
Network or concurrent keys come in 3 varieties: all are red in color but come in
different allotments of 1 to 10 users, 1 to 50 users, and 1 to 250 users. The
license file that is applied to the network key further restricts the number of
users. For example, you need to have a network key for 30 users. Thus you
would need to use the network key that allows 11 50 users with a license that
is good for 30 users.
V10 AccuMark and other Gerber Products will use different keys for now
Previously different Gerber products were all able to use the same SafeNet USB black security key and
use the Install License application to apply each of the different licenses, including for AccuMark
software prior to V10, Cutworks, and Cutter software.
Now, because of the V10 security updates, if you have more than one Gerber product like those
mentioned above, you will now need to have two security keys in order to run your applications; one for
the new V10 AccuMark Family software and one for the existing Cutworks and/or Cutter software.
Continue to use Install License for AccuMark Family V9 and earlier versions of software as well for the
Cutworks and Cutter software.
Page 1 of 18
Station: Each login request for a single machine is counted as an instance (default)
Login: Each login request is counted as an instance
Process: Each login request for a single process is counted as an instance
In the network key contents details, you will see the number of concurrent instances for one or more
Features. This value specifies the number of instances of simultaneous usage that the license allows on
the customers network. Concurrent instances may relate to the network, processes, or machines.
Page 2 of 18
Sentinel License Manager contains an automatic function that identifies instances where a network
protection key and the relevant protected application (on separate computers) have become
disconnected. License Manager handles this situation as follows:
If both computers contain active instances of License Manager, but the protected application
fails, License Manager on the computer that hosts the network protection key immediately
closes the session and frees the network seat for re-use.
If only the computer that hosts the network protection key contains an active instance of
License Manager, the session times out after three minutes. At that point, License Manager
frees the network seat for re-use.
This functionality is completely automatic and requires no setup or configuration activities by the ISV or
the end user.
Sentinel Keys enables you to identify which Sentinel protection keys are currently present on
the network, including locally connected keys.
Products enables you to view a list of all the Base Products available on all Sentinel License
Managers (local and network). In addition, when a Product contains Features with detachable
licenses you can see the number of licenses for the Product that are currently available to be
detached from the network and the maximum duration for which they may be detached. This
option also enables you to access the Detach/Extend functions.
Note : The Product name for Products that are licensed with Sentinel HL keys are not necessarily
displayed in Admin Control Center.
Features enable you to view a list of the Features that are licensed in each of the Sentinel
protection keys that are currently present on the network, including locally connected keys. In
addition, you can see the conditions of the license, and the current activity related to each
Feature.
Page 3 of 18
Sessions lists all the sessions of clients on the local machine, and those remotely logged in to
Sentinel License Manager on the local machine. You can view session data and terminate
sessions.
Update/Attach enables you to update existing licenses on a Sentinel protection key in the field
and, in the case of Sentinel SL keys, to attach a detachable license to a recipient machine. It also
enables you to apply identification details of an offline recipient machine to a host machine in
order to create a file for a detachable license.
Access Log enables you to view a history of log entries for the server on which Sentinel License
Manager is running.
Configuration enables you to specify certain operating settings for Sentinel Admin Control
Center running on the connected machine. You can set parameters relating to user access,
access to remote Sentinel License Managers, and access from remote clients. In addition, you
can customize log template files in terms of the data they return.
Diagnostics enables you to view operating information for the Sentinel License Manager to
which you are currently logged in, to assist in diagnosing problems. You can generate reports in
HTML format. This option also enables you to view miscellaneous data relating to the use of the
server on which Sentinel License Manager is running.
Help displays the Sentinel Admin Control Center help system. Context-sensitive help is available
within each of the functions described above, by clicking the Help link at the bottom of the page.
About provides information about the version of Sentinel License Manager, and a link to the
SafeNet, Inc. Web site.
Country Flags enables you to change the language of the user interface by clicking on the flag of
the country appropriate to the language you require. Languages other than English can be
downloaded from the Sentinel Web site.
Page 4 of 18
This example has several different kinds of keys. Not all these types of keys will be visible to others,
mainly just the standalone and networked keys.
The blue Master keys allow specific people to generate files for the security keys. No one will have these
keys except for those who are allowed to make such files, like CAD engineering or IT/SAP.
Page 5 of 18
The soft license or certificate is a different kind of security also may be known as keyless, and is
currently under investigation at this time. The red key is the Network key and the green key is the
Standalone key.
The see the contents of the network key, click on the Net Features link-box on the right:
Page 6 of 18
You may see just numbers listed in the Features column or you may see actual feature names. Your
initial preconfigured key will only show the features as numbers.
If any anytime you need an update to your license, then you will receive an updated license file to apply
and this will enable the ability to see the feature names. Your key will work with either numbers or
feature names.
You will see an expiration date in the Restrictions column. All keys will have expiration dates regardless
if they are permanent licenses. If you are entitled to permanent licenses you will receive updates for
your key prior to your expiration period.
Clicking on the Sessions link will display the information of the connected users:
Page 7 of 18
Page 8 of 18
Users
The user restrictions that you define are evaluated in the order in which they are specified, and the
evaluation process stops when the first match is found. You therefore need to take care that the
restrictions are listed in an order that satisfies this logic.
The value allow=all@all is implicitly added to the end of the list. According to the logic just described, if
this value was at the beginning of the list, all subsequent restriction values would be ignored.
Additional information about defining restriction values is provided in the Admin Control Center help
system.
Page 9 of 18
The value allow=all is implicitly added to the end of the list. According to the logic just described, if this
value was at the beginning of the list, all subsequent restriction values would be ignored.
Additional information about defining remote client access restriction values is provided in the Admin
Control Center help system.
Accessing Sentinel License Manager Located on a Different Subnet
When a Windows application that is protected with Sentinel LDK v.6.0 or later is located on a different
subnet than Sentinel License Manager and the Sentinel protection key, you must create a separate
configuration file to enable the application to find the License Manager.
Create a file called hasp_vendorID.ini, where vendorID is the Vendor ID associated with your Batch
Code (for the DEMOMA Batch Code, use hasp_demo.ini). Place the file on the same machine as the
protected application, in the following directory:
For Windows Windows 7: %LocalAppData%/SafeNet Sentinel/Sentinel LDK/
For example, for Vendor ID 37517 and a user named test1, create the following file:
C:\Users\test1\AppData\Local\SafeNet Sentinel\Sentinel LDK\hasp_37517.ini
Page 10 of 18
A separate .ini file must be created on the machine for each user of the protected application.
The hasp_vendorID.ini file should contain the following line:
SERVERADDR = remoteServerAddress where remoteServerAddress is the IP address or computer
name of the remote machine that contains Sentinel License Manager and the protection key.
When you define criteria relating to the machines that may be searched for Sentinel License
Manager, you can choose to:
Enable a broadcast that searches all machines on the local network
Search the default local group in an IPv6 subnet
Restrict the search to specific machines. In this case, it is necessary to specify each machine that
may be searchedby specifying either its name or its IP address.
Additional information about defining remote license manager access restriction values is provided in
the Admin Control Center help system.
Page 11 of 18
Page 12 of 18
Page 13 of 18
You will see an acknowledgement that the file has been saved along with other options:
Note the name and location of your Downloads folder to locate the file to send to the requestor. Send
this file to the person who requested the file from your key.
It can be sent through email or the way as instructed by the requestor.
Once the requestor receives the C2V file, they will generate a new file for you to apply.
Page 14 of 18
Page 15 of 18
Select the V2C file to use then select the Open button:
Page 16 of 18
You should receive a confirmation message indicating the file was applied successfully:
Page 17 of 18
If you receive an error, capture a copy of the error message and send it to the requestor.
To see the updated file, simply click on the link for the key ID:
Now you will see the updated contents and the feature names:
Page 18 of 18