Home6.3 Network GuidePrinter Friendly Version

6.3 Network Guide

Palisade's 6.x Network Software for network admins.

1. Server Setup

1.1. License Server System Requirements (6.x)

If you have a 7.x network, see License Server System Requirements (7.x).

Full administrative rights are required for the server setup. There's no need to uninstall an older 6.x version of Palisade Server Manager before installing the latest version.

System Requirements

The server software can run on Microsoft Windows XP or any later version of Windows. There is no need for a dedicated machine, because the license service just needs to sit and listen for license requests from clients.

Installing on a virtual server? See Are virtual servers supported?

Server Manager 7.x must not be installed on a server with Palisade 1.x or 4.x licenses. See What if I already have a Palisade 1.x/4.x license on this server? for further information.

Client Versions Supported

Any Server Manager 6.x will support any licenses 5.x/6.x and any client software 5.x/6.x, even including 6.x versions later than the Server Manager version. It is not necessary to upgrade client software and server software at the same time, as long as the client software version is within 5.x/6.x.

Last edited: 2015-04-10

1.2. Step 1: Install 6.x Server Software

If you have a 7.x network, see Step 1: Install 7.x Server Software.

If you already have a 6.x version of our server software on this server, you can skip this step. See What if I already have a Palisade 6.x license on this server? for more information.)

If you're installing your first Palisade 6.x license on this server, even if you have Palisade 5.x licenses, then you need the 6.x server software. Download the server installer from the link you received in email, and run it as administrator.

Folders used: If you already have any Palisade software installed (6.x server software or 5.x/6.x end-user software), the installer will use the existing Palisade folder. Otherwise, the installer will suggest C:\Program Files (x86)\Palisade or C:\Program Files\Palisade for the install, but will let you select a different install folder. NetServer and System folders will be created under the install folder unless they already exist.

The main components of the installed server software are:

  • An interactive Server Manager that you use to set licensing options, activate and deactivate licenses, and monitor license use. You will find it in the Palisade Network Server group in the Start menu. (This Guide, and your network license agreement, can be opened from the same program group.)

  • Four background processes: FNPLicensingService.exe, running as the service Flexnet Licensing Service; two instances of lmgrd.exe, one running as the service Palisade License Service; and Palisade.exe, also known as the vendor daemon. All run as system processes; if you want to find them in the Windows Task Manager, select the Show processes from all users button.

  • Three license files: PalisadeNetwork.lic, Server.lic, and Palisade.opt.

PalisadeNetwork.lic is the same for every network and should not be touched.

Server.lic will be rewritten by Server Manager if you change server options, and Palisade Technical Support will supply a new Server.lic if you get a certificate license.

Palisade.opt is also written by Server Manager and is used to manage borrowing in Concurrent Networks. You can add some FLEXnet options to Palisade.opt; see Can we use our standard FLEXnet options file? and Access Control in Concurrent Network.

Palisade software release 6.x installs FLEXnet Publisher 11.10 as the licensing system. This is compatible with Palisade 5.x licenses and will not interfere with FLEXnet licenses from other vendors.

Caution: Do not alter any of the files in the NetServer folder, except as instructed in this Guide or by Palisade Technical Support. Our software uses the .lic and .opt files in customized ways that don't always match the standard FLEXnet usage.

Last edited: 2015-09-10

1.3. Step 2: Set Options—Port Numbers (6.x)

Disponible en español: Cambio de Número de Puerto para Licencias de Red 6.x
Disponível em português: Modificando número da porta de rede

Applies to:
Palisade network software releases 6.x
If you have a 7.x network, see Step 2: Set Options—Port Numbers (7.x).

Click Start » All Programs » Palisade Network Server » Server Manager. Server Manager will update any 5.x license process; see What if I already have a Palisade 5.x license on this server?

The defaults are to select both communication ports dynamically, and to disallow borrowing. Your current options are shown in the Network Server Information box. Click Options if you want to change them. Otherwise, skip to Server Step 3.

Port Numbers

The FLEXnet licensing software uses two TCP/IP ports for communications between client and server. They are called the lmgrd port and the Palisade or vendor daemon port. You can allow both of them to be chosen dynamically (the typical setting), or you can specify either or both of them. "Dynamic" means that the software chooses the ports each time the license service starts.

  • If you specify the lmgrd port, you can choose any unused port number. If the lmgrd port is set to "Dynamic", the software will choose an unused port number, but only within the range 27000 to 27009.
  • If you specify the Palisade vendor daemon port, you can choose any unused port number. If the Palisade port is set to "Dynamic", the software will choose an unused port number, not limited to the range 27000 to 27009.
  • You must not specify the same port number for lmgrd and the vendor daemon.

By default, a first-time install of Server Manager allows both ports to be chosen dynamically. However, if you're installing Server Manager on a server that already has Palisade 5.x licensing software, Server Manager will bring forward any port selections you have already made.

If you want to specify port numbers, it's best to do that before you install multiple clients. If you change the lmgrd port number later, you will also need to change it on every Concurrent Network client that is already installed.

Caution: If you have other FLEXnet-licensed products on the same server, then either every one needs to specify a unique lmgrd port number, or none of them can specify an lmgrd port number.

To find which port numbers the license software is using:

If you have not specified port numbers, you can determine which ports the server is actually using. Click Status in Server Manager.

To set or change the lmgrd port:

  1. In Server Manager, click Options.
  2. On the Options screen, under Communication Port Number (lmgrd), specify a port number (not otherwise used) or select Dynamic.
  3. Click OK, then Stop Service, then Start Service.
  4. In a Concurrent Network, change the lmgrd port number on any clients that have already been installed. See Redirecting 6.x Concurrent Clients to a New Server or Port Number.

To set or change the Palisade vendor daemon port:

In Server Manager 6.2 or later, edit the vendor daemon port on the same Options screen, just below the lmgrd port. (In Server Manager 6.0 or 6.1, on the main screen click Open .LIC Folder. Open the file Server.lic in Notepad and and place the vendor daemon port number on the VENDOR line, in this form:
VENDOR palisade PORT=12345
Then click Refresh in Server Manager.)

There's no software setting on the client for the vendor daemon port. However, if you previously found that you needed to open that port in the firewall of any installed clients, you will need to update the client firewall settings.

Last edited: 2016-03-16

1.4. Step 2: Set Options—Borrowing (6.x)

If you have a 7.x network, see Step 2: Set Options—Borrowing (7.x).

You may wish to let end users borrow a license for use while not connected to your network. If you allow borrowing, you will also specify the maximum number of days allowed, up to 366.

At the time of borrowing, the user specifies a number of days to borrow the license, subject to the maximum that you set on this screen. For end-user instructions, see Borrowing a Concurrent Network License for Use Off Network. A borrowed license is deducted from the available pool on the server during the borrowing period.

When the underlying Concurrent Network license is the certificate type, a borrowed license can be used only by the user who borrowed it. When the underlying license is the activatable type, a borrowed license can be used by any user on that computer. (See Server Step 3 for the certificate and activatable license types.)

At the end of the borrowing period, the license is automatically returned to the server pool, even if the user is still off network. In Server Manager, click Status to view the count of available licenses.

A user who returns to the office earlier than expected can return the borrowed license early by following instructions in the article mentioned above.

Some things to think about before you enable borrowing, or when you set a maximum period:

  • A borrowed license is monopolized by that user. Even when the borrower isn't using it, the license is unavailable to everyone else. (Only the client software can do an early return; there is no way for the server to "force-return" a borrowed license.)
  • If any licenses are borrowed, you can't deactivate the Concurrent Network license. If you allow a long borrowing period, you may have to wait for that length of time to change servers or upgrade to a new major version of the software.
  • Borrowing might not even be needed in your organization. If all licensed users are on desktop computers, for instance in a training session or a computer lab, they are always on network and have no need for borrowing. Similarly, if remote users can access your server through a VPN, they are on network and will not need borrowing.
  • Borrowing will not work if you have the end-user applications installed on a server, or any other environment where end users log in remotely to use the software. The borrow operation will seem to succeed, but in fact it will simply lock up the license till the end of the borrowing period.

You can change the borrowing options at any time. The change will apply to future borrowing but will not affect any currently borrowed licenses.

Borrowing doesn't apply to the Enterprise Network, because every Enterprise client is activated once and then has no more need to communicate with your server.

Last edited: 2015-11-09

1.5. Step 3: Activate 6.x License or Obtain Certificate

If you have a 7.x network, see Step 3: Activate 7.x License or Obtain Certificate.

In this one-time process, you transfer the network license from Palisade's server to your server. Your users will get their licenses from your server and will not need to communicate with Palisade's server.

We offer two options for your Concurrent Network license, activatable license and certificate license. (At this time, Enterprise Network licenses are offered in activatable form only.)

If Server Manager shows any activated or certificate licenses already installed, it's simplest to select the same type for your new license. If this is your first Concurrent Network license, use this chart to help you choose:

 

Concurrent Network

Activatable
License

Certificate
License

License must be refreshed at least once a year?

No

Yes

Change servers without contacting Palisade?

Yes

No

Your server needs an Internet connection?

No

No

Recommended for military and other ultra-secure environments?
(To activate a license, your server communicates directly with ours or you email us an XML file.)

No

Yes

INCLUDE_BORROW, EXCLUDE_BORROW, and BORROW_LOWWATER supported?

No

Yes

Next step: either Activating an Activatable License or Getting a Certificate License.

Last edited: 2015-04-27

1.6. Step 3: Activating a 6.x Activatable License

If you have a 7.x network, see Step 3: Activating a 7.x Activatable License.

Caution: Once the license is activated on your server, it is your responsibility to manage. You must not erase the server's hard drive or decommission the server without first deactivating the license.

To activate a license, either a new license or additional users on an existing license:

  1. In Server Manager, click Activate. Server Manager will prompt you for the Activation ID; enter the one that you received via email.

  2. Server Manager will then prompt you for the number of users. Enter the number given in that same email, or enter a smaller number if you want to split the users among multiple servers.
  3. Server Manager will next give you the choice of Automatic Activation or Manual Activation. Automatic Activation is simplest and best, if your security policy allows it. (Automatic Activation can take up to 60 seconds to return a success or failure status, depending on network connections.)

    If your server has no Internet, or if Automatic Activation fails because of your security policies, select Manual Activation. Server Manager will guide you through the Manual Activation process of creating a request file, sending it to Palisade in email or uploading it to our Web site, receiving a response file from Palisade, and letting Server Manager process the response file. When you activate the first license on this server, and under certain other circumstances, Server Manager will have to configure Trusted Storage as a preliminary procedure. It will guide you through a request-response cycle for Conf files and a second request-response cycle for Act files, so just follow the prompts on your screen.

  4. After a successful activation, Server Manager will update the display. This may take a few seconds.

