Company A has X, Y and Z software and uses Flexnet based protection. Company B purchases software X. Company A continues independently with software Y and Z. Company A is prohibited or not interested in issuing licenses for software X anymore.
Company B plans to continue with Flexnet based protection. But they have to get a new key, etc... So, their licenses would be valid only for the new versions released from Company B. Users need multiple years to transition to new versions or want to keep older versions to compare even after transitioning to new versions.
Questions:
1. How can users continue to use older versions of the software when Company A is prohibited to generate licenses and Company B cannot generate licenses for the older versions? Of course, Company B can re-compile older versions with new license keys. But this has the potential to introduce some uncertainty, reinstallations, etc.. and both users and Company B would want to avoid that.
2. What is the typical experience from those who have gone through such a transition?
3. Is there any legal mechanism / process for Company B to generate licenses for older versions of software X?
The easiest way would be as what you suggested "re-compile older versions with new license keys" as this would ensure compatibility .
You can also use a CVD Configuration , for example the vendor being served by Company A is "XYZ" and Company B can buy a new license key /new vendor say "ABC" altogether for serving new versions of the software . You can combine both the vendors to create a single license file that servers both the software .For further details you can have a look at "Creating a Common Vendor Daemon "in the programming reference guide .
