HomeNetwork GuidePrinter Friendly Version

Network Guide

Palisade's Network Software for network admins.

1. Server Setup

1.1. License Server System Requirements

Applies to:
Palisade Server Manager 6.x/7.x

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

System Requirements

  • Server Manager 7.5.2: Windows Server 2008 or newer, or Windows 7 or newer.
  • Server Manager 6.0.1–7.5.1: Windows Server 2003 or newer, or Windows XP or newer.

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 Virtual Servers.

Server Manager must not be installed on a server with certain Palisade 1.x or 4.x licenses. See Compatibility with 1.x/4.x Server Software for further information.

Last edited: 2018-01-17

1.2. Choose Network License Type

Applies to:
Palisade Server Manager 6.x/7.x, with Concurrent Networks only.

If you have an Enterprise Network, please go to Activate License.

What are the tradeoffs between an activatable (Trusted Storage) license and a license certificate?

We offer two options for your Concurrent Network license, activatable license (also known as Trusted Storage), and certificate license. (Enterprise Network licenses are offered in activatable form only.)

The majority of our customers use activatable licenses, and that's the type our Operations Department will supply, unless they have other instructions. However, in some circumstances a certificate license may be better for you. Differences between activatable and certificate licenses are minor, and are shown in the table below.

In Step 3 of the server install, you will either activate your license or get a license certificate, depending on which license type you prefer.

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 the chart below to help you choose.

 

Concurrent Network

Activatable
License

Certificate
License

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

Concurrent Network License must be refreshed at least once a year?

No

Yes

Change servers without contacting Palisade?

Yes

No

Reimaging server permanently destroys the license?

Yes

No

Is cloning supported?

No

No

Reverting to a snapshot (in a virtual server) can break the license?

Yes

No

INCLUDE_BORROW, EXCLUDE_BORROW, and BORROW_LOWWATER supported?

No

Yes

Borrowed license can be used by any Windows login on the same workstation, or only by the user who borrowed it?

Any
login

That
user

Redundant server (triad) option available?

No

Yes

Last edited: 2018-01-17

1.3. Step 1: Install Server Software

Applies to:
Palisade Server Manager 6.x/7.x

Do I need to install a new version of Server Manager?

Please check the table. If you already have a version of Server Manager that is compatible with your license and client software, there is no need to install a new one, unless there is a new feature or bug fix you want to take advantage of. See Server Manager Version History.

Server Manager Releases
End User Software Releases
7.5.27.0.0–
7.5.1
6.0.1–
6.3.1
5.0.0–
5.7.1
7.5.2
7.0.0–7.5.1  
6.0.1–6.3.1    

Within a major version, it doesn't matter if the client software is an older or newer version than the server software. For instance, client software or license version 7.0.0, 7.0.1, 7.5.0, or 7.5.1 will all work equally well with any Server Manager 7.0.0 or newer. 6.x licenses and client software will work with Server Manager 7.x, but 7.x client software and licenses will not work with Server Manager 6.x.

Exception: 7.5.2 clients require 7.5.2 license server software and will not work with earlier versions. If you're planning to upgrade your end users to Palisade software 7.5.2, you must first upgrade Server Manager. Earlier versions of client software will still work with the 7.5.2 server software.

How do I perform the server install?

If you have an earlier version of Server Manager already installed, don't uninstall it. The new version will overwrite it, but will carry forward all licenses and option settings.

Upgrading from 5.x: There was no Palisade Server Manager for version 5.x software. The Server Manager installer will disable the old license software but will not remove it. Server Manager will take over the administration of your 5.x licenses. You can delete the 5.x license software if you wish, either through Control Panel » Programs and Features (look for a product name followed by "Network Edition") or by deleting the C:\Program Files (x86)\FLEXnet\Palisade or C:\Program Files\FLEXnet\Palisade folder. Don't create a new 5.x license process; that may render all your licenses unusable.

Simply download the server installer from the link you received in email, and run it as administrator.

Which version of FLEXnet software do you use?

  • Palisade software releases 6.0.0–7.5.1 will install FLEXnet Publisher 11.10 as the licensing system.
  • Palisade software releases beginning with 7.5.2 will install FLEXnet Publisher 11.14.1.2 as the licensing system.

Palisade installs its own copy of lmgrd and the vendor daemon, so there should be no interference with FLEXnet licenses or software from other vendors, provided you don't let different vendors' license software use the same port numbers.

Which folders are created?

Main Palisade folder:

By default, this is C:\Program Files (x86)\Palisade or C:\Program Files\Palisade.

If you already have any Palisade software installed, either server software or end-user software, the installer will use the existing Palisade folder. But if this is the first Palisade install on this server, the installer will suggest the default folder for the install, but will let you select a different install folder. Caution! Don't install to a folder with an at-sign (@) in its name. The licensing software will not work if installed in such a folder.

Subfolders NetServer and System will be created under the main Palisade folder, unless they already exist. System contains files used by all Palisade software. NetServer contains files for the network license server:

  • 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.)
  • lmgrd.exe, Palisade.exe, and other components of the licensing software.
  • 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 holds the lmgrd port number for all license types. If you have a certificate license, the actual license will also be in this file. Server Manager rewrites the file when you change server options.
    • 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 Site-Standard FLEXnet Options File, Options File, and Access Control in Concurrent Network.

Caution: Don't 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.

FLEXnet Publisher folder:

The folder C:\Program Files (x86)\Common Files\Macrovision Shared\FLEXnet Publisher or C:\Program Files\Common Files\Macrovision Shared\FLEXnet Publisher holds the FNPLicensingService.exe file, which runs as the service Flexnet Licensing Service. All vendors' lmgrd programs use this file. All vendors' installers will update this file if the new install carries a later version than the existing file.

FLEXlm folder:

Beginning with Palisade Server Manager 7.5.2, the log file is written to C:\ProgramData\FNP\FLEXlm\PalisadeService.log. In older versions of Server Manager, PalisadeService.log was in the Palisade\NetServer folder.