Caution: If you have multiple Activation IDs to activate on this server, and you are using Manual Activation, finish activating each ID before you begin activating the next one. The FLEXnet software may not work correctly if you go out of sequence.

Last edited: 2015-04-27

1.7. Step 3: Getting a 6.x Certificate License

If you have a 7.x network, see Step 3: Getting a 7.x Certificate License.

  1. In Server Manager, click Open .LIC Folder, and locate the Server.lic file in that folder.

  2. Send your Server.lic file, your serial number or Activation ID, and your desired number of users (up to the number in the email you received) to Palisade Technical Support. If security policies won't let you send the actual Server.lic file as an attachment, we can work with a PDF or a clear screenshot or fax.

  3. When you receive the new Server.lic file from Palisade, replace the old one and click Refresh in Server Manager. (If Start Service appears, click it instead of Refresh.)

  4. Your first certificate on a given server will always be for 30 days. When you have tested it and you know that clients can use the license successfully, contact Palisade Technical Support and we'll send you a production license. Certificate licenses are issued for a maximum of one year at a time, less if you have plans to change servers. Before each one expires, we contact you about a renewal so that you have no interruption in service.

Last edited: 2015-09-09

1.8. Step 4: Create Palisade_NetworkClient.ini File (6.x)

If you have a 7.x network, see Step 4: Create Palisade_NetworkClient.ini File (7.x).

After completing Server Step 3 for the first time, or after changing server name or port number, click Create Client.ini to create the Palisade_NetworkClient.ini file that is needed for client install. (For 5.x licenses, the file is named Client.ini.) Server Step 5 tells you how to use this file.

You may or may not need to create a new .ini file after subsequent license installs with Server Step 3. Here are the rules:

  • For 6.x Concurrent Networks, the Palisade_NetworkClient.ini file contains the server name and lmgrd port number. One Palisade_NetworkClient.ini file can be used for all release 6.x Concurrent Network licenses on a given server.

  • For 5.x Concurrent Networks, the legacy Client.ini file contains the server name and lmgrd port number plus the Activation ID. Each of these Activation IDs therefore needs its own Client.ini.

  • For Enterprise Networks, the 6.x Palisade_NetworkClient.ini file or 5.x Client.ini file contains the server name and lmgrd port number plus the Activation ID. Each of these Activation IDs therefore needs its own .ini file.

After you install your first Concurrent Network license or any new Enterprise Network license on this server, Server Manager will remind you to create the .ini file for the new license. But you can create the .ini file at any time: click the appropriate license in the list, and then click Create Client.ini.

In some unusual setups, clients will need a fully qualified domain name, or an IP address, to find the server. If your network is set up in this way, simply edit the Palisade_NetworkClient.ini file after creating it and before doing the client installs. See Can clients reach our server by FQDN or IP address?

Last edited: 2015-04-27

1.9. Step 5: Post the 6.x Client Installer

If you have a 7.x network, see Step 5: Post the 7.x Client Installer.

The client install needs two files:

  • The Palisade_NetworkClient.ini file that you created in Server Step 4. (For 5.x client installs, it will be Client.ini rather than Palisade_NetworkClient.ini.)

  • The client installer EXE or MSI. The email with your Activation ID also contained a link to the EXE client installer. Download it and place it in the same folder with Palisade_NetworkClient.ini, or contact Palisade Technical Support to obtain an MSI installer and special instructions.

The two files must be in the same folder during the client install. That folder can be anywhere you like—in a network share, on a USB stick, burned to a CD, etc. If you have multiple Concurrent Network products, you can set up the client installs in the same folder or in different folders, as you prefer. Each Enterprise Network client installer must be in its own folder.

Last edited: 2015-04-27

2. Client Setup

2.1. Client Setup Introduction (6.x)

If you have a 7.x network, see Client Setup Introduction (7.x).

Full administrative rights are required for the client install. For system requirements on client computers, see Which Platforms Are Supported by Palisade?

For a silent install, scripted install, SCCM, or other uses of an MSI installer, see How can I script the client install?

Last edited: 2015-06-04

2.2. Concurrent Network Client Setup (6.x)

If you have a 7.x network, see Concurrent Network Client Setup (7.x).

To perform a full install or upgrade install, browse to the network share or other location that you chose in Server Step 5. Then, either run the EXE installer there, or copy the installer and the .ini file to the client computer and run the EXE installer there. Either way, in Vista or Windows 7 or later, you should right-click the EXE installer and select Run as administrator; in Windows XP, you can just double-click the installer.

If the application software is already installed on this client, and you just need to hook it into the network, you can use a shorter procedure if you wish. See Changing 6.x Standalone Workstation to Concurrent Client.

There is no limit to the number of client installs. The client installer doesn't need a connection to your server at install time. Instead, the installer copies the server information from the .ini file to the System Registry. After install, that file is not used.

After the first client install, run the client to make sure that the server and client setups are correct. To do this, on the client click Start » All Programs » Palisade DecisionTools and select the shortcut for the software.

  • If the client software launches without error, click Help » License Manager and look at the license being used. If the network license is not being used, click Select License and select it.

  • During launch, if the client software displays a trial prompt or a "no available license" error, click License Manager. In License Manager, click Select License and select the network license.

If you have to click Select License, the end user will need to do that also, because the license selection applies only to the user who is currently running.

At run time, the client software reads the System Registry to find the server information. If the information copied from the Palisade_NetworkClient.ini file is incorrect, the client software will say that it cannot reach the server. To correct this information on the client, see How do I change port numbers or server names on existing Concurrent Network clients?

Last edited: 2015-06-04

2.3. Enterprise Network Client Setup (6.x)

If you have a 7.x network, see Enterprise Network Client Setup (7.x).

To perform a full install or upgrade install, browse to the network share or other location that you chose in Server Step 5. Then, either run the EXE installer there, or copy the installer and the .ini file to the client computer and run the EXE installer there. Either way, in Vista or Windows 7 or later, you should right-click the EXE installer and select Run as administrator; in Windows XP, you can just double-click the installer.

If the application software is already installed on this client, and you just need to hook it into the network, you can use a shorter procedure if you wish. See Changing 6.x Standalone Workstation to Enterprise Client.

For Enterprise Networks, your license specifies the number of clients you may activate. The installer will try a client activation using your server and Activation ID as shown in the Palisade_NetworkClient.ini file. If the activation succeeds, then when the user runs the software it will start up without any licensing messages.

The activation could fail during install if your server or Activation ID is incorrect, or if the licensed number of users have already been activated, or if your server is unreachable. The software will still be installed, but a message will tell you that the client could not be activated. To fix this, on the client click Start » All Programs » Palisade DecisionTools and then select the application. In the application, click Help » License Manager and then Activate.

  • If the server information or Activation ID was incorrect, enter the Activation ID and server information when prompted. Correct the Palisade_NetworkClient.ini file for future use.

  • If you've already activated the licensed number of users, either contact your Palisade sales office to add users to this Activation ID or deactivate another client to free up a license. Then on this client enter the Activation ID and server information.

  • If you have already installed a trial version, or if all the licenses were in use when you installed the software and now a license is free, please follow the procedure in Changing a Standalone Copy to an Enterprise Network Client.

Reminder: If you later give this user a new computer, or reassign the software to a different user, you must first deactivate the license on this workstation through License Manager. That returns the license to the pool of available licenses on your server.

Last edited: 2015-06-04

3. FAQs

3.1. Citrix and Remote Desktop Services (6.x)

Applies to:
All Palisade Concurrent Network software, release 6.x
If you have a 7.x network, see Citrix and Remote Desktop? (7.x)

No other licenses will work on Citrix servers or through any type of remote login.

Can we use Citrix or Remote Desktop Services (formerly called Terminal Services)?

You can configure a Concurrent Network (only) for all thin clients, all thick clients, or a mix. If your setup includes thin clients, you can configure multiple Citrix servers.

On one or more servers, perform the Server Setup Procedure. This will be your license server. The simplest setup is to have only one license server and place all licenses on it, but if you wish you can have multiple license servers. Multiple License Servers? explains how to split the licenses and how to connect the clients to multiple servers.

If you have all thick clients or a mix, perform the Client Setup Procedure on the appropriate end users' machines.

If you have all thin clients or a mix, perform the Client Setup Procedure on your server(s). It's perfectly okay to have the client software on the same server(s) that you're using for license server. The end-user applications are all in a program group called Palisade DecisionTools in the Start menu. After you publish the applications in that group, end users log in to your server and can run the Palisade software. End users should not have access to the Palisade Network Server group.

Last edited: 2016-08-18

3.2. Virtual Servers? (6.x)

If you have a 7.x network, see Virtual Servers? (7.x).

Are virtual servers supported?

Yes. Most administrators with virtual servers find that an activatable or certificate license works just fine. But a small minority have found that an activatable license does not work: it seems to activate successfully, but then it cannot be used, possibly after the service is stopped and restarted or after the virtual server is rebooted.

This problem does not occur on most virtual servers, and we have not been able to reproduce it or isolate the cause. The activatable type of license does write to the machine's boot record, so possibly the disk emulation is less than perfect with some VM software.

If you have a virtual server and you have any reason to think the activatable license type might be a problem, please don't activate your production license. Palisade Technical Support will be happy to create a test license for you on request. Or you could just use a certificate license and avoid the whole issue, even though the odds that it would affect your server are low. See Getting a Certificate License to obtain a certificate license.

Certificate licenses are not available for Enterprise Networks. Therefore, if you have any reason to suspect a virtual server might not work, please consider a physical server with your Enterprise Network. If that is not convenient, please work with Palisade Technical Support to make certain that a test license works on your virtual server.

Last edited: 2015-04-27

3.3. Internet Needed? (6.x)

If you have a 7.x network, see Internet Needed? (7.x).

Does the software need Internet access?

The clients do not need an Internet connection.

