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
- :
- Site License Best Practice
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
‎Dec 09, 2009
04:09 PM
Site License Best Practice
What would be the best practice for implementing a site license for a customer that does not wish to use server?
Let's say the customer has 20 desktops and a couple of laptops. The customer is also getting in new hardware frequently.
Do you just give them a node-locked license for each machine...?
Let's say the customer has 20 desktops and a couple of laptops. The customer is also getting in new hardware frequently.
Do you just give them a node-locked license for each machine...?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 09, 2009
05:54 PM
Part of the answer depends on how you're fulfilling licenses: with FlexNet Operations, or by hand, or...? You could issue node-locked licenses, but that could be a hassle if you're creating them by hand.
Another option is to use "activatable" trusted storage licenses: you could provide the customer with a count of licenses, and their client machines would have to touch an internal server (at their site) once to detach a license, and then never have to contact the server again. The programming and reference guide for trusted storage-based licensing (ProgRef-TS.pdf) has more information about that option.
Another option is to use "activatable" trusted storage licenses: you could provide the customer with a count of licenses, and their client machines would have to touch an internal server (at their site) once to detach a license, and then never have to contact the server again. The programming and reference guide for trusted storage-based licensing (ProgRef-TS.pdf) has more information about that option.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 11, 2009
11:16 AM
We create the licenses by hand, well, we use a utility. It only takes a few seconds to generate a license.
As a scenario, let's say the customer does not have any sort of networking capabilities. Let's say they don't even have networking cards installed on the machines. They could not even contact the activation server one time. They are also constantly changing and adding hardware.
How would you handle that?
As a scenario, let's say the customer does not have any sort of networking capabilities. Let's say they don't even have networking cards installed on the machines. They could not even contact the activation server one time. They are also constantly changing and adding hardware.
How would you handle that?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 14, 2009
06:04 PM
It's difficult to say what's "best" at this level of detail; it depends on your relationship with the customer, your business processes, and all that. One option is to issue a single license file with a node-locked wildcard HOSTID identifier (in HOSTNAME or INTERNET, for example)...