Which services or processes are created?

  • In the Palisade\NetServer folder, lmgrd.exe runs as the Palisade License Service. You may see a second copy of lmgrd.exe in Windows Task Manager.
  • Also in the Palisade\NetServer folder, the vendor daemon palisade.exe runs in background, but not as a service.
  • In the Flexnet Publisher folder, the FNPLicensingService.exe file runs as the service Flexnet Licensing Service. All vendors' lmgrd programs use this service.

All of these run as system processes; if you want to find them in the Windows Task Manager, select the Show processes from all users button.

Last edited: 2018-02-26

1.4. Step 2: Set Options—Port Numbers

Applies to:
Palisade Server Manager 6.x/7.x

Click Start » All Programs » Palisade Network Server » Server Manager. Server Manager will update any Paliasde 5.x license process.

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 activating your license or getting your license certificate (depending on your license type).

Which port numbers does the license process use?

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 without restriction. 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/6.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 (a) every product including Palisade must specify a unique lmgrd port number, or else (b) every product including Palisade must leave the lmgrd port number unspecified ("Dynamic").

I left both ports as dynamic. How can I determine which ports the 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.

Caution: There's no guarantee that the same ports will be used the next time the service starts up.

How can I 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. Create a new Palisade_NetworkClient.ini file to replace the old one, even if you're not installing any new clients at this time. See Prepare the Client Install.
  5. In a Concurrent Network, change the lmgrd port number on any clients that have already been installed. See Redirecting Concurrent Clients to a New Server or Port Number.

How can I set or change the Palisade vendor daemon port?

Server Manager 6.2 and newerServer Manager 6.0 and 6.1
  1. In Server Manager, click Options.
  2. On the Options screen, under Communication Port Number (vendor daemon), specify a port number (not otherwise used) or select Dynamic.
  3. Click OK, then Stop Service, then Start Service.
  1. In Server Manager, click Open LIC Folder.
  2. Open PalisadeNetwork.lic in Notepad or another plain-text editor.
  3. To specify a port, add PORT=portnumber at the end of the VENDOR line in both files. To let the FLEXnet software choose a port dynamically, remove the PORT specification from the VENDOR line.
  4. Repeat the same edit on Server.lic. Server.lic must use the same vendor daemon port as PalisadeNetwork.lic.
  5. In Server Manager, click Stop Service, then Start Service.

There is no need for a new INI file if you change the vendor daemon port but not the lmgrd port.

There's no software setting on the client for the vendor daemon port. (In the initial handshake when an end user starts the client software, it sends a message through the lmgrd port, and the return message from the server tells the client software which vendor daemon port to use.) However, if you previously found that you needed to open the vendor daemon port in the firewall of any installed clients, you will need to update the client firewall settings.

See also: Network Ports and Firewalls for recommended firewall settings.

Last edited: 2017-11-10

1.5. Step 2: Set Options—Borrowing

Applies to:
Palisade Server Manager 6.x/7.x, with Concurrent Networks only.

Can end users borrow a network license for use off network?

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 Choose Network License Type 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.

What should I consider before making that option available?

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.)

  • Therefore, borrowing is almost always a bad idea if your license is for one concurrent user, because no one else will be able to run until the borrower returns the 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 end-user 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.

How do I enable the borrowing option?

In Server Manager, click Options, and in the bottom section select Allowed. For the reasons given above, most administrators set a maximum of 7 or 14 days.

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: 2017-11-10

1.6. Step 3: Activate Network License

Applies to:
Palisade Server Manager 6.x/7.x, with activatable (Trusted Storage) licenses only.

If your license is the certificate type, see Get License Certificate. To decide between the two kinds, see Choose Network License Type.

My license is the activatable type. How do I activate it? If I have multiple "seats", can I split them among servers?

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.

Next step: Prepare the Client Install.

Last edited: 2017-11-10

1.7. Step 3: Get License Certificate

Applies to:
Palisade Server Manager 6.x/7.x, with certificate licenses only.

If your license is the activatable type, see Activate Network License. To decide between the two kinds, see Choose Network License Type.

I prefer a certificate license. How do I get it?

  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: 2017-11-10

1.8. Step 4: Prepare the Client Install

Applies to:
Palisade Server Manager 6.x/7.x

I've downloaded the installer from the link you emailed to me. Do I need anything else to install the end-user software on client computers?

Yes, you need a file called Palisade_NetworkClient.ini. You create this in Palisade Server Manager. After you install a network license for the first time, or after you change server name or port number, Server Manager may offer to create the Palisade_NetworkClient.ini file; if it doesn't, just click the Create Client.INI button.

(If you have a 5.x network license, the process is the same but the file is named Client.ini.)

I already have an INI file. Do I need to create a new one?

You always need a new INI file after you change the LMGRD port number or change to a server with a different name.

If you're just installing a new license, you may or may not need to create a new INI file, depending on the license type:

  • For 6.x/7.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/7.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 all Enterprise Networks, the 6.x/7.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 Server Identified by FQDN or IP Address

How is the INI file used?

The client installer reads it to find out how the client should connect to license your server. The installer stores that information in the System Registry, in HKLM\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE or HKLM\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE, so the end-user software doesn't look for the INI file after installation.