Whether the server needs an Internet connection depends on the license type and how it is activated:

  • Concurrent Network license, activatable type: Internet connection needed for Automatic Activation and Automatic Deactivation, not needed for Manual Activation and Manual Deactivation. (For Automatic Activation and Automatic Deactivation, see How should I set up my firewalls?)
  • Concurrent Network license, certificate type: Internet connection not needed.
  • Enterprise Network license: same as Concurrent Network license, activatable type.

The server software does not need the Internet at any other time.

Last edited: 2015-04-27

3.4. Server by FQDN or IP Address? (6.x)

If you have a 7.x network, see Server by FQDN or IP Address? (7.x).

Can clients reach our server by FQDN or IP address?

Yes, these are both compatible with the FLEXnet licensing software. Don't put an FQDN (fully qualified domain name) on the SERVER line of the Server.lic file; that line must always carry either the bare server name or the placeholder this_host. Instead, after you create the Palisade_NetworkClient.ini file (Server Step 4), edit it before you run the client installer. On the SERVERNAME line, change the host name to the desired FQDN or IP address. Be careful to keep the @ sign.

If you wish, you can have one Palisade_NetworkClient.ini file for clients that are on your LAN and another for client computers that need to get a license from your server but are not on your LAN.

If a given client is usually on your LAN but occasionally goes off network and needs to run the software, borrowing may be a simpler approach. See Can a user borrow a Concurrent Network license for use off network?

Last edited: 2015-04-27

3.5. Multiple License Servers? (6.x)

Disponible en español: Especificando uno o más Servidores para la Licencia 6.x
Disponível em português: Especificando um ou mais servidores de licenças 6.x

Applies to: All Palisade Concurrent Network software, releases 6.x
If you have a 7.x network, see Multiple License Servers? (7.x).

Can a client get its license from multiple servers?

For an Enterprise Network, the issue does not arise because the license is obtained in a one-time activation rather than dynamically when the application is run.

For a Concurrent Network, you can specify multiple servers. You allocate your licenses among the servers, but if one server is unavailable the client will try to get a license from the next. FLEXnet documentation says that the license software looks at multiple servers in the order listed.

Servers are separated by semicolons, as in this example:

27000@Alpher;@Bethe;27010@Gamow

In this example, the end-user (client) software will try to get a license from server Alpher, using port 27000 only. If no license is available, it will try server Bethe, all ports 27000 through 27009. Lastly it will try server Gamow, port 27010 only. (The port numbers must match those chosen on the respective servers; different servers can use the same port number or different port numbers.)

For existing clients, use one of the methods in How do I change port numbers or server names on existing Concurrent Network clients? For new clients, do a regular install first, and then follow one of the methods in that section.

From the end user's point of view, there's no difference between one license server and multiple license servers. A user trying to run @RISK Industrial doesn't know which server is providing the license. If the user runs License Manager and clicks Select License, the display will show all available network licenses on all the listed servers, with no indication of the location of any particular license. (Which License Gets Used? tells much more about Select License.)

Future Needs

If you have only one server now, but you want to plan ahead for future configurations, you can list all servers now, even servers that don't exist yet. The client software will not report an error as long as at least one of the listed servers is reachable and has a license available.

For example, even before purchasing a disaster-recovery server, you can preconfigure clients to reach a disaster-recovery server if the regular server is off line. All you'll need to do if the regular server fails is bring the disaster-recovery server on line, and clients will connect to it automatically when they launch the software. (If the disaster-recovery server won't be connected until the production server fails, a simpler alternative is just to give them the same name. The client software reaches a server by name and port number only.)

Last edited: 2015-04-27

3.6. Redundant Servers? (6.x)

If you have a 7.x network, see Redundant Servers? (7.x).

Is a redundant server system supported?

This Network Server release does not support a redundant server configuration for either type of network.

Last edited: 2015-04-27

3.7. Standard FLEXnet Options File? (6.x)

If you have a 7.x network, see Standard FLEXnet Options File? (7.x).

Can we use our standard FLEXnet options file?

You can use lines from it, but you can't use the actual file.

Server Manager writes an options file called Palisade.opt in the NetServer folder, and uses it to manage borrowing. This file is also read by FLEXnet, so you can add most of the standard FLEXnet options at the end. Please don't change the file name or alter any of the lines written by Server Manager, or the license may not function correctly.

Because Palisade.opt is always the file name, the Server.lic file doesn't need an OPTIONS field on the VENDOR line. In fact, when Server Manager rewrites the file after you change options, it will remove an OPTIONS field if it finds one.

For supported keywords in the options file, see Reference – Options File.

Last edited: 2015-04-27

3.8. Network Ports and Firewalls (6.x)

Applies to:  Palisade Concurrent Network software, releases 6.x
(If you have a 7.x network, see Network Ports and Firewalls (7.x).)
(For standalone software, see Firewall Settings for Palisade Standalone Software.)

How should I set up my firewalls?

Most of our customers don't need to make any changes in their firewall settings at all.

Internet access (from server only, and only when activating or deactivating a license): If Automatic Activation of your license fails owing to your firewall, we recommend that you use the Manual Activation procedure rather than make firewall changes. For Manual Activation instructions, see Activating an Activatable License. If you prefer to change server firewall settings and perform Automatic Activation, here is the relevant information:

  • Server Manager makes a direct connection between your server and Palisade's server via port 80, the same port used by Web browsers for http.
  • If you need to specify exceptions for your server firewall, use *.palisade.com.
  • If your firewall won't let you use wildcards, specify service.palisade.com and service2.palisade.com. We do not recommend listing IP addresses in your firewall exceptions, because those could change without notice.

Client-server communications: Clients and your server must communicate every time a client launches the software, and also periodically while the software is running.

  • On the client side, the simplest setting is to list PalFlexServer6.exe as an exception for send and receive.
  • On the server, it's simplest to list Palisade.exe and lmgrd.exe as exceptions for send and receive.

If you prefer to open specific ports, on the server you need to open the outgoing ports that are listed in Port Numbers. If necessary, open those same port numbers as remote ports in the client's firewall.

Last edited: 2015-04-27

3.9. FLEXnet from Other Vendors? (6.x)

If you have a 7.x network, see FLEXnet from Other Vendors? (7.x).

What if I already have FLEXnet-licensed applications from other vendors?

