This is a release note regarding the new versions, Trinity 8.03, Genesis 6.3s, and Kinex 5.31 released Octover 1st, 2026 and later. With this version, the license information is stored differently than before. It is now saved in the HKEY_CURRENT_USER, rather than HKEY_LOCAL_MACHINE. This page describes the implications for users and IT/admin.

Software Installation

Software installation remains the same. You need to be an administrator. Launch the .msi file and follow instructions. All our application and the installer files are signed using Microsoft Artifcat Signing, by ZetaWare Inc. IT may package the installation in their rollout script easily.

License Regitration

After installing the new version. For existing network license users, you may run this cript to copy the license info from HKLM to HKCU. it is optional, as otherwise, you will just manually click OK when it asks for the license.

For future installations, the following step no longer requires admin or UAC elevation. You will just launch the application as a standard user. If a license has not already registered, it will show this dialog: Do not use an admin account to register the license, because the license information is user speficic, not specific to a hardware.

For most corporate users, the choice is number (3), Register to an existing floating network license. Ask your IT/System admin friend for the path, enter in the license path box. Click OK. This is a onetime only registeration.

This change has several advantages:

• Eliminates most of the UAC/Permission related problems we have had in the past
• Users can check out, check back in, a license for traveling, off line work, or with poor network connection
• User specific, works implicitly with cloud on demand VM machines.
• Rollout, packaging team no longer need to assign the license path

IT administrators

We recommend packaging only the software installation. All our installers are standard .msi files, you can incorporate in your deployment. We dont recommend packaging the licnese path along with the application. The license path is stored in HKCU as below:

Users have full power to regieter to existing licenses. This eliminates many of the issues related to UAC, and permissions we used to have.

Automating within user groups This registry key can be exported by one user and merged by any other user directly to automate the process. Right click the Acudata key under HKCU\Software\ and choose Export. Save it as a .reg file. Another user can double click the .reg file and choose Merge. This does not require admin rights.

Managing multiple site licenses on one server If your company has licenses at multiple sites, you can install licenses on the same cloud server in different folders: such as: \\license_serverx.company.com\ZetaWareLicenses\Houston\ and \\license_serverx.company.com\ZetaWareLicenses\London\. To conform to license agreements, it is important to set permissions to each license folder only to users at a given site.

Enterpris deployment It is possible to configure the license in HKCU in your deployment process using PSADT with Intune or SCCM. This may work if your company has only onesite, or your deployment is site specific. But we dont recommend it. We recommend publishing the license path within your user groups.

Thanks for your kind corporation in our transition to make licensing easier for our users. Do note hesitate to contact us if you have any questions.

Back to Trinity support page