Licensing
Applying a Standalone License
If you are going to apply the license to a server machine, please see the Server Setup article below
Once installation of Verity is complete, an activation box will appear assuming you kept the Launch Licensing Utility checkbox checked during installation. If the activation box does not appear, type Verity License Tool into the windows search bar and press enter. Apply the code that you received with your ClearEdge3D License Certificate email in the activation window and click Activate. The license should successfully activate allowing you to access the software. We recommend reading the Project Setup section of the Knowledge Base for additional guidance.
Server Setup
To install only the necessary tools to host the license on a server, download this zip file: VerityNetworkSetup.zip
If you are unable to download this for any reason, please contact Support@ClearEdge3D.com
On the server machine that will host the license, unzip the VerityNetworkSetup.zip found above. It contains the following 3 files:
- Haspdinst_Runner.bat
- haspdinst.exe
- RUS-LicenseTool.exe
Quick summary of steps to install and activate the license
- Run the Haspdinst_Runner.bat as an admin.
- Create a .c2v file using the RUS-LicenseTool.exe (use your company name as the name of the file to keep things organized).
- Email the .c2v file to Licensing@ClearEdge3D.com
- Apply the .v2c file sent in response using the RUS-LicenseTool.exe.
More detailed instructions with images below.
Licensing Environment Setup
Step 1: Run the Haspdinst_Runner.bat as an admin

Figure 1: Installing the licensing environment
After successful installation, confirm the licensing environment installation locally on the server here: Sentinel Admin Control Center
Step 2: Once this is accessible, open the Verity RUS-LicenseTool. Select the Installation of new protection key within the Collect Status Information tab. Click the Collect Information button to create the .c2v file.

Figure 2: Verity RUS-LicenseTool
Step 3: Email the .c2v file to Licensing@ClearEdge3D.com. It is recommended to respond directly to the ClearEdge3D License Certificate email and include details such as your company name. A corresponding .v2c file will be sent back to you during our standard business hours.
Step 4: On the same computer, open the Verity RUS-LicenseTool and navigate to the Apply License File tab. Click the 3 dots button (…) in the bottom right corner to select the .v2c file that was sent back to you and then click the Apply Update button.

Figure 3: Verity RUS-LicenseTool Apply License File
Finally, you may verify that the license is active by navigating to Sentinel Admin Control Center and checking for Vendor 109705, this will be Verity.

Figure 4: Sentinel Admin Control Center
End User Configuration
Once the license is activated on the server, the end user running Verity will need to configure their computer to access the license. This can be done in the configuration section of Sentinel Admin Control Center: Configuration:
Start by selecting the Access to Remote License Managers tab. You will need to check the Allow Access to Remote Licenses checkbox and place either the IP or FQDN of the server that is hosting the license within the Remote License Search Parameters box. Then select Submit.

Figure 5: Allow Access to Remote Licenses
After configuration, you can check to see if the license is pulling successfully by waiting a few minutes then checking the Sentinel Admin Control Center for the name of the server machine with Vendor 109705. Once this is populated, Verity can be opened and the license can be pulled to the end user’s machine.

Figure 6: Defined Licenses on the Server
Server Access Controls
License access can be controlled in the Access from Remote Clients section of the Sentinel Admin Control Center: Client Configuration. By default, any computer on the network can access the license.
Ensure the Allow Access from Remote Clients is checked. There are a large variety of options for controlling access. This is a guide hosted by the local licensing environment: Sentinel Admin Control Center: Configuring Access from Remote Clients
License Transfers
The licensing system is currently not setup to perform transfers purely on the client side. To conduct a license transfer the following steps need to be conducted.
For the transfer to work, both servers need to have this zip folder downloaded: VerityNetworkSetup.zip. Additionally, you must run the Haspdinst_Runner.bat as an admin. For “Server A” this should already be done because it has an existing license. For “Server B” this is essentially following the steps provided in the Server Setup section above. (These steps in the example below are assuming a license transfer from Server A to Server B)
Step 1: Produce a .c2v file using the Verity RUS-LicenseTool.exe on Server A (the server that has the license currently). Choose the Update of existing protection key option within the Collect Status Information tab, then select Collect Information. Name the file your company name.

Figure 7: Collecting a .c2v file for License Transfers
Step 2: Email this file to Licensing@ClearEdge3D.com and request a license transfer in the body of the email with your company name included.
Step 3: Our licensing team will respond with a .v2c file. Within the Verity RUS-LicenseTool on Server A, navigate to the Apply License File tab and click the 3 dots (…) in the bottom right corner. Attach the .v2c file that was sent by the licensing team. Finally Click the Apply Update button. This will essentially wipe the license from Server A allowing us to create a new license for Server B.

Figure 8: Attaching the .v2c file for License Transfers
Step 4: Repeat Step 1 of License Transfers to ensure the license has been wiped.
- Send the newly acquired .c2v file to Licensing@ClearEdge3D.com.
- These first 3 steps above format your existing license to deactivate it. By collecting a second .c2v file, we are able to confirm the format has fully taken place. Once these steps are complete, we can proceed to the following steps that involve Server B.
Step 5: Follow Steps 1-4 of Server Setup but on Server B instead of Server A.
After formatting the license on the previous server, you are essentially setting up a new server so following the steps of Server Setup will work.