/build/static/layout/Breadcrumb_cap_w.png

License Issue with Repackaged NetViz program

I support a package called NetViz which previously just needed to be repackaged and worked fine. I used WinstallLe, removed the extra stuff I didnt want, cleaned up the MSI and everything worked. However, licensing has changed. There is a particular license for each copy for NetViz. I asked for a site-license but we dont pay them enough money (over a million dollars). I tried just using one license and managing the number of licenses myself except the program sends a broadcast out to the network to see if anyone else has that serial number.

What I would like to do is set it up so that each client gets their own license. Thankfully, the license key is kept in HKLM so it is rather easy to change. I could create MSTs for each of the licenses but we are talking about 25 licenses and that really isnt an elegant solution.

Is there any other easier way to have a package have a license based on a particular computer or something like that? Or am I going to have to maintain 25 MSTs? Thanks.

0 Comments   [ + ] Show comments

Answers (1)

Posted by: WiseUser 18 years ago
Fourth Degree Brown Belt
0
You could include a sort of "ini" file with your package, and use a CA to read the license key into a property.

[Licenses]
Machine1=LicenseKey1
Machine2=LicenseKey1
Machine3=LicenseKey3
Machine4=LicenseKey4
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