Palisade network licenses are built on FLEXnet Publisher 11.10. Even if you have FLEXnet licenses from other vendors, please perform our server install. By default, it installs to Palisade folders, preventing versioning problems or any other interference with other FLEXnet on your server. All you need to do is choose a port number for Palisade licenses that is not otherwise in use. (Or just accept the default of Dynamic and let the software choose a port. Caution: If one vendor's lmgrd port is unspecified or dynamic, all must be. In a mix of specified and unspecified ports, the specified ports can create a conflict with the dynamically chosen ones.)

We strongly recommend that you use only our Server Manager to administer Palisade licenses. Server Manager is a more convenient alternative to LMTools and LMAdmin. But more important, Server Manager and the associated Network Server software perform some additional setup behind the scenes, beyond the standard FLEXnet functions. If you bypass Server Manager and make changes using LMTools or LMAdmin, your client software may not be able to obtain a license.

Last edited: 2015-04-10

3.10. Another 6.x License?

If you have a 7.x network, see Another 7.x License?.

What if I already have a Palisade 6.x license on this server?

If you're just adding a license, there's no need to run the server software install again. Follow this shorter procedure:

  1. Download the client installer to the folder where you're keeping client installers.
  2. Install your Activation ID or get a new license certificate, as explained in Server Step 3: Activate License or Obtain Certificate.
  3. Install the new client installer on the clients; see Client Setup Procedure.

If you're upgrading the server software itself, or reinstalling the server software for some reason, you can run the server install without first uninstalling the existing 6.x server software. Here's how:

  1. Run Server Manager and click Stop Service, then close Server Manager.
  2. Run the server installer.
  3. Run Server Manager and click Start Service.

See also: Keeping Each 6.x User to the "Right" License

Last edited: 2015-04-27

3.11. Replacing 5.x Server Software with 6.x

If you have a 7.x network, see Replacing 5.x/6.x Server Software with 7.x.

What if I already have a Palisade 5.x license on this server?

Whether you are replacing a 5.x network with an upgrade to 6.x, or keeping your 5.x network license and adding a 6.x network license, you'll use Palisade Server Manager 6.x to manage all 5.x/6.x licenses. Follow the normal 6.x Server Setup Procedure.

If this is your first install of Server Manager, and you have any 5.x licenses, then the first time you run Server Manager it will ask your permission to take over management of them. This is necessary before you can activate any 6.x licenses. With your permission, the 5.x service will be stopped. For a brief period, while you set a couple of options in Server Manager, clients already running can continue to run but no new clients can get licenses; typically this should be on the order of a minute or two. As soon as you select your options and click OK, the new background license process will be started and client licenses will again be available. The 5.x license service will be deleted, but all files will remain. You can delete them if you wish, either through Control Panel » Programs and Features (look for a product name followed by "Network Edition") or by deleting the containing folder. The default location is C:\Program Files (x86)\FLEXnet\Palisade or C:\Program Files\FLEXnet\Palisade. Please don't create a new 5.x license process; that may render all your licenses unusable.

If your 6.x network license is an upgrade to replace a 5.x network license, your initial Activation ID or certificate license for 6.x will be a temporary one. This allows for a transition period while you upgrade server and clients to 6.x. At the end of the transition period, you will receive your production Activation ID or certificate. For step-by-step procedures, see Upgrading Palisade Software.

Last edited: 2015-04-27

3.12. Compatibility of 6.x with Palisade 1.x/4.x Server Software

If you have a 7.x network, see Compatibility of 7.x with Palisade 1.x/4.x Server Software.

What if I already have a Palisade 1.x/4.x license on this server?

There were two types of 1.x/4.x Concurrent Network licenses, FLEXnet certificate licenses that were pre-activated, and "Palisade concurrent" licenses that required authorization and operated through a network share. If you're not sure which type you have, please contact Palisade Technical Support.

Palisade 5.x/6.x network licenses can't coexist on the same server with 1.x or 4.x certificate licenses. Either remove the older license and uninstall the server software, or choose a different server for your 6.x license.

The "Palisade concurrent" licenses did not use FLEXlm or FLEXnet and will not conflict with Palisade 5.x–7.x network licenses.

Last edited: 2015-04-10

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

3.14. Moving 6.x Concurrent Network to a New Server

Applies to:
Palisade 6.x Concurrent Network licenses
Palisade 5.x licenses managed with Palisade Server Manager

If you have a 7.x network, see Moving 7.x Concurrent Network to a New Server.

How do I move a Concurrent Network to a new server?

The answer varies slightly, depending on whether you have an activatable license (also called "trusted storage") or a certificate license. (Server Manager displays the license type in the lower window of the main screen. If the window is too narrow, hover your mouse over an entry or expand the window.) If your license is the activatable type, you can choose between a 30-day transitional period when both old and new servers are on line, or just finishing the transfer as quickly as possible.

Activatable Licenses, Method 1 – Transfer with Transitional Period

This method affords zero downtime, but there are extra steps to obtain and activate a 30-day temporary license.

  1. Contact Palisade Technical Support with your serial number and request the Server Manager installer, the client installer, and a temporary license. Please do this when you're actually ready to start transitioning the clients, so that the license doesn't run out before you've finished the transition.

  2. On the new server, install Server Manager, activate the temporary license, and post the client installer and the Palisade_NetworkClient.ini file. See Server Setup Procedure.

  3. Redirect the existing clients (end user computers) to the new server for licensing. See How do I change port numbers or server names on existing Concurrent Network clients?

    Exception: If you're upgrading the Palisade software version at this time, skip the redirection step and install the new software right over the old, using the Palisade_NetworkClient.ini file from the new server; see Client Setup Procedure. You can use the same installer on new clients as well.

  4. On the old server, run Server Manager, write down the Activation ID and number of concurrencies, and deactivate the license; see Activating and Deactivating Licenses. Uninstall Server Manager or not, as you choose.

  5. You don't need a new permanent license. On the new server, run Server Manager and activate the license you just deactivated on the old server. You can then deactivate the temporary license to tidy up your Server Manager display, if you wish.

Activatable Licenses, Method 2 – Faster Transfer

The fewer end users you have, the faster you'll be able to redirect them to the new server, and the more attractive this alternative becomes.

  1. Contact Palisade Technical Support with your serial number and request the Server Manager and client installers. You don't need a new license.

  2. On the old server, run Server Manager, write down the Activation ID and number of concurrencies, and deactivate the license; see Activating and Deactivating Licenses. Uninstall Server Manager or not, as you choose.

  3. On the new server, install Server Manager, activate the permanent license that you just deactivated, and post the client installer and the Palisade_NetworkClient.ini file. See Server Setup Procedure.

  4. Redirect the existing clients (end user computers) to the new server for licensing. See How do I change port numbers or server names on existing Concurrent Network clients?

    Exception: If you're upgrading the Palisade software version at this time, skip the redirection step and install the new software right over the old, using the Palisade_NetworkClient.ini file from the new server; see Client Setup Procedure. You can use the same installer on new clients as well.

Certificate Licenses – Transfer Procedure

With certificate licenses, the first certificate on a new server is always for a maximum of 30 days, ensuring zero downtime during the transition.

  1. Contact Palisade Technical Support with your serial number and request the Server Manager and client installers.

  2. On the new server, install Server Manager.

  3. Send Palisade Technical Support the needed host information about the new server; see Server Steps 1–3. Tech Support will respond with a 30-day temporary certificate license file. (Your old certificate license will not work on a different server.)

  4. Install the certificate and post the client installer and the Palisade_NetworkClient.ini file. See Server Steps 3–5.

  5. Redirect one existing client (end user computer) to the new server for licensing; see How do I change port numbers or server names on existing Concurrent Network clients? Or, just install on a new client machine.

    Exception: If you're upgrading the Palisade software version at this time, skip the redirection step and install the new software right over the old, using the Palisade_NetworkClient.ini file from the new server; see Client Setup Procedure. You can use the same installer on new clients as well.

  6. When you have verified that a client is able to get a license from the new server, send the Server.lic file from the new server to Palisade Technical Support and request a production license file. You can easily find the file by clicking Open .LIC Folder in Server Manager on the new server.

  7. Install the production license, following the instructions you'll receive from Tech Support.

  8. Redirect the other existing clients (end user computers) to the new server for licensing, or install the software upgrade.

  9. On the old server, run Server Manager and click Stop Service. You can then uninstall Server Manager or not, as you choose.

Last edited: 2015-04-27

3.15. Redirecting 6.x Concurrent Clients to a New Server or Port Number

Disponible en español: Redireccionando Computadoras Cliente Concurrente 6.x a un Servidor Nuevo o Número de Puerto
Disponível em português: Redirecionando clientes concorrentes 6.x a um novo servidor ou número de porta de rede

Applies to: Palisade Concurrent Network software releases 6.x
If you have a 7.x network, see Redirecting 7.x Concurrent Clients to a New Server or Port Number.

How do I change port numbers or server names on existing Concurrent Network clients?

(This section applies only to Concurrent Network clients. Enterprise Network clients don't connect to your server after activation, so there's no need to update them when you change port number or server name.)

Please see Port Numbers for changes on the server.

If you change or specify the Palisade port (vendor daemon port) on the server, you probably don't need to do anything on the existing clients. However, if you had to open the old port as a remote port on the clients' firewalls, you will need to update their firewall settings to open the new port.

If you change the lmgrd port on the server, you will need to make corresponding changes on any clients that are already installed. You will also need to update the clients if you change servers or rename the server.

The port number (if specified) and server name are stored on the client in a System Registry key:

  • 64-bit Windows: HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE
  • 32-bit Windows: HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE

The information in that key came from the Palisade_NetworkClient.ini file at install time. You can change it later through License Manager in the end-user software, or directly in the System Registry.

Redirecting a Client, Method 1 – End-User Software

If you have only a few installed clients, it's probably easiest to change the information through the software:

  1. Run @RISK (or other licensed Palisade software), with full administrative rights. (It doesn't matter which Palisade software you run, because all applications use the same license path.)
  2. Within the Help menu, click License Manager.
  3. Click Select License and then Concurrent Network.
  4. Select the old portnumber@servername or @servername, and click Delete.
  5. Click Import Client.ini and browse to the Palisade_NetworkClient.ini file that you created on the new server.

As an alternative to steps 4 and 5, you can select the old server information in the list and click Edit.

If you opened the old lmgrd port as a remote port in the client's firewall, change the firewall setting to match the new port.

Redirecting a Client, Method 2 – Registry Edit

You may prefer to change the lmgrd port number by editing the System Registry key mentioned above. If the lmgrd port number is specified on the server, the data in the client's System Registry key should be in the form

portnumber@servername;PalisadeSystemFolder

If the lmgrd port is Dynamic on the server, the System Registry data on the client should have the form

@servername;PalisadeSystemFolder

There could be multiple servers, separated by semicolons. PalisadeSystemFolder is the System folder under the main folder where the Palisade client software is installed. By default, that is C:\Program Files (x86)\Palisade\System in 64-bit Windows, or C:\Program Files\Palisade\System in 32-bit Windows.

Examples:

27003@ourserver;C:\Program Files\Palisade\System
@ourserver;C:\Program Files\Palisade\System
27003@ourserver;C:\Program Files\Palisade (x86)\System
@ourserver;C:\Program Files\Palisade (x86)\System

If you opened the old lmgrd port as a remote port in the client's firewall, change the firewall setting to match the new port.

You can set up a .REG file if you wish. Follow this pattern for 64-bit Windows:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\FLEXlm License Manager]
"PALISADE_LICENSE_FILE"="27003@ourserver;C:\\Program Files (x86)\\Palisade\\System"

or this pattern for 32-bit Windows:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager]
"PALISADE_LICENSE_FILE"="27003@ourserver;C:\\Program Files\\Palisade\\System"

If the lmgrd port on the server is not specified (port is Dynamic in Server Manager), omit the port number but keep the @ sign in the .REG file.

Last edited: 2016-01-26

3.16. Renewing 6.x Enterprise Network on the Same Server

Applies to: All release 6.x products with Enterprise Network licenses
If you have a 7.x network, see Renewing 7.x Enterprise Network on the Same Server.

How do I refresh my Enterprise Network license on the same server?

To allow for the possibility of server moves, Enterprise Network licenses are reissued every year. You should receive a new Activation ID from Palisade about a week before the old one expires. If you have not received it, or if you have a large number of clients and need extra time, please contact Palisade Technical Support with your current Activation ID. When you have the new Activation ID, follow this procedure to renew the network license.

On the server:

There is no need to deactivate the expired or expiring license, and there is no need to reinstall the software on existing clients.

  1. Run Server Manager and click Activate. Enter the new Activation ID and number of licenses.
  2. Click Automatic, or if your firewall prevents Automatic Activation from running click Manual and follow the on-screen instructions.
  3. Server Manager will offer to create a new .INI file. (You may recall that, during an Enterprise Network client install, the Palisade_NetworkClient.ini file must be present in the same folder as the installer. This file contains server information and the Activation ID.) Save the new file, and overwrite the existing Palisade_NetworkClient.ini file that goes with this Enterprise Network license.

For more, see Server Step 4: Create Palisade_NetworkClient.ini File.

On each existing client where the software is still being used:

There is no need to deactivate the expired or expiring license, and there is no need to uninstall or reinstall the software on existing clients.

  1. Log on to the client computer as an administrator.
  2. Run the software and click Help » License Manager. (If the existing license has already expired, License Manager will come up spontaneously.)
  3. Click Activate, enter the new Activation ID, and click Next.
  4. License Manager should already know the port number and server name, and will present them to you for confirmation. The port number (if any) and server name must exactly match those in the generated Palisade_NetworkClient.ini file. If this information is missing or incorrect, edit the screen, then click Next and Activate.
  5. The end user may need to click Select License in License Manager to begin using the new license.

Reminder: If you later give this user a new computer, or reassign the software to a different user, you must first deactivate the license on this workstation through License Manager. That returns the license to the pool of available licenses on your server.

On each new client:

Follow the Client Setup Procedure.

Reminder: If you later give this user a new computer, or reassign the software to a different user, you must first deactivate the license on this workstation through License Manager. That returns the license to the pool of available licenses on your server.

What if my old license has already expired?

The procedure is the same whether the previous license is still current or has expired.

Last edited: 2015-04-27

3.17. Moving 6.x Enterprise Network to a New Server

Applies to: Palisade Enterprise Networks, release 6.x
If you have a 7.x network, see Moving 7.x Enterprise Network to a New Server.

How do I move an Enterprise Network to a new server?