The EXE and INI files must be in the same folder during install, but this can be almost anywhere—in a network share, on a USB stick, burned to a CD, etc. (It's more complicated with the MSI installer; see Scripting the Client Install.)

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: 2017-12-03

2. Client Setup

2.1. Concurrent Network Client Setup

Applies to EXE installer for:
Concurrent Network client software 6.x/7.x
Course License end-user software (network clients and independent workstations) 6.x/7.x

If you're using the MSI installer, see Scripting the Client Install.

How do I install the Concurrent Network end-user software with the EXE installer?

Full administrative rights are required for the client install. For system requirements on client computers, see Windows and Office Versions Supported by Palisade.

To perform a full install or upgrade install of end-user software, browse to the network share or other location where you placed the EXE and INI files in Prepare the Client Install. Either run the EXE installer there, or copy the installer and the INI file to the client computer and run the copy. Either way, in Vista or Windows 7 or newer, right-click the EXE installer and select Run as administrator; in Windows XP, you can just double-click the installer.

The installer copies the server information from the INI file to the System Registry key HKLM\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE or HKLM\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE. The client installer doesn't connect to your server during install, but just assumes the INI file is correct. After install, the INI file is not used.

You can install the Concurrent Network client on any number of computers.

If I'm upgrading, do I need to uninstall the old version first?

If you're upgrading to a new major version, such as 6.x to 7.x, you can choose to uninstall the old version immediately, or leave it in place until the whole company has been upgraded. If you uninstall the old version later, the uninstall will not affect the new version.

If you're upgrading within the same major version, such as 7.x to a later 7.x, the new version will automatically overwrite the old version.

How can I verify the end-user install?

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, which the installer copied from the INI file to the Registry. If the server information is incorrect, the server is unavailable, or the server software isn't running, the client software will say that it cannot reach the server. To correct this information on the client, see Redirecting Concurrent Clients to a New Server or Port Number.

See also:

Last edited: 2017-11-10

2.2. Enterprise Network Client Setup

Applies to EXE installer for:
Enterprise Network client software 6.x/7.x

If you're using the MSI installer, see Scripting the Client Install.

How do I install the Enterprise Network end-user software with the EXE installer?

Full administrative rights are required for the client install. For system requirements on client computers, see Windows and Office Versions Supported by Palisade.

To perform a full install or upgrade install of end-user software, browse to the network share or other location where you placed the EXE and INI files in Prepare the Client Install. Either run the EXE installer there, or copy the installer and the INI file to the client computer and run the copy. Either way, in Vista or Windows 7 or newer, right-click the EXE installer and select Run as administrator; in Windows XP, you can just double-click the installer.

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 INI file. If the activation succeeds, then when the user runs the software it will start up without any licensing messages.

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.

If I'm upgrading, do I need to uninstall the old version first?

If you're upgrading to a new major version, such as 6.x to 7.x, you can choose to uninstall the old version immediately, or leave it in place until the whole company has been upgraded. If you uninstall the old version later, the uninstall will not affect the new version.

If you're upgrading within the same major version, such as 7.x to a later 7.x, the new version will automatically overwrite the old version.

What should I do if I get a message that activation failed?

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; or use the desktop icon if there is one. In the application, click Help » License Manager and then Activate.

  • If the server information or Activation ID in the INI file was incorrect, enter the correct 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.

How can I verify the end-user install?

If you got no error messages during install, just launch the software by double-clicking the desktop icon, if present, or single-clicking the shortcut. On new installs, after some initialization you should get a popup headed "Welcome to" and the name of the app. On upgrade installs, depending on the application settings, you'll either get that Welcome screen, or go straight to Excel, with a new tab in the ribbon for the Palisade software.

See also:

Last edited: 2017-11-10

2.3. Scripting the Client Install

Applies to MSI installer for:
Concurrent Network client software 6.x/7.x, including Course License network clients
Enterprise Network client software 6.x/7.x

How can I script the Concurrent Network or Enterprise Network client install?

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 the appropriate one of these articles:

For the client install, you will need the INI file that was described in Prepare the Client Install. 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 INI file. It must be the actual path—constructs like .\ won't work.

  • 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="organization"

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

Either way, replace C:\TEMP following SETUPEXEDIR with the folder that contains Palisade_NetworkClient.ini. It must be the actual path; ".\" and similar won't work. 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.

Variation — no desktop shortcuts:

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 DTOPSHORTCUTS=0 parameter:

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

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

Last edited: 2017-12-21

3. FAQs

3.1. Citrix and Remote Desktop

Applies to:
Palisade Concurrent Network software 6.x/7.x

Other license types (Enterprise Network or Standalone) will not 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.

Additional keywords: Citrix, Citrix server, Installation on Citrix

Last edited: 2017-11-10

3.2. Virtual Servers

Applies to:
Palisade network software 6.x/7.x

Does not apply to: Palisade Custom Runtime licenses, which are designed not to activate on virtual servers.

Are virtual servers supported?

Yes. (Cloning is not supported.) You should find that an activatable or certificate license works just fine. As always, if you have any doubts, 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 a problem is unlikely. See Get License Certificate to obtain a certificate license.

Warning! Just as with a physical server, if your license is the activatable type, you must not delete the virtual server or reformat it without first deactivating your Palisade network license. Doing that would permanently destroy the license. If you reimage your server periodically, get a certificate license from Palisade.

Caution! If you take a snapshot, and later revert to that snapshot, an activatable license may break, and users won't be able to run. To fix it, see Repairing a Broken Network License. If you plan to continue to use your virtual server in that way, request a certificate license to replace your activatable 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 for 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: 2018-01-18

3.3. Internet Needs

Applies to:
Palisade Network software 6.x/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 Deactivation, not needed for Manual Activation and Deactivation. (For Automatic Activation and Deactivation, see Network Ports and 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: 2017-11-10

3.4. Server Identified by FQDN or IP Address

Applies to:
Palisade network software 6./7.x

Can clients reach our server by FQDN (fully qualified domain name) or IP address?

Yes, these are both compatible with the FLEXnet licensing software.

Edit the INI file, after you create it but before you run the client installer. On the SERVERNAME line of the INI file, 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.

Don't put an FQDN on the SERVER line of the Server.lic file; that line must always carry either the plain server name or the placeholder this_host.

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 Using a Concurrent Network License Off Network (Borrowing).

Last edited: 2017-11-10

3.5. Multiple License Servers

Applies to:
Palisade Concurrent Network software 6.x/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, not dynamically every time the application runs.

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 new clients, the easiest thing is to edit the SERVERNAME line in the INI file on the server and use the modified file with the client installer. For existing clients, use one of the methods in Redirecting Concurrent Network Clients to a New Server or Port Number.

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.)

I'm planning for multiple servers eventually, but only one of them is on line yet. If I put all of them in the INI file, will that cause a problem?

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 (DR) server, you can pre-configure clients to reach a DR server if the regular server is off line. All you'll need to do if the regular server fails is bring the DR server on line, and clients will connect to it automatically when they launch the software. (If the DR 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: 2017-11-10

3.6. Redundant Servers

Applies to:
Palisade Concurrent Network software 6.x/7.x

Is a redundant server system supported?

Yes, FLEXnet Publisher provides for three-server (triad) redundancy. Please note that Palisade has no direct experience with that setup and may not be able to troubleshoot problems; however, we do have at least one customer using that setup successfully.

When you have a triad of redundant servers, they are called primary, secondary, and tertiary, according to their order in the license file. The three servers talk to each other periodically, and licenses will be served whenever two or three of them are running. The primary is normally the master, responsible for parceling out licenses and for writing logs. If the primary goes down, the secondary takes over its duties. When the primary comes back up, it resumes the duties of master, provided you have that option in the license file (below).

How is the license created?

Redundant server setups must be certificate licenses. You install Palisade Server Manager on all three servers, and provide the Host ID information from all three to Palisade Technical Support. We create a license file with information on all three servers and send it to you.

We recommend that you add the optional keyword PRIMARY_IS_MASTER on the first SERVER line in the license file. This keyword has two effects:

  • With PRIMARY_IS_MASTER present, you can start and stop the three servers' license processes in any order; without it, you must start them in order.
  • With PRIMARY_IS_MASTER present, the primary will resume the master's duties when it comes back up after an outage. Without this keyword, the secondary, which took over the master's job when the primary went down, will continue as master unless it goes down itself—if that happens, the primary will become master again.

When you use PRIMARY_IS_MASTER with an LMGRD port number, the port number comes before PRIMARY_IS_MASTER. Though you don't have to use the same port number for all three servers, it simplifies administration and troubleshooting if you do. As usual, if you omit the LMGRD port number, the server will select a port in the range 27000–27009 dynamically. A specimen license file is attached to this article.

After adding PRIMARY_IS_MASTER, you install the same file on all three servers. You then start the license server processes on the three servers.

How does client software know about the redundant server triad?

For clients, specify the three servers, separated with commas, not semicolons. Examples:

27010@Alpher,27010@Bethe,27010@Gamow
@Alpher,@Bethe,@Gamow

For new clients, the easiest thing is to edit the SERVERNAME line in the INI file on the server and use the modified file with the client installer. For existing clients, use one of the methods in Redirecting Concurrent Network Clients to a New Server or Port Number—but with commas rather than semicolons.

Last edited: 2017-12-02

3.7. Site-Standard FLEXnet Options File

Applies to:
Palisade Concurrent Network software 6.x/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 Server.lic file after you change options, it will remove an OPTIONS field if it finds one.

For supported keywords in the options file, see Options File and Access Control in Concurrent Network.

Last edited: 2017-12-03

3.8. Network Ports and Firewalls

Applies to:
Palisade network software 6.x/7.x

How should I set up my firewalls?

Most of our customers don't need to make any changes in their firewall settings at all. But if you have a restrictive firewall, you may need to change some settings to let your Palisade network software run.

TL;DR version: On server, give Palisade.exe and lmgrd.exe send/receive privilege; if Automatic Activation fails use Manual Activation instead. On client, give send/receive privilege to PalFlexServer6.exe or PalFlexServer7.exe, depending on your software version.

How should I configure the firewall on my license server?

Your license server does two jobs: it activates your network license with Palisade's license server, and it provides licenses to the client computers.

Server's Internet communications with Palisade (when activating or deactivating a license):

If your firewall settings prevent Automatic Activation of your license, we recommend that you use the manual procedure rather than make firewall changes. For Manual Activation and Manual Deactivation instructions, see Activate Network License and Deactivating a Network 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 our IP addresses in your firewall exceptions, because they could change without notice.

Server's communications with end-user computers (clients):

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, specify them as described in Port Numbers, and then open those in the server firewall for send and receive.

How should I configure the firewall on client (end-user) computers?

Client computers never need to communicate with Palisade's server. They do need to communicate with your license server. Concurrent Network clients do this while they run @RISK or other Palisade applications; Enterprise Network clients do this only during install or when updating the annual license.

If your client firewall is blocking communication with the server's license process, it's simplest to list PalFlexServer6.exe or PalFlexServer7.exe (depending on your software version) as an exception for send and receive in the client computer's firewall. If you prefer to open specific port numbers, see Set Options—Port Numbers to set specific lmgrd and vendor daemon ports on your server, and then open those ports for send and receive on the client.

Last edited: 2017-12-03

3.9. FLEXnet from Other Vendors

Applies to:
Palisade network software 6.x/7.x

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

Current Palisade network licenses are built on FLEXnet Publisher 11.14.1.2. (Palisade releases 6.0.1–7.5.1 used 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: 2018-01-19

3.10. Multiple Palisade Licenses

Applies to:
Palisade network software 6.x/7.x

What if I already have a Palisade network license on my server?

This depends on the major version of Server Manager and of the license. The major version of Server Manager is the first digit of the Server Manager version displayed in the title bar. (If none is displayed, the major version is 6.) The major version of the license is the first digit of the serial number, or the first numeric in the Activation ID.

New major version:

If the major version of the new license is greater than the major version of Server Manager, you must upgrade Server Manager. You might also want to upgrade Server Manager to get new features or bug fixes. 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.
  4. Download the client installer to the folder where you're keeping client installers.
  5. Activate your new Activation ID or get a new license certificate, depending on your license type. The email with your new license information should tell you which type of license you have.
  6. Install the new client installer on the clients; see Client Setup procedure.

It's not possible to have multiple versions of Palisade Server Manager installed on the same server, but there's no reason to do it anyway. A later version of Server Manager can handle all the licenses that an earlier version can handle.

Not a new major version:

If the major version of the new license is less than or equal to the major version of Server Manager, you can follow this shorter procedure:

  1. Download the client installer to the folder where you're keeping client installers.
  2. Activate your new Activation ID or get a new license certificate, depending on your license type. The email with your new license information should tell you which type of license you have.
  3. Install the new client installer on the clients; see Client Setup procedure.

See also:

Last edited: 2017-12-03

3.11. Compatibility with Palisade 1.x/4.x Server Software

Applies to:
Palisade network software 6.x/7.x

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 network licenses, for software releases 5.x and newer, 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 newer license.

The "Palisade concurrent" licenses did not use FLEXlm or FLEXnet and will not conflict with later Palisade network licenses.

Last edited: 2017-11-10

3.12. Keeping Each User to the "Right" License

Applies to:
Palisade network software 6.x/7.x

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 INI file for each Enterprise Network Activation ID. Then, when you install an Enterprise Network client, you simply use the INI file 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 in Access Control in Concurrent Network.

Last edited: 2017-12-03

3.13. Moving Concurrent Network to a New Server

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

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 INI file. See Server Setup procedure.

  3. Redirect the existing clients (end user computers) to the new server for licensing. See Redirecting Concurrent Clients to a New Server or Port Number.

    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 Deactivating a Network License. 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 Deactivating a Network License. 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 INI file. See Server Setup procedure.

  4. Redirect the existing clients (end user computers) to the new server for licensing. See Redirecting Concurrent Clients to a New Server or Port Number.

    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 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 INI file. See Get License Certificate and Prepare the Client Install.

  5. Redirect one existing client (end user computer) to the new server for licensing; see Redirecting Concurrent Clients to a New Server or Port Number. 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 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: 2017-12-03

3.14. Deactivating a Network License

Applies to:
Server Manager 6.x/7.x, managing 5.x–7.x licenses

This article is about deactivating (returning) a network license. If you're looking for how to activate a license, you'll find full details in Activate Network License.

When would you want to deactivate a license?

  • When you're planning to change servers, reimage your server, or upgrade your server's 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, open Server Manager, select the license in the lower window, and 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 select the location of the saved file.

    Creating the request file does not deactivate the license but merely makes it unusable. You must complete the deactivation via the Web or email.

Via Web
(faster)
Via Email
(response during business hours)
  1. At our activations and deactivations Web page, click Browse, select the saved DActRequest.xml file, and click Submit.

  2. Click the button to download the response file.

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

  1. 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. The license is deactivated in Palisade's database, using your request file, and the license is now available for transfer to another server. But if you're keeping this server, please proceed to the next step.

  1. In Server Manager, on the Manual Deactivation screen, click Load Deactivation Response File and load the ResponseDAct.xml file you received from the Web page or 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 (DActRequest.xml). 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, via Automatic or Manual, 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: 2018-02-16

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

Applies to:
Palisade Concurrent Network software 6.x/7.x

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.

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

Please see Set Options—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. See the client section of Network Ports and Firewalls.

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 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 INI file that you created on the new server or after changing LMGRD port on the existing server.

As an alternative to steps d and e, 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:

  • 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

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: 2017-11-10

3.16. Renewing Enterprise Network on the Same Server

Applies to:
Enterprise Network software 6.x/7.x

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 Prepare the Client Install.

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 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 for Enterprise Network clients.

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: 2017-11-10

3.17. Moving Enterprise Network to a New Server

Applies to:
Enterprise Network software 6.x/7.x

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 Prepare the Client Install.

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 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 for Enterprise Network clients.

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: 2017-11-10

3.18. Adding Users to Network License

Applies to:
Palisade network software 6.x/7.x
Palisade network software 5.x when managed by Server Manager

How can I add users to my existing network license?

Look in Server Manager to see whether the existing license 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 Activate Network License for the activation process. Network Licenses Installed on This Server in Server Manager 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: 2017-11-10

3.19. Repairing a Broken Network License

Applies to:
Palisade Concurrent Network software 6.x/7.x
Palisade Concurrent Network software 5.x with Server Manager 6.x/7.x

My network license doesn't show in the lower window of Server Manager, but when I click the Unusable Licenses button I see it there, with a "broken" status. How can I fix it?

First, a word about prevention. If you're running a virtual server, and you have an activated license, reverting the server to a snapshot will break the license. To avoid this, assuming you want to continue using snapshots and reverting to them, contact Palisade Technical Support to surrender your activated license for a certificate license.

To repair the license, please follow this procedure:

  1. In Palisade Server Manager click the magnifying glass in the lower left corner to open the Advanced Options. Click the View Button, find your Activation ID (called "Entitlement ID" in the file), and note the adjacent Fulfillment ID. Copy/paste it with your mouse if at all possible, instead of trying to look at it and type it, because there are usually both single and double underscores.

  2. Click the Execute button. In the box that appears, paste this text, all as one line:

    -repair xxx -comm soap -commServer http://service.palisade.com/flexnet/services/ActivationService?wsdl

    Caution! Copy/paste the whole line, including the leading hyphen.

  3. Replace the xxx in that line with the Fulfillment ID, and click the OK button.

  4. A Notepad window will open, after a delay of up to 60 seconds. Look at the last couple of lines.

    • If the word SUCCESSFULLY appears, the command succeeded. (Ignore "ERROR 0" or "Error Output".) Close the Notepad window and Server Manager. Ignore the rest of this procedure.
    • If SUCCESSFULLY does not appear, the Automatic Repair failed; continue these steps to do a manual repair.
  5. Click File » Save As and save the PalLicenseCommand.txt file to your desktop or another convenient location.

  6. Close the Notepad window, then click Execute again and paste this text, all on one line:

    -repair xxx -comm flex -gen C:\Windows\Temp\RequestRepair.xml

    Caution! Copy/paste the whole line, including the leading hyphen.

  7. Again, replace xxx with the Fulfillment ID. Click the OK button, and wait for the Notepad window to appear.

  8. Click File » Save As and save the file to your desktop as PalLicenseCommand2.txt.

  9. Close the Notepad windows.

  10. Send an email to Palisade Technical Support with your Activation ID and brief text requesting a repair. Please attach C:\Windows\Temp\RequestRepair.xml as well as PalLicenseCommand.txt andPalLicenseCommand2.txt to the email. Attach them as files; don't copy the text into the body of your email. Tech Support will send you back a response file and instructions.

Last edited: 2017-12-03

3.20. Recovering When a Concurrent Network Client Crashes

Applies to:
Palisade Concurrent Network software 5.x/6.x/7.x

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

No specific action is necessary or possible.

When a 6.x or newer client crashes, the license is reserved for ten minutes for that same client, and then returns to the available pool. If 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 or unloads the add-in, the license returns to the available pool. If the crashed client doesn't come back on line or doesn't 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.

When a 5.x client crashes, the Concurrent Network license that was used by that client is not usable, not even by that client, for two hours and then automatically returns to the pool of available licenses. This is true regardless of the version of the server software. There's no way to speed up that process.

See also: Recovering When a Concurrent Network Client Is Idle

Last edited: 2018-02-27

3.21. Recovering When a Concurrent Network Client Is Idle

Applies to:
Palisade Concurrent Network software 5.x/6.x/7.x, used on network

If the license was borrowed, see Recovering a Borrowed License.

A user opened the Palisade software but isn't actually using it; it's just sitting idle on the computer. Can we recover that license for someone who needs it?

The best practice is to educate your users so that this situation doesn't occur. Explain that use of the software is limited to a certain number of users and ask everyone to cooperate in releasing a license when they're not using it.

Suppose people are careless or forget? You can contact the user, go to the computer, or log on remotely, and do any of these to release the license:

  • Close our software while leaving Excel open, through Utilities » Unload. If two or more of the DecisionTools are open, @RISK and PrecisionTree for example, the license is released when the last one is closed.
  • Close Excel, and Palisade software will close too. If the workbook has been changed, Excel prompts you to save the changes.
  • Crash Excel by killing all instances of Excel.exe in Task Manager, and wait ten minutes. See Recovering When a Concurrent Network Client Crashes.

We recommend the first of these, of course. Although it takes a few seconds more, the workbook remains open, so there is no loss of any work done.

Last edited: 2018-02-27

3.22. Using a Concurrent Network License Off Network (Borrowing)

Applies to:
Palisade Concurrent Network software 6.x/7.x

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, by setting the borrowing option in Server Manager.

For end-user instructions, after you have enabled borrowing,see Borrowing a Concurrent Network License for Use Off Network.

Last edited: 2017-12-03

3.23. Recovering a Borrowed License

Applies to:
Palisade Concurrent Network software 5.x/6.x/7.x

A user borrowed a license for a long period. How can we get that license back sooner?

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 or force an early return.

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 in Server Manager. Please see Set Options—Borrowing. 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: 2017-12-03

3.24. Monitoring Network License Use

Applies to:
Palisade Concurrent Network software 6.x/7.x

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. Here is some assistance in interpreting the display.

Concurrent License Status

The long Concurrent License Status section displayed by the Status button 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.

Concurrent License Currently 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 Licenses Currently 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 Licenses Currently 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 (also called Trusted Storage). 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.

Concurrent License Usage History

The Status button 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, click the View button in Sever Manager's Advanced Options. Scroll to the bottom of the Notepad window that opens. OUT lines show when end users launched the software; IN lines show when end users closed Excel, or clicked Utilities » Unload Add-In, to release the license.

If your Concurrent Network is the activatable type, then borrowing or returning is indicated by an OUT or IN line with a user name of ACTIVATED LICENSE(S).

If your Concurrent Network is the certificate type, then borrowing a license is indicated by an IN line immediately followed by an OUT line, and returning a borrowed license is indicated by a REMOVING line immediately followed by an IN line. (Ignore "by administrator request" on the REMOVING line; the return was not necessarily done by an administrator.)

Enterprise License Status

If you have any Enterprise licenses on this server, a brief Enterprise License Status section appears in the display when you click the Status button.. It shows each Enterprise Network Activation ID, with the number of activated users and the total number of users allowed on the license.

Enterprise License Usage History

The Status button shows the number of activated clients and the total number of allowed users, but it does not show which clients have been activated. To show the Enterprise Network clients since the license service was last started, click the View button in Sever Manager's Advanced Options. 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.

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.

The system denied a license to a user. How can I find out the reason?

If the problem is simply that all seats are in use, the user will see a message saying as much. But if seats are currently available and you're using FLEXnet options to control access, see the section Troubleshooting License Denials in the article Access Control in Concurrent Network.

Last edited: 2017-12-03

3.25. Changing Standalone Workstation to Concurrent Client

Applies to:
Palisade software 6.0.1–6.3.1, 7.x

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 Set Options—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.

The conversion procedure requires full administrative rights. You can perform it via remote login to the end user's computer if you wish. (To keep this simple, we're presenting just the Regedit files for the whole DecisionTools Suite. If you have just @RISK or another product, rather than the whole Suite, the extra "License to Use" keys will do no harm.)

  1. Download the appropriate file attached to this article. The files are named for 32-bit or 64-bit Windows on the client computer (not necessarily your computer), and for Palisade software release 6.x or 7.x. (To keep this simple, we're presenting just the Regedit files for the whole DecisionTools Suite. If you have only @RISK or another product, rather than the whole Suite, the extra "License to Use" keys will do no harm.)

  2. Double-click the downloaded file to open it. 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. Examples:
    28162@SERVER21;C:\\Program Files (x86)\\Palisade\\System
    @SERVER21;C:\\Program Files (x86)\\Palisade\\System
    28162@SERVER21;C:\\Program Files\\Palisade\\System
    @SERVER21;C:\\Program Files\\Palisade\\System

  3. Save the file with a REG extension instead of TXT, 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: 2017-12-03

3.26. Changing Concurrent Client to Standalone Workstation

Applies to:
Palisade software 6.x/7.x

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: 2017-11-13

3.27. Changing Standalone Workstation to Enterprise Client

Applies to:
Palisade software 6.0.1–6.3.1, 7.x

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. 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 your license 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 license server.

Last edited: 2017-12-02

4. Reference

4.1. Server Manager Main Screen

Applies to:
Server Manager 6.x/7.x

When you launch Palisade Server Manager, it presents two categories of information on the main screen: information about the server itself, and information about the licenses on the server. You can enlarge the screen by dragging the borders, even though the borders don't look draggable, or maximize the screen by the usual windows methods. Text in either window can be copied with Ctrl+C; first use your mouse to select text, or press Ctrl+A to select all the text in a window.

Special case: If Server Manager detects a Palisade 5.x license service running, before it can present that screen it will need your permission to shut down that service and start up the current version of the license service. See Upgrading from 5.x in Install Server Software.

Network Server Information window

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.

Text in this window can be copied with Ctrl+C; first use your mouse to select text. You can still do this after pressing the Status button (below).

Refresh button

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. Also click this button if you edit the options file directly.

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".

Status button

While the license service is running, click this button to show details of current license use in your Concurrent Network or Enterprise network. The details appear in the Network Server Information window, not in a separate popup. The information is provided by FLEXnet and is not very easy to interpret; see Monitoring Network License Use for details. To update the information, click the Status button again, not the Refresh button.

The Status button is grayed out while the license service is stopped.

Start Service button
Stop Service button

If the license service is currently running, the 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.

Options button

This button opens a dialog where you can set the ports used for communicating with clients and determine whether to allow borrowing. See Set Option—Port Numbers and Set Options–Borrowing 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. You don't need to click the Refresh button.

Network Licenses Installed on This Server window

This box lists all Palisade activated and certificate licenses on this server, both Concurrent and Enterprise type, for releases 5.0 and newer, 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 the Unusable Licenses button, below.

Activate button

Click this button to activate an activatable network license. For more details, see Activate Network License.

Deactivate button

Use this button to deactivate a network license. (The button is grayed out if the currently selected license is the certificate type.) For details, see Deactivating a Network License.

Create Client.ini button

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 Prepare the Client Install for further details of when and how to use this button.

Unusable Licenses button

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, or a license broken when you reverted a virtual server to a snapshot. 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.

Open LIC Folder button

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.

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.

Advanced Options button

The Advanced Options button looks like a zoom-in icon, not a magnifying glass. Please see Server Manager Advanced Options.

Last edited: 2017-12-03

4.2. Server Manager Advanced Options

Applies to:
Server Manager 6.x/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 the Status button: For details, please see Monitoring Network License Use.

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 normally for use by Palisade Technical Support during a remote support session. However, you also need it to follow the instructions in this Guide for repairing a network license.

Last edited: 2017-12-01

4.3. Options File

Applies to:
Palisade network software 6.x/7.x

Finding and Editing the 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 the Refresh button 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.)

Controlling End-User Access

This complicated topic is explained in the separate article Access Control in Concurrent Network.

Maximum Allowed Borrowing Period

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 Set Options—Borrowing.

Specifying a File for License Log

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

  • Server Manager 7.5.2: C:\ProgramData\FNP\FLEXlm\PalisadeService.log
  • Server Manager 6.0.1–7.5.1 in 64-bit Windows: C:\Program Files (x86)\Palisade\NetServer\PalisadeService.log
  • Server Manager 6.0.1–7.5.1 in 32-bit Windows: C:\Program Files\Palisade\NetServer\PalisadeService.log

It's easiest to look at this file by clicking the View button in Server Manager; this file forms the last section of that display.

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 Neitwork License Usage

Last edited: 2018-01-17

4.4. Access Control in Concurrent Network

Applies to:
Palisade Concurrent Network software 6.x/7.x

You can limit access to your Concurrent Network licenses by adding lines to the options file. 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. See Method 1 below.

  • 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. See Method 2 below.

In this Article:

Features

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 Status 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 Network License Usage.)

