/build/static/layout/Breadcrumb_cap_w.png

License control

I have a product that is shipped on a CD-Rom containing a .MSI file created with a Visual Studio 2010 Deployment Project. I am looking for a way to control the number of times our software package can be installed. That is, if we sell the customer 15 licenses I only want the install process to work 15 times. On the same note, we need a way to allow the product to be reinstalled when hardware changes and software is upgraded.

I am open to using a dongle or some type of physical or software device. How are people handling these sorts of issues?

Thanks,

Tony

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 13 years ago
Red Belt
0
I don't think this kind of thing belongs in the installer but in the application. There was quite a good registration/serial number "shell" written in VB6 posted ages ago on Planet Source Code which you may be able to adapt, depending on which is your coding language. Nowadays, I think most of these things "phone home" to check whether or not the license is valid.
Posted by: mazessj 12 years ago
Blue Belt
0
ORIGINAL: taiken

I am open to using a dongle or some type of physical or software device. How are people handling these sorts of issues?


SafeNet Sentinel HASP? You can control runtime access via individual local dongles or via a network dongle (concurrent). Pass along the costs to the customer.
Posted by: jmaclaurin 12 years ago
Third Degree Blue Belt
0
license server
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