You must deactivate every Enterprise Network client before you can move an Enterprise Network to a new server. There is no need to uninstall or reinstall the client software, and you don't need a new Activation ID.

  1. Get the necessary server and client installers from Palisade Technical Support.

  2. On the new server, perform Server Setup Steps 1 and 2.

  3. On every Enterprise client (workstation), run the software and click Help » License Manager » Deactivate. For more about deactivating, see Deactivating an Enterprise Network Client License.

  4. On the old server, use Server Manager to deactivate the Enterprise license. Make a note of the Activation ID, because you will need it on the new server. See Activating and Deactivating Licenses.

  5. On the new server, use that same Activation ID to perform Server Step 3: Activate License, then do Server Setup Steps 4 and 5.

  6. On every Enterprise client, run the software. If License Manager doesn't open automatically, click Help » License Manager. In License Manager, click Activate, enter the Activation ID, and enter the new server name and port number.

  7. (optional) On the old server, if there are no other licenses, uninstall Palisade Network Server.

Last edited: 2015-04-27

3.18. Changing 6.x Standalone Workstation to Concurrent Client

Applies to: Palisade software releases 6.x
If you have a 7.x network, see Changing 7.x Standalone Workstation to Concurrent Client.

Can I convert a trial or an activated standalone copy to a Concurrent Network client?

Yes, you can, and without uninstalling or reinstalling the software. Here are some things you should be aware of:

  • After you convert a standalone copy to a network client, that user will need to be connected to your network to run the software. (There is a provision for temporary off-network use; see Borrowing for the server procedure and Borrowing a Concurrent Network License for Use off Network for the end-user procedure.)
  • If there's an activated standalone license on the end user's computer, you should almost certainly deactivate it. (It's possible to have a standalone license on a concurrent network client, but it's unusual. Please consult Technical Support if you have questions about your specific situation.) The procedure below includes the necessary steps to do the deactivation.
  • 6.0.1 and later standalone licenses can be converted to Concurrent Network clients without reinstalling. If you have 6.0.0, first upgrade to the current version with a standalone installer; there is no need to uninstall 6.0.0.

The conversion procedure requires full administrative rights. You can perform it via remote login to the end user's computer if you wish.

  1. Open a Notepad window, and paste the appropriate text.

    For a client with 32-bit Windows, use this text:

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Palisade\@RISK for Excel\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\Palisade\Evolver\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\Palisade\NeuralTools\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\Palisade\PrecisionTree\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\Palisade\StatTools\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\Palisade\TopRank\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager]
    "PALISADE_LICENSE_FILE"="port_number_here_if_specified_on_server@server_name;C:\\Program Files\\Palisade\\System"

    For a client with 64-bit Windows, use this text:

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Palisade\@RISK for Excel\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Palisade\Evolver\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Palisade\NeuralTools\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Palisade\PrecisionTree\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Palisade\StatTools\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Palisade\TopRank\6.0\License to use]
    @="Network:"
    [HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager]
    "PALISADE_LICENSE_FILE"="port_number_here_if_specified_on_server@server_name;C:\\Program Files (x86)\\Palisade\\System"
    
  2. Change the last line to reference your lmgrd port number and server name. (You can get them from the main window of Palisade Server Manager. If the lmgrd port number shows as "Dynamic" in Server Manager, don't specify a port number in the file but do keep the @ sign.)

  3. Save the file with a .REG extension, and copy it to the client computer.

  4. If there's an activated license on the client computer, deactivate it as follows. (If there's only a trial license on this computer, skip these lettered steps and just double-click the .REG file.)

    1. On the client computer, run the Palisade software. You may get a message that running the application remotely is not allowed. But the message will also ask if you're an administrator managing licenses, and you should answer Yes, because this can be done remotely.
    2. If License Manager does not come up spontaneously, click Help » License Manager.
    3. License Manager's main screen should show the activated license. If it doesn't, click the Select License button and select the activated license.
    4. Click Deactivate and follow the prompts on screen. If Automatic Deactivation fails, select Manual Deactivation » Save Request File and send the request file to Palisade Technical Support, or upload it to our activations Web page. You must complete the deactivation before proceeding.
    5. When the deactivation is complete, the Palisade software will unload itself. You should then close Excel.
  5. Double-click the REG file. This will complete the conversion of this workstation to a Concurrent Network client.

Last edited: 2016-01-26

3.19. Changing 6.x Concurrent Client to Standalone Workstation

Applies to: Palisade software releases 6.x
If you have a 7.x network, see Changing 7.x Concurrent Client to Standalone Workstation.

Can I change one Concurrent Network client to permanent standalone, while keeping the other users as network clients?

Yes, you can convert a network client to a standalone license without reinstalling the software, so that the user's workstation no longer needs access to your server while running Palisade software.

Please be aware that remote login is not allowed for standalone licenses, so the user will need to be physically present at the workstation to run the installed Palisade software. If this is acceptable, please follow this procedure to change a concurrent network client to standalone:

  1. Contact your Palisade sales representative to purchase the standalone license. You will receive an Activation ID in email.
  2. Launch the existing software. If License Manager does not come up spontaneously, click Help » License Manager.
  3. Click Activate and enter the new Activation ID. Follow the prompts to complete either Automatic Activation or Manual Activation.

Last edited: 2015-04-27

3.20. Changing 6.x Standalone Workstation to Enterprise Client

Applies to: Palisade software releases 6.x
If you have a 7.x network, see Changing 7.x Standalone Workstation to Enterprise Client.

Can I convert a trial or an activated standalone copy to an Enterprise Network client?

You will need to know the port number and server name of your license server, as well as the Activation ID of your Enterprise Network license.

6.0.1 and later standalone licenses can be converted to Enterprise Network clients without reinstalling. If you have 6.0.0, first upgrade to the current version with a standalone installer; there is no need to uninstall 6.0.0.

For 6.0.1 and later, follow this procedure:

  1. On the user's workstation, log on to Windows as a full administrator.
  2. Launch the Palisade software. If License Manager does not come up spontaneously, click Help » License Manager.
  3. If this workstation has an activated standalone license, click Deactivate and follow the prompts on screen.
  4. Click Activate, and enter your Enterprise Network Activation ID.
  5. You will then be prompted to enter the server information.
  6. Click OK, and if a network license is available on that server the software will immediately be activated on this workstation. License Manager will describe this as an enterprise license.

Reminder: If you later give this user a new computer, or reassign the software to a different user, you must first deactivate the license on this workstation through License Manager. That returns the license to the pool of available licenses on your server.

Last edited: 2015-04-27

3.21. Adding Users to 6.x Network License

If you have a 7.x network, see Adding Users to 7.x Network License.

How can I add users to my existing network license?

Look at the existing license in Server Manager to see whether it is activated or a certificate.

To add to a certificate license, click Open .LIC Folder and locate the Server.lic file. Send that file to Palisade Technical Support with a request for us to update it with the additional users.

To add to an activated license, click the Activate button, enter your Activation ID, and specify the number of additional users, not the total number of users. See Activating an Activatable License for the activation process. Network Licenses Installed on This Server will show two instances of the Activation ID, one with the original number of users and one with the newly added number. If you click the Status button, "Licenses issued" will show the total number of users.

Last edited: 2015-07-16

3.22. Silent Install of 6.x Network Client

Disponible en español: Instalación Silenciosa de la Computadora Cliente para Licencias de Red 6.x
Disponível em português: Instalação silenciosa do cliente de rede 6.x

Applies to:

  • All Concurrent Network and Enterprise Network client software, release 6.x. (If you have a 7.x network, see Scripting the 7.x Client Install.)
  • All 6.x Course Licenses installed in Workstation or Concurrent Network configuration

(Please see Silent Install of 6.x Standalone Software if you have standalone software other than a Course License.)

Our configuration management system wants to use MSI-type installers for pushing software to clients, but your installer is an EXE. Can you provide an MSI installer and instructions?

Please see the instructions below for your version of the software.

With releases 6.2 and later:

For SCCM installs or other forms of scripting, you probably want an MSI installer. Please contact Palisade Technical Support to request one, and please include your serial number with your request. When you get the link, make certain that the file includes "-cust-" in its name.

Your script must install the prerequisite software before installing our software from an MSI installer. See Microsoft Components Required for Palisade 6.x Software Install.

For the client install, you will need the Palisade_NetworkClient.ini file as described in Server Step 4: Create Palisade_NetworkClient.ini File. That file should be in a local folder, not necessarily the same folder with the installer. The following commands use C:\TEMP; please substitute the actual folder that contains the Palisade_NetworkClient.ini file.

  • With user interface:

    msiexec /i installername.msi SETUPEXEDIR=C:\TEMP

  • Without user interface (silent install):

    msiexec /i installername.msi SETUPEXEDIR=C:\TEMP /qn USERNAME="firstname lastname" COMPANYNAME="company"

    Specify user name and company name as you wish them to appear on the software's About screen.

Either way, replace C:\TEMP following SETUPEXEDIR with the actual folder that contains Palisade_NetworkClient.ini. Guidelines for the SETUPEXEDIR folder:

  • The folder can be different from the folder where the installer MSI file is located, but it should still be on the local computer.
  • UNC path names are not recommended. The local SYSTEM account used by SCCM is typically unable to resolve UNC paths.
  • Avoid special characters like @ in path names.
  • Even spaces in the path might be a problem. We have had one report that the path cannot contain spaces, even if quoted, but possibly that failure was actually due to another issue.

With releases 6.0 and 6.1:

We don't supply MSIs, but you can extract the MSI installer from the EXE installer:

  1. Run the EXE installer past the point where it extracts the MSI, but don't click the final Install button.
  2. The MSI is extracted to your %TEMP% folder. You can copy (not move) it from there while the installer is waiting for you to respond.
  3. After copying the MSI file, cancel the install.

Before running the extracted MSI installer on a client, you need to install the prerequisites listed in Microsoft Components Required for Palisade 6.x Software Install. These specific versions are required; other versions may not work. You must also place the Palisade_NetworkClient.ini or Palisade_Course.lic file in a folder on the local computer.

Sample command line:

msiexec.exe /i DTS6.MSI SETUPEXEDIR=c:\temp

(Replace c:\temp with the actual folder that contains Palisade_NetworkClient.ini or Palisade_Course.lic. Please see guidelines for SETUPEXEDIR, above.)

If you prefer to script the EXE installer:

Make certain that you have the right file: it must include "-cust-" in its name. If it does not, please contact Palisade Technical Support with your serial number for an installer file.