The feature names for 7.x software all contain 70, and the feature names for 6.x software all contain 60, regardless of the actual 7.x version number. This is why you don't need a new license when you perform a minor upgrade, from one 7.x release to a later 7.x release, and why you do need a new license when you upgrade between major versions, such as 6.x to 7.x.

Here is the full list of feature names:

  • DecisionTools70_Industrial, DecisionTools70_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.
  • @RISK70_Industrial, @RISK70_Professional, @RISK70_Standard
  • BigPicture (no "70")
  • Evolver70_Industrial, Evolver70_Professional
  • NeuralTools70_Industrial, NeuralTools70_Professional
  • PrecisionTree70_Industrial, PrecisionTree70_Professional
  • StatTools70_Industrial, StatTools70_Professional
  • 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 @RISK70_Industrial USER Stan<
INCLUDE @RISK70_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 @RISK70_Industrial USER Stan
INCLUDE @RISK70_Industrial USER Michelle
INCLUDE @RISK70_Industrial USER Fernando
INCLUDE @RISK70_Industrial HOST EC-Server
INCLUDE @RISK70_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.

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

INCLUDE Evolver70_Industrial HOST Atlantis
EXCLUDE Evolver70_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."

Caution: If you have any INCLUDE...USER lines in your options file for a feature, and your network license is the activatable type, user access to run the software on network will follow the INCLUDE...USER lines, but no one will be able to borrow a license of that feature for off-network use. This does not apply to certificate-type licenses, and it does not apply to INCLUDE...HOST lines with either type of license.

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 @RISK70_Industrial USER Stan
EXCLUDE @RISK70_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 @RISK70_Industrial USER Stan
EXCLUDE @RISK70_Industrial USER Michelle
EXCLUDE @RISK70_Industrial USER Fernando
EXCLUDE @RISK70_Industrial HOST EC-Server
EXCLUDE @RISK70_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.

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 Lawyers Michelle Mark Doug Cristina Robson
GROUP Doctors Stan Sally
HOST_GROUP ThirdFloor Asus14132 Asus14133 Asus14134 \
    Asus14135 Asus14136
