Home6.3 Network GuideFAQsKeeping Each 6.x User to the "Right" License

3.13. Keeping Each 6.x User to the "Right" License

Disponible en español: Múltiples Licencias Concurrentes de Red 6.x en un servidor
Disponível em português: Várias 6.x Concurrent Licenças de rede em um servidor

Applies to: All 6.x products deployed in a Concurrent Network
If you have a 7.x network, see Keeping Each 7.x User to the "Right" License.

How can I let each user use only the "right" license when our server holds multiple Palisade licenses?

Enterprise Network

An Enterprise Network client gets its license at install time, or in a specific activation step. That license stays with that computer, whether or not the Palisade software is running, unless the license is deactivated through License Manager in the software. (This would be done before the computer is wiped or decommissioned, for example.)

When you download an Enterprise Network license from Palisade's server to your server, Server Manager prompts you to create a separate Palisade_NetworkClient.ini file for each Enterprise Network Activation ID. Then, when you install an Enterprise Network client, you simply use the Palisade_NetworkClient.ini file for the product and edition that you want that user to have.

Concurrent Network

A Concurrent Network client gets a license dynamically from your server at run time. When the end user closes Excel, or unloads the Palisade software, the license is released.

The software has default rules about which license is used, but the end user can always click Select License in License Manager to get a list of available licenses. The list includes every relevant license that exists on one or more of the listed servers and has a seat available; it excludes licenses that this user or computer is not authorized to use. After the user chooses one, the software remembers the selection and tries to use the same license the next time that user runs. (Which License Gets Used? tells much more about this.)

For example, if all @RISK Industrial licenses are in use, but the user doesn't need to run any optimizations or fit time series, an @RISK Professional license (if available) would be perfectly usable. A user who usually uses @RISK Professional, but needs to run a one-time optimization, could click Select License and select an Industrial license, if one is available.

If you want to restrict certain users to certain licenses, there are two methods to enforce this:

If you have multiple Activation IDs for the same product and edition, the network software treats the total of those concurrencies as a single pool. Usually this is a good thing, but if you need to make sure that certain people or groups always have a license available, you can use the RESERVE keyword in the options file. See More Options for On-Network Use.

Additional keywords: Multiple licenses on serve; More than one license on server

Last edited: 2015-04-10

This page was: Helpful | Not Helpful