Have the Palisade_NetworkClient.ini file in the same folder as the installer, and execute this command:

installername.EXE /s /v/qn

The attended install has a checkbox for putting shortcuts on the desktop. To suppress those desktop shortcuts (equivalent to removing the check mark from the box), add the /v"DTOPSHORTCUTS=0" parameter:

installername.EXE /s /v/qn /v"DTOPSHORTCUTS=0"

See also: Silent Install of Non-English 6.x Software

Additional keywords: Scripted install, MSI install, MSI installer, SETUPEXEDIR

Last edited: 2015-04-27

3.23. Using a 6.x Concurrent Network License Off Network

If you have a 7.x network, see Using a 7.x Concurrent Network License Off Network (Borrowing).

Can a user borrow a Concurrent Network license for use off network?

Borrowing is disabled by default, but you can enable it if you wish; see Server Step 2: Set Options. For end-user instructions, see Borrowing a Concurrent Network License for Use Off Network.

Last edited: 2015-04-27

3.24. Taking Back a Borrowed License

Disponible en español: Regresar una Licencia Prestada
Disponível em português: Devolvendo uma Licença Emprestada

Applies to: All Concurrent Network licenses for releases 5.x and 6.x

If you have a 7.x network, see Recovering a Borrowed 7.x License?

A user borrowed a license for a long period and went on vacation. How can we get that license back for another person to use?

The license will come back automatically at the end of the borrowing period, but there's no way for the server to "un-lend" it early.

Only the end user can return the license early, and only while connected to the network.  The procedure is in Borrowing a Concurrent Network License for Use off Network.

To avoid this situation in the future, you may want to shorten the maximum borrowing period. Please see the Options screen of Palisade Server Manager. Users may also need a reminder that they should borrow a license for just as long as they will need it, not for the maximum time they can get.

Last edited: 2015-04-27

3.25. Recovering a Concurrent Network Seat

Applies to: All Concurrent Network products, releases 5.x and 6.x

If you have a 7.x network, see Recovering License if a 7.x Concurrent Network Client Crashes.

How do I recover the license if a Concurrent Network client crashes?

No specific action is necessary. 

If a 6.x client crashes and the same client re-runs the software within ten minutes after the crash, that client will automatically reuse the same license that it was using when it crashed.  As usual, when the client closes Excel its license returns to the available pool.

If a 6.x client crashes and the same client does not re-run the software, then after ten minutes the license is automatically recovered by the server software and returns to the pool of available licenses.

If a 5.x client crashes, the license used by that client is not usable, not even by that client, for two hours.  But the license is automatically returned to the pool of available licenses at the end of that time.  (This is true regardless of the version of the server software.)

Last edited: 2015-04-27

3.26. Monitoring License Use on 6.x Network

Disponible en español: Monitorear el uso de Licencias 6.x en Red
Disponível em português: Monitorando o uso da licença 6.x na rede

Applies to:
All 6.x products deployed as Concurrent NEtwork or Enterprise Network

If you have a 7.x network, see Monitoring License Use on 7.x Network.

How do I monitor client use of my network license?

Most information is displayed when you click the Status button in Server Manager. Further details are available if you click View in Advanced Options.

For details of interpreting the display, see the descriptions of those two buttons in the Reference section.

How can an end user find out who is using the network licenses?

End users can't get this information through the software. Server administrators can find it as described above.

Last edited: 2015-04-27

4. Reference—Server Manager

4.1. Network Server Information (6.x)

If you have a 7.x network, see Network Server Information (7.x).

When you launch the Palisade Server Manager, it presents two categories of information on the main screen: information about the server (below), and information about the licenses on the server.

However, if the Server Manager detects a Palisade 5.x license process running, before it can present that screen it will need your permission to shut down that process and start up the 6.x license service. See What if I already have a Palisade 5.x license on this server?

Network Server Information

This box shows current information known to Server Manager: your server name, the ports used for communication with the clients, and so on. The status of the license service is also shown.

Last edited: 2015-04-28

4.2. Refresh Button (6.x)

If you have a 7.x network, see Refresh Button (7.x).

Click this button after you replace Server.lic with a new license file (certificate) from Palisade. That will cause the license service to read the new license file, and Server Manager will then update both sections of the display.

Please be patient. FLEXnet can take up to 60 seconds to reread licenses, and during that time the title bar of Server Manager may display "Not Responding".

Last edited: 2015-04-28

4.3. Status Button (6.x)

If you have a 7.x network, see Status Button (7.x).

This button adds further information in the Network Server Information box.

To update this status information, click Status, not Refresh.

Enterprise License Status

If you have any Enterprise licenses on this server, a brief Enterprise License Status section appears. It shows each Enterprise Network Activation ID, with the number of activated users and the total number of users allowed on the license. To see which clients have activated Enterprise Network licenses, follow the directions in View.

Concurrent License Status

The long Concurrent License Status section is a pass-through from the FLEXnet software's lmstat program. It shows the license files, the status of the license service, and the status of the Palisade vendor daemon. Then it lists the Concurrent Network licenses, showing the license count for each one in this form:

licenses issued: 7 licenses in use: 3

The "licenses issued" is the number of concurrent users allowed on this license; "licenses in use" includes on-network users and borrowed licenses. These numbers may be off if you stop and restart the license service while a license is borrowed; see below.

If "licenses in use" is nonzero, there's one line for each current on-network or off-network user. (For the history of license use by your end users, see View.)

Concurrent License in Use On Network

If a status line doesn't begin with ACTIVATED and doesn't contain the word "linger", it represents one user using the license on the network. This status line shows the user name, the computer name, and the date and time this user began using the license.

Concurrent License Borrowed (When Server License Is Certificate Type)

If a line ends with "linger" and a number, this is a license borrowed for use off network, when the underlying server license is the certificate type. The user name and computer name are shown, along with the date and time when the user borrowed the license. The date of scheduled return is not shown directly, but the number after "linger" is the number of seconds for which the license was borrowed; divide by 86400 to get the number of days.

Concurrent License Borrowed (When Server License Is Activatable Type)

If a line begins with "ACTIVATED LICENSE(S)", it represents a license borrowed for use off network, when the underlying server license is the activatable type. The status line shows the computer name and the date and time the person borrowed the license. There's no indication of the date the license is scheduled for return.

If you stopped and restarted the license service after a license of this type was borrowed, the borrowed licenses may not be shown in the status display. In this case, instead of including the borrowed licenses in licenses in use, the display shows a lower number of licenses issued. For example, if your activatable Concurrent Network license has five users, two have borrowed it, and none are using it on network, then you may see

licenses issued: 3 licenses in use: 0

The difference between the numbers still gives the number of licenses available, and the "Network Licenses Installed" box below always shows the total number of concurrent users licensed.

Last edited: 2015-06-16

4.4. Starting and Stopping the Service (6.x)

If you have a 7.x network, see Starting and Stopping the Service (7.x).

If the license service is currently running, the next button says Stop Service. If the license service is not currently running, the button says Start Service.

Under normal circumstances, Server Manager will start or stop the service as required, and you won't need to click this button. In some unusual configurations—for instance, if your policy doesn't allow services to be set up for automatic start—you can click Start Service to start the license service.

Stop Service can be useful if for some reason you want to prevent users from running the software for a period of time, for instance while rolling out a new version to all clients.

Last edited: 2015-04-28

4.5. Options Button (6.x)

If you have a 7.x network, see Options Button (7.x).

This button opens a dialog where you can set the ports used for communicating with clients and determine whether to allow borrowing. See Server Step 2: Set Options for the meanings of these options.

If you change server options, Server Manager will stop and restart the license service automatically. This should not have any effect on clients that are currently using the software.

Last edited: 2015-04-28

4.6. Network Licenses Installed on This Server (6.x)

If you have a 7.x network, see Network Licenses Installed on This Server (7.x).

This box lists all Paliasde 5.x–6.x activated and certificate licenses, both Concurrent and Enterprise type, with the details of each.

For some license types, the license information may extend past the right edge of the screen. In that case, just click once on the license of interest and hover your mouse over the text box to display the full description of the selected license. If you prefer, you can resize the Server Manager window.

You may see the same Activation ID listed more than once. Here's an example. Suppose you have a Concurrent Network license with ten concurrent users allowed. Over time your organization grows and you buy an additional five concurrencies. These will be added to the same Activation ID, and after you activate them you will have two entries in the list for that Activation ID, one showing 10 users and one showing 5.

An expired or broken license is not shown here; see Unusable Licenses....

Last edited: 2015-04-28

4.7. Deactivating 6.x Network Licenses

If you have a 7.x network, see Deactivating 7.x Network Licenses.

This article is about deactivating (returning) licenses. If you're looking for how to activate a license, you'll find full details of the activation process in Activating an Activatable License.

When would you want to deactivate a license?

  • When you're planning to change servers, reimage your server, or upgrade your operating system, you must deactivate all licenses first.

  • When you're upgrading Palisade network software to a later version, Palisade Technical Support may ask you to deactivate any old permanent licenses in order to receive the new permanent licenses.

If an Activation ID is listed more than once, that means you originally split its activations; see Network Licenses Installed on This Server. In that case, to deactivate the Activation ID you will need to deactivate each line item, known as a "fulfillment". When you reactivate the Activation ID later, on this server or a different server, you can activate all users in one operation or split them in a different way if you wish.

To deactivate a license, select the license from the list and then click Deactivate. If the Deactivate button is grayed out, this license is a certificate type and cannot be deactivated (returned).

After clicking Deactivate, you can choose Automatic or Manual Deactivation. Automatic is faster, but it won't work if your server can't establish a connection with Palisade's server.

Automatic Deactivation

In Palisade Server Manager, click the license that you want to deactivate. Click Deactivate » Use Automatic Deactivation. You should get a response within 60 seconds. If it is "Your license has been successfully deactivated", then the deactivation is complete. Otherwise, the deactivation is not complete, so please contact Technical Support for assistance before you decommission your server.

After the deactivation, Server Manager will update the display.

If you're returning a license to obtain a newer software release, and you've successfully completed the Automatic Deactivation, please contact Technical Support. Mention the serial number that you deactivated, and ask for the production license for your upgrade.

Manual Deactivation

If Automatic Deactivation fails because your server can't connect to Palisade's server, or if your server is not on the Internet, use Manual Deactivation.