INCLUDE DecisionTools70_Industrial HOST_GROUP ThirdFloor
INCLUDE DecisionTools70_Industrial GROUP Doctors
INCLUDE DecisionTools70_Industrial USER Vince
INCLUDE StatTools70_Professional GROUP Lawyers
INCLUDE StatTools70_Professional USER Vince

This lets the ThirdFloor group of computers, the Doctors group of users, and user Vince use a DecisionTools70_Industrial license, but no one else can. The Lawyers group, Vince, and no one else can use a StatTools70_Professional license. The ThirdFloor and Doctors groups, and Vince, can still use StatTools Industrial, as part of the DecisionTools Suite. If all the DecisionTools70_Industrial licenses are in use, the Third Floor and Doctors groups will not be able to run StatTools under the StatTools70_Professional license, but Vince and the Lawyers group will. (Vince, who was previously using the DecisionTools Suite license, can use Select License 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.

Caution: If you have any INCLUDE...GROUP lines in your options file for a feature, and your network license is the activatable type, user access to run the software on network will follow the INCLUDE...GROUP lines, but no one will be able to borrow a license of that feature for off-network use. This does not apply to certificate-type licenses, and it does not apply to INCLUDE...HOST_GROUP lines with either type of license.

More Options for On-Network Use

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

MAX 2 DecisionTools70_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, even if some licenses are not in use.

RESERVE 2 DecisionTools70_Professional HOST_GROUP Wizards

Two DecisionTools Professional licenses are reserved for the use of the computers in the Wizards group. Another authorized user who tries to use the license from another computer will succeed only if the number of free licenses, plus the number currently in use by computers in the Wizards group, is greater than 2.

RESERVE 1 DecisionTools70_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 her to have a standalone license on her 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 DecisionTools70_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 DecisionTools70_Professional USER Heather
INCLUDE_BORROW DecisionTools70_Professional GROUP Managers

Heather, and members of the Managers group, can borrow a DecisionTools70_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, above.)

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 DecisionTools70_Professional USER Denise
EXCLUDE_BORROW DecisionTools70_Professional HOST_GROUP Contractors

