This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- Re: Multiple Served License For Same Vendor
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 11, 2007
03:46 PM
Multiple Served License For Same Vendor
Background:
Our company's product had to change our vendor seeds for crypt as it was compromised. Now we have two different vendor daemons, license generators, etc, for our product based on the product's revision.
Questions:
In general, can you have multiple license servers served on the same box.
If it is possible, is there an issue for having two separate license servers serving two products that use different lmgrd and vendor daemons?
Or will there be conflicts?
If there are no conflicts, how is multiple license servers set up?
Our company's product had to change our vendor seeds for crypt as it was compromised. Now we have two different vendor daemons, license generators, etc, for our product based on the product's revision.
Questions:
In general, can you have multiple license servers served on the same box.
If it is possible, is there an issue for having two separate license servers serving two products that use different lmgrd and vendor daemons?
Or will there be conflicts?
If there are no conflicts, how is multiple license servers set up?
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 15, 2007
01:36 PM
Seems like you cannot have the two vendor daemon's of the same name served from the same box at the same time. See:
http://community.installshield.com/showthread.php?t=170295
If this is the case, what did customers moving from 10.x -> 11.x do when their vendor seeds changed? Did they also change their vendor daemon name during this transition?
http://community.installshield.com/showthread.php?t=170295
If this is the case, what did customers moving from 10.x -> 11.x do when their vendor seeds changed? Did they also change their vendor daemon name during this transition?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 16, 2007
03:17 PM
So lesson learned. Never change your vendor seeds. Ever.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 17, 2007
05:36 PM
Quite right; the Programming and Reference Guide section "Upgrading to FLEXnet Licensing 11.x" states that the seeds should not change, to avoid the need to reissue everything...
Robert
Robert
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 18, 2007
05:46 PM
TobiaszJason wrote:
Seems like you cannot have the two vendor daemon's of the same name served from the same box at the same time. See:
http://community.installshield.com/showthread.php?t=170295
If this is the case, what did customers moving from 10.x -> 11.x do when their vendor seeds changed? Did they also change their vendor daemon name during this transition?
Hi,
Typically moving from v10.x to v11.x the vendor keys have changed, which are provided by Mvsn, NOT the seeds. You need to maintain the same seeds for backward compatibility.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2007
01:45 PM
But the point was that we had to change our seeds as our encryption was compromised.
Then when we updated our product (total overhaul of the old product), we generated different vendor keys for each product line not know the ramifications that that would have.
Now we have to do another build of our older product so that it uses the same vendor keys as the new product. It's a tad bit frustrating, but necessary to have the ability to serve both at the same time.
Then when we updated our product (total overhaul of the old product), we generated different vendor keys for each product line not know the ramifications that that would have.
Now we have to do another build of our older product so that it uses the same vendor keys as the new product. It's a tad bit frustrating, but necessary to have the ability to serve both at the same time.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)