Caution! Don't start any other activation or deactivation while you have this one in progress. That could confuse the FLEXnet licensing software, and recovering from such a state is not simple.

  1. On the main screen of Palisade Server Manager, click the license that you want to deactivate. Then, click Deactivate » Use Manual Deactivation » Save Deactivation Request File and send the saved request file to Palisade Technical Support. It's impossible for Technical Support to deactivate your license without this file.

    You may close Server Manager while you're waiting, if you want to. Use the Close button, not Reset.

  2. Technical Support will send you a response file.

    If you're planning to decommission your server, you can ignore the response file. Technical Support has deactivated the license in Palisade's database, using your request file, and the license is available for transfer to another server. But if you're keeping this server, please proceed to the next step.

  3. On the Manual Deactivation screen, click Load Deactivation Response File and load the file you received from Technical Support. When you get the response "Deactivation was successful", the deactivation procedure is complete.

    If you don't get that response, first verify that you are loading the response file (ResponseDAct.xml), not the request file. If that's not the answer, contact Palisade Technical Support for assistance; include your software serial number and a screen shot of the message.

    If you closed Palisade Server Manager earlier, reopen it and click Resume to get back to the Manual Deactivation screen. If you don't have a Resume button, see After Reset, Can't Load Response File.

After the deactivation, Server Manager will update the display.

Why might deactivation fail?

  • If your server can't make contact with our server, Automatic Deactivation will fail. In that case, try Manual Deactivation.

  • Network licenses can be deactivated only once in 90 days. If you try to deactivate a license too soon, you'll get a message that not enough time has passed.
  • For a Concurrent Network license, if anyone has borrowed a license you will not be able to return the "fulfillment" that includes it. See Status to determine whether any licenses are currently borrowed. If a license is borrowed, and you don't want to wait for the borrow to expire, see Borrowing a Concurrent Network License for Use Off Network for the early return procedure.

  • For an Enterprise Network, if you have activated any end users (clients) you will not be able to return the "fulfillment" that includes them. See Status to determine whether any licenses are currently activated. To deactivate an end user, see Deactivating an Enterprise Network Client License.

Last edited: 2016-09-07

4.8. Create Client.ini ... (6.x)

If you have a 7.x network, see Create Client.ini ... (7.x).

The client installers require a Palisade_NetworkClient.ini or Client.ini file during client install, so that the client software knows where to obtain a license. Click this button to create the needed .ini file for the license that is selected in the panel at left.

Please see Server Step 4: Create Palisade_NetworkClient.ini File for further details of when and how to use this button.

Last edited: 2015-04-28

4.9. Unusable Licenses (6.x)

If you have a 7.x network, see Unusable Licenses (7.x).

The Network Licenses box lists licenses that are currently activated on this server and are usable. If you also have any unusable licenses, Unusable Licenses... will appear. Click it to display a list.

The most common reason for a license to be unusable is that it was a time-limited license and has expired. Other possibilities for an activatable license include changes in server hardware after the license was activated. For a certificate license, editing the certificate (except as directed in this Guide) or moving it to a different server will make it unusable.

If you have an unusable license and you can't determine why it is unusable, Palisade Technical Support will be happy to help you.

Last edited: 2015-04-10

4.10. Open .LIC Folder (6.x)

If you have a 7.x network, see Open .LIC Folder (7.x).

This button opens an Explorer window on the folder that contains your Server.lic file and the Palisade Network Server software. There are three occasions when you might need to open this folder:

  • When you request a certificate license for your Concurrent Network, you need to send a copy of Server.lic from this folder to Palisade Technical Support as part of your request.
  • When you receive a new certificate license from Palisade Technical Support, you replace the old Server.lic file in this folder.
  • To update this Guide with a later version downloaded from Guide for 6.x Network Administrators, open this folder and replace the old GuideForAdministrators_EN.htm file.

Caution: Do not alter any of the files in this folder, except as instructed in this Guide or by Palisade Technical Support. Our software uses the .lic and .opt files in customized ways that don't always match the standard FLEXnet usage.

Last edited: 2015-04-28

4.11. Advanced Options (6.x)

If you have a 7.x network, see Advanced Options (7.x).

The Advanced Options button is the magnifying-glass icon near the lower left corner of the Server Manager window. It opens a panel with the following three buttons.

View

Clicking this button will open a Notepad window containing mostly debugging information. However, the displayed file also contains some license information that supplements the display from Status:

  • For Concurrent Network licenses, Status shows the number currently in use and lists the current users, but it does not show any past usage of the license. To show all usage since the license service was last started, scroll to the bottom of the Notepad window. OUT lines show when end users launched the software; IN lines show when end users closed Excel, or clicked Utilities » Unload @RISK Add-In or similar, to release the license.
  • For Enterprise Network licenses, Status shows the number of activated clients and the total number of allowed users, but it does not show which clients have been activated. For that information, search in the Notepad window (Ctrl+F) for the Activation ID. Below the information block for the license, you will see one "Destination System Name" line for each activated client.

Exception: If you redirected the license log, Server Manager will be unable to display it. In that case, get the information from the file where you redirected the log.

Host ID

The Host ID button displays the server name and Ethernet address(es) as they are known to the FLEXnet licensing software. Palisade Technical Support may ask you to send this information in some circumstances.

Execute

The Execute button is for use by Palisade Technical Support during a remote support session.

Last edited: 2015-04-28

5. Reference—Options File

5.1. Finding and Editing the 6.x Options File

If you have a 7.x network, see Finding and Editing the 7.x Options File.

To view or edit the options file, open Server Manager and click Open .LIC FOLDER. The options file is in that folder and is called Palisade.opt.

You can edit it with Notepad or any plain-text editor, but first make a backup in another location. Special rules for editing:

  • User names and computer names are generally case sensitive, with one exception (GROUPCASEINSENSITIVE).
  • Feature names seem to be case insensitive, but we recommend treating them as case sensitive for compatibility with possible future changes.
  • You will see one or more MAX_BORROW_HOURS lines in the options file. These are written by Palisade Server Manager and should not be changed.
  • If the last character on a line is \ (backslash), then the next line is treated as a continuation of this one.
  • Lines cannot exceed 4000 characters.
  • Comment lines begin with the # character.

After you save the options file, click Refresh in Server Manager to make the license service read the new options. (Stopping and restarting the service will also reread the options file, but a refresh is sufficient.)

Last edited: 2015-04-28

5.2. Maximum Allowed Borrowing Period (6.x)

If you have a 7.x network, see Maximum Allowed Borrowing Period (7.x).

Server Manager writes one or more lines beginning MAX_BORROW_HOURS to the options file. A feature where borrowing is not allowed will have MAX_BORROW_HOURS set to zero; a feature where borrowing is allowed will have MAX_BORROW_HOURS set to 24×(1+maximum days to borrow).

You should not edit the MAX_BORROW_HOURS lines yourself. Instead, click Options in Server Manager and set the maximum borrowing period there. See Step 2: Set Options—Borrowing.

Last edited: 2015-04-10

5.3. Access Control in 6.x Concurrent Network

Disponible en español: Control de Acceso para Licencias Concurrentes de red 6.x
Disponível em português: Controle de acesso para redes simultâneas 6.x

Applies to: All 6.x products deployed as Concurrent Network

If you have a 7.x network, see Access Control in 7.x Concurrent Network.

Can I control user access to particular products, so that certain licenses are reserved to certain users or forbidden to certain users?

For example, I have some @RISK Professional licenses and some @RISK Industrial licenses, and I want to limit who can use the Industrial licenses. Or, I have some DecisionTools Suite licenses and some StatTools licenses, and I want to specify who can use the full Suite and who can use only StatTools. How do I accomplish that?

Yes, you can do this by adding lines to the options file on the server. Before you do that, you need to decide which way you want to structure your permissions for a given product:

  • You can restrict the software so that only designated users can use it. You do this by listing them in INCLUDE lines. Anyone not on an INCLUDE line is locked out from that product.

  • Or, you can let anyone except specified users use it. To do this, list the prohibited users in EXCLUDE lines. Anyone not on an EXCLUDE line is allowed to use the product.

There's no reason to mix INCLUDE and EXCLUDE lines for a given product. But if you do, then anyone not listed on an INCLUDE line is locked out from using the product, and anyone listed on both an INCLUDE line and an EXCLUDE line is also locked out.

Contents of This Article

What Is a "Feature"?

You control access to some or all of your products by specifying the "feature name" on INCLUDE and EXCLUDE lines. In FLEXnet terms, each product is a feature, and every access control command in the options file relates to a particular feature. Different editions of the same product, like @RISK Professional and @RISK Industrial, are different features.

To find the feature name for a license, in Palisade Server Manager click the Status button and then look at the display for lines beginning "Users of". Those list the feature names of licenses on this server. (For information about how licenses are actually being used, see Monitoring License Use on 6.x Network.)

The feature names for 6.x software all contain 60, regardless of the actual 6.x version number; this is why you don't need a new license when you upgrade from a 6.x version to a later 6.x version. Here is the full list of feature names:
  • DecisionTools60_Industrial, DecisionTools60_Professional
    The DecisionTools features allow use of all components of the Suite. If a DecisionTools Suite user has more than one application open at the same time, only one license is consumed.
  • @RISK60_Industrial, @RISK60_Professional, @RISK60_Standard
  • Evolver60_Industrial, Evolver60_Professional
  • NeuralTools60_Industrial, NeuralTools60_Professional
  • PrecisionTree60_Industrial, PrecisionTree60_Professional
  • StatTools60_Industrial, StatTools60_Professional

If you misspell a feature name, or if you have no license on this server for that feature, then when the options file is reread there will be a line in the log file diagnosing it as an invalid feature. See Troubleshooting License Denials, below, to access the log file.

Method 1: Only Named Users Can Use a Feature

You can designate users by Windows user name or Windows computer name. If you have any INCLUDE lines for a feature, then everyone else is locked out from that feature.

Example:

# Stan can use @RISK Industrial from any computer,

# and anyone on computer Atlantis can use @RISK Industrial,

# but no one else can use @RISK Industrial.

INCLUDE @RISK60_Industrial USER Stan

INCLUDE @RISK60_Industrial HOST Atlantis

Only one user name or host name can appear on a line. If you are granting access to just a few users or computers, use multiple INCLUDE lines, like this:

INCLUDE @RISK60_Industrial USER Stan

INCLUDE @RISK60_Industrial USER Michelle