Denise, on any computer, and anyone on computers in the Contractors group, cannot borrow a DecisionTools70_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 why the license was denied.

Last edited: 2017-12-02

4.5. Server Software Version History

Release 7.5.2, January 2018

New features:

  • Beginning with this release, Palisade software uses FLEXnet Publisher version 11.14.1.2. Because of that, we no longer support Windows Server 2003 or Windows XP.
  • Server software 7.5.2 supports all 5.x, 6.x, and 7.x licenses. Client software 7.5.2 requires Server Manager 7.5.2 and will not work with older versions of server software.
  • The log file was moved from the Program Files hierarchy to ProgramData.

Significant maintenance fixes:

Release 7.5.1, October 2016

Significant maintenance fixes:

  • 12593: Upgrading from 7.0.1 to 7.5.0, when you launched the new version you got a message that Codejock.Controls.Unicode.v17.1.0.ocx is missing.

Release 7.5.0, July 2016

Significant maintenance fixes:

  • 12337: Server Manager allowed the same port to be specified for the vendor daemon and lmgrd.

Release 7.0.1, September 2014

Server Manager 7.0.1 has no significant functional changes from release 7.0.0.

Release 7.0.0, July 2015

Server Manager 7.0.0 replaces Server Manager 6.x. The new version can handle any 7.x licenses and clients, as well as 5.x/6.x licenses and clients.