INCLUDE @RISK60_Industrial USER Fernando

INCLUDE @RISK60_Industrial HOST EC-Server

INCLUDE @RISK60_Industrial HOST Atlantis

If you need to grant access to a large number of users or hosts, you'll want to define a group rather than have many INCLUDE lines. See User and Host Groups, below.

In any conflict between INCLUDE and EXCLUDE lists, EXCLUDE wins. For example:

INCLUDE Evolver60_Industrial HOST Atlantis

EXCLUDE Evolver60_Industrial USER Lucy

Lucy can't use Evolver from any computer, not even Atlantis. All other users can use Evolver from computer Atlantis, but not from any other computer.

According to FLEXnet documentation, "Anywhere a host name can be used in an options file, an IP address can be used instead."

Method 2: All Except Named Users Can Use a Feature

You can designate users by Windows user name or Windows computer name. If you have any EXCLUDE lines for a feature, then the named people or computers are locked out from that feature, but everyone else can use it.

Example:

# Stan cannot use @RISK Industrial from any computer,

# and no one on computer Atlantis can use @RISK Industrial,

# but everyone else can use @RISK Industrial.

EXCLUDE @RISK60_Industrial USER Stan

EXCLUDE @RISK60_Industrial HOST Atlantis

Only one user name or host name can appear on a line. If you are blocking access to just a few users or computers, use multiple EXCLUDE lines, like this:

EXCLUDE @RISK60_Industrial USER Stan

EXCLUDE @RISK60_Industrial USER Michelle

EXCLUDE @RISK60_Industrial USER Fernando

EXCLUDE @RISK60_Industrial HOST EC-Server

EXCLUDE @RISK60_Industrial HOST Atlantis

If you need to block access by a large number of users or hosts, you'll want to define a group rather than have many EXCLUDE lines. See User and Host Groups, below.

According to FLEXnet documentation, "Anywhere a host name can be used in an options file, an IP address can be used instead."

User and Host Groups

It's tedious to put a lot of INCLUDE or EXCLUDE lines in the options file. Rather than do that, define one or more user groups or host groups. Here's an example:

GROUP Gentry Michelle Mark Doug Cristina Robson

GROUP Peasants Stan Sally

HOST_GROUP ThirdFloor Asus14132 Asus14133 Asus14134 \

Asus14135 Asus14136

INCLUDE DecisionTools60_Industrial HOST_GROUP ThirdFloor

INCLUDE DecisionTools60_Industrial GROUP Peasants

INCLUDE DecisionTools60_Industrial USER Vince

INCLUDE StatTools60_Professional GROUP Gentry

INCLUDE StatTools60_Professional USER Vince

This lets the ThirdFloor group of computers, the Peasants group of users, and user Vince use a DecisionTools60_Industrial license, but no one else can. The Gentry group, Vince, and no one else can use a StatTools60_Professional license. The ThirdFloor and Peasants groups, and Vince, can still use StatTools Industrial, as part of the DecisionTools Suite. If all the DecisionTools60_Industrial licenses are in use, the Third Floor and Peasants groups will not be able to run StatTools under the StatTools60_Professional license, but Vince and the Gentry group will. (Vince, who was previously using the DecisionTools Suite license, can use the Select License button in License Manager to switch to the StatTools license.)

If your group contains too many members for one line, you can split it into multiple lines, like this:

GROUP giants many names

GROUP giants many more names

GROUP giants still more names

The license system will merge all the lists of users into the "giants" group.

Your HOST_GROUP can identify computers by name or by IP address. According to FLEXnet documentation, "Anywhere a host name can be used in an options file, an IP address can be used instead."

User names and computer names on INCLUDE and EXCLUDE lines are always case sensitive. But you can make them case insensitive on GROUP and HOST_GROUP lines by including this line in the options file:

GROUPCASEINSENSITIVE ON

Even with that line in the options file, the name of the group is still case sensitive.

If you EXCLUDE a group, you cannot then INCLUDE one user or computer from that group, because EXCLUDE always wins.

More Options for On-Network Use

With MAX and RESERVE lines, you can allocate licenses among user groups.

MAX 2 DecisionTools60_Professional GROUP Muggles

Members of the Muggles group may not use more than 2 DecisionTools Professional licenses at a time. If two Muggles are already using licenses and a third member of that group tries to run the software, the request will be denied.

RESERVE 2 DecisionTools60_Professional HOST_GROUP Wizards

Two DecisionTools Professional licenses are reserved for the use of the Wizards group. When any other authorized user tries to use the license, they will succeed if the number of free licenses, plus the number currently in use by members of the Stars group, is greater than 2.

RESERVE 1 DecisionTools60_Professional USER Frances

A DecisionTools Professional license is reserved for use by Frances. When any other authorized user tries to use the license, they will succeed if the number of free licenses is greater than 1 or if Frances is currently using a license.

This setting is usually not a good idea: rather than reserve a Concurrent Network license for Frances permanently, it would make more sense for him to have a standalone license on his workstation. But you might want this setting temporarily, for instance if she is teaching a class and must have guaranteed use of a license while the class runs.

Options for Borrowing

Borrowing is available for both certificate and activatable Concurrent Network Licenses. All of the access-control options mentioned above work with either type; but the three options in this section are different. End users can borrow either type of Concurrent Network license, but you can control borrowing with these options only if your Concurrent Network license is the certificate type. If you try to use these options with an activatable license, the software will simply ignore them without any kind of error message in the log file.

If you need to use these options and you have an activatable license, please contact Palisade Technical Support to surrender your activatable license and receive a certificate license. You won't need to reinstall any software.

BORROW_LOWWATER DecisionTools60_Professional 4

Authorized users may borrow licenses, but there will always be at least 4 unborrowed licenses. This ensures that at least some users will still be able to run on network.

INCLUDE_BORROW DecisionTools60_Professional USER Heather
INCLUDE_BORROW DecisionTools60_Professional GROUP Managers

Heather, and members of the Managers group, can borrow a DecisionTools60_Professional license for off-network use. Other authorized users can use a license while on network but cannot borrow it. (For defining groups, see User and Host Groups.)

If you have any INCLUDE_BORROW lines, then all users not mentioned on those lines are prohibited from borrowing.

Our software lets you borrow only the license you are currently using. Therefore, there's no way to configure options so that someone can borrow a license for use off network but cannot use it on network.

EXCLUDE_BORROW DecisionTools60_Professional USER Denise
EXCLUDE_BORROW DecisionTools60_Professional HOST_GROUP Contractors

Denise, on any computer, and anyone on computers in the Contractors group, cannot borrow a DecisionTools60_Professional license for off-network use, but they can still run on network unless you have separate INCLUDE or EXCLUDE lines forbidding that. Other authorized users can use a license while on network and can borrow it for off-network use. (For defining groups, see User and Host Groups.)

If the same user is covered by an INCLUDE_BORROW line and an EXCLUDE_BORROW line, explicitly or as part of a group, then EXCLUDE_BORROW wins.

If an unauthorized user tries to borrow, or if any user tries to borrow when no more borrowable licenses are left, the borrow operation will fail "for an unknown reason". The administrator can find the reason by looking at the log file. See the next section to access the log file.

Troubleshooting License Denials

If a user is locked out of a license, the client software will tell them only that there is no license. FLEXnet doesn't make a specific failure reason available to the client software, so Palisade software can't display it for the end user. The same is true if the user tries to borrow a license but is locked out from borrowing.

You can find specific reasons in the log file on the server. The log file is PalisadeService.log, in the same folder where Palisade Server Manager is installed. You can access it directly in Windows Explorer, or run Server Manager and click Open .LIC Folder. Either way, scroll to the bottom of the file and you'll see the reason why the license was denied.

Additional keywords: Selective access, License permission, License access, License control, Access control, Dual editions, Dual products, Multiple editions, Multiple products, Multiple network licenses on one server

Last edited: 2015-04-28

5.4. Specifying a File for License Log

Applies to: Palisade Server Manager 6.x
(Concurrent Network licenses and Enterprise Network licenses)

If you have a 7.x network, see Specifying a File for License Log (7.x).

Where is the record of license checkouts and checkins? Can I redirect it to a different location

By default, all logging information is written to a single file:

  • 64-bit Windows: C:\Program Files (x86)\Palisade\NetServer\PalisadeService.log
  • 32-bit Windows: C:\Program Files\Palisade\NetServer\PalisadeService.log

It's easiest to look at this file by clicking View in Server Manager.

This log file actually merges two streams, the lmgrd log and the vendor daemon log. You can tell which is which by the (lmgrd) or (palisade) prefix on each line. You can redirect the vendor daemon log, which contains license checkouts and checkins, to a different location by specifying it in the options file:

DEBUGLOG "c:\full path\file name"

This change is effective after you stop and restart the license service in Server Manager. You don't have to create the file yourself; the license service creates it if it doesn't exist and appends to it if it does.

If you redirect the vendor daemon log to a separate file in this way, please note:

  • Stopping and starting the service does not erase the redirected vendor daemon log file. That log file will continue growing until you purge it.
  • The Advanced Options » View command of Server Manager 7.x will not display the separate vendor daemon log file.

See also: Monitoring License Use on 6.x Network

Last edited: 2015-04-28

Downloadable Versions

1. Guide for 6.x Network Administrators

If you have a 7.x network, see Guide for 7.x Network Administrators.

Language versions:

Applies to: All 6.x products, Concurrent Network and Enterprise Network deployments
(If you have release 5.x, please see Readme Files for 5.x Network.)

The Guide for Administrators is the complete documentation for IT staff who must administer Palisade network software licenses. It includes server setup and client setup instructions, plus FAQs and reference material. The information is available in two formats:

  • When you install the server software, the Guide is installed as Microsoft Word files in all supported international languages, and as an HTML file in English. You can access the Guide on your server by clicking Start » Programs » Palisade Network Server » Guide for Administrators, or by clicking the question mark at the lower left of the Server Manager window. They are also attached to this article, and include any updates since the last release.

  • The full Guide is also included in this Knowledge Base, with each section in a separate article. This makes it easier to search for key words and phrases and go directly to the section that answers your question. The table of contents lets you jump directly to any article, or you can start at the beginning and use the navigation links at the bottom of each article.

If you can't find the information you need, please email Technical Support or phone us at +1 607 277-8000 during operating hours. Please include your software serial number in your email or have it ready when you call.

Last edited: 2016-01-26