Release 6.3.1, September 2014

Server Manager 6.3.1 has no significant functional changes from release 6.3.0.

Release 6.3.0, June 2014

Significant maintenance fixes:

  • 10934: In Server.lic, if "SERVER" is changed to "Server", certificate license is not recognized.
  • 11003: Under some circumstances, Server Manager displays "Path/File access error" instead of an instruction to run as administrator.
  • 11007: In Server.lic, blank lines or lines with only the comment token cause Server Manager to crash.

Release 6.2.1, March 2014

Server Manager 6.2.1 has no significant functional changes from release 6.2.0.

Release 6.2.0, September 2013

Server Manager now displays the Palisade vendor daemon port in addition to the lmgrd port. Both can now be set on Server Manager's Options screen.

Server Manager and this Guide are now available in all the same languages as the end-user software.

Server Manager and the client installers are now available in MSI versions as well as EXE.

Significant maintenance fixes:

  • 10549: With more than one license in a certificate, only the first is usable.
  • 10564: Putting host name on SERVER line makes license unusable.
  • 10637: A borrowed license could not be returned early if the server was identified on that client by a fully qualified domain name.

Release 6.1.2, April 2013

Server Manager 6.1.2 has no significant functional changes from previous releases.

Release 6.1.1, February 2013

Server Manager 6.1.1 has no significant functional changes from Server Manager 6.0.1.

Release 6.0.1, October 2012

This is the initial release of Server Manager. Although the underlying license scheme is similar to 5.x, the interface for server administrators and end users has been made much more convenient. The interactive Server Manager replaces LMTools and all command-line operations.

For Concurrent Networks, server administrators can easily allow or disallow borrowing and set a maximum borrowing term. If borrowing is allowed, end users can borrow a license through @RISK and the other applications, with no need for a separate borrowing utility.

For Enterprise Networks, end-user license activation is normally done silently by the client installer. But if that fails for any reason, end users can activate through @RISK and the other applications, with no need for a separate activation utility.

Last edited: 2018-03-14

4.6. 7.x Network Server License Agreement

Applies to: All 7.x products, Concurrent or Enterprise Network servers

Where can I find a copy of the license terms for Palisade network software?

If you have already installed the server software, click Start » Programs » Palisade Network Server » License Agreement. You'll also find the agreement, in Microsoft Word format, attached to this article.

See also: Overview of 6.x/7.x Network Licenses and End User License Agreement (EULA).

Last edited: 2015-11-20

4.7. Downloadable 7.x Guides

Applies to:
Palisade network software 7.x
Palisade network software 5.x, 6.x with Server Manager 7.x

Can I download the Network Guide to my computer for easier reference?

The Guide is presented as a series of articles to make online searching easier, and this format always has the most current information, but you can download it for offline reading. The

automatically packs the whole Guide in one HTML page, though without the attachments to articles.

There are also Language Versions, though they are not updated as often:

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: 2017-12-03

4.8. Downloadable 6.x Guides

Applies to:
Palisade network software 6.x
Palisade network software 5.x with Server Manager 6.x

Where is the documentation for my 6.x Palisade network? Can I download it?

We recommend our online Network Guide as the most current information. While of course the actual network software 6.x is no longer changing, we often update the Network Guide with answers to customer questions, which usually apply to all network software releases.

You can also download the language versions that were released with the network software:

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