Welcome to Palisade network software! This Guide will show you how to install and activate the software on server and clients.
This Guide begins with full instructions for server setup and client setup. You’ll also want to scan the Frequently Asked Questions to see if any of them apply to your situation. The Guide concludes with reference information on Palisade Server Manager.
Please get in touch with Palisade Technical Support if you have any questions. Here’s how to reach us:
This is best for simple, brief queries rather than detailed troubleshooting. Please have your serial number ready.
This printed copy shows URLs for all external links, and most internal links are followed by the words “in this Guide”. If you view the original in your Web browser, either on our Web page below or on your server via » » » , all internal and external links become active.
On the Web, Guide for 6.x Network Administrators always has the latest version of this Guide.
Full administrative rights are required for the server setup.
The server software can run on Microsoft Windows XP or any later version of Windows. There is no need for a dedicated machine, because the license service just needs to sit and listen for license requests from clients.
Installing on a virtual server? See Are virtual servers supported?
Palisade software releases 6.x install FLEXnet Publisher 11.10 as the licensing system. This is compatible with Palisade 5.x licenses and will not interfere with FLEXnet licenses from other vendors. It must not be installed on a server with Palisade 1.x or 4.x licenses. Please see What if I already have FLEXnet-licensed applications from other vendors?, What if I already have a Palisade 5.x license on this server?, and What if I already have a Palisade 1.x or 4.x license on this server? for further information.
If this is the first time you’re installing a Palisade 6.x license on this server, even if you have Palisade 5.x licenses, download the server install .zip file, unpack the included .exe, and run it. (If you already have 6.x licenses installed, you can skip this step. See What if I already have a Palisade 6.x license on this server? for more information.)
If this is your first Palisade software on this server, the installer will suggest installing in C:\Program Files (x86)\Palisade or C:\Program Files\Palisade but will let you select a different location. If you already have any Palisade software installed, the installer will use the existing Palisade folder. NetServer and System folders will be created under the install folder unless they already exist.
The main components of the installed server software are:
Palisade.opt is also written by Server Manager and is used to manage borrowing in Concurrent Networks. You can add some FLEXnet options to Palisade.opt; see Can we use our standard FLEXnet options file?
Caution: Do not alter any of the files in the NetServer folder, except as instructed in this Guide or by Palisade Technical Support. Our software uses the .lic and .opt files in customized ways that don’t always match the standard FLEXnet usage.
Click » » » . Server Manager will update any 5.x license process; see What if I already have a Palisade 5.x license on this server?
The defaults are to select both communication ports dynamically, and to disallow borrowing. Your current options are shown in the Network Server Information box. Click if you want to change them. Otherwise, jump down to Server Step 3.
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.
By default, Server Manager allows both ports to be chosen dynamically. However, if you’re installing Server Manager on a server that already has Palisade 5.x licensing software, Server Manager will bring forward any port selections you have already made.
If you want to specify port numbers, it’s best to do that before you install multiple clients. If you change the lmgrd port number later, you will also need to change it on every Concurrent Network client that is already installed.
If you have not specified port numbers, you can determine which ports the server is actually using. Look at the Network Server Information box on the main screen of Server Manager to find the lmgrd port. To find the Palisade vendor daemon port number:
VENDOR palisade PORT=12345PORT= so that the VENDOR line becomes VENDOR palisadeThere’s no software setting on the client for the vendor daemon port. However, if you previously found that you needed to open that port in the firewall of any installed clients, you will need to update the client firewall settings.
Clients will ordinarily be on network and thus connected to the license server. In that case, license checkout is automatic and invisible, assuming that a license is available: the user launches the software and it runs. If no license is available, the user will see a message to that effect. You can let users check out a license to use it off network for a specified time, this is called borrowing. See Borrowing a 6.x Concurrent Network License for Use Off Network for end-user instructions.
You may or may not wish to allow borrowing. Here are some things to consider:
A borrowed license is deducted from the available pool on the server during the borrowing period. 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 to view the count of available licenses.
If you allow borrowing, you will also specify the maximum number of days allowed, up to 366. When actually borrowing a license, a user can specify any number of days up to the maximum that you specified.
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.
In this one-time process, you transfer the network license from Palisade’s server to your server. Your users will get their licenses from your server and will not need to communicate with Palisade’s server. We offer two options for your Concurrent Network license, activatable license and certificate license. (At this time, Enterprise Network licenses are offered in activatable form only.)
If Server Manager shows any activated or certificate licenses already installed, you should keep things simple by selecting the same type for your new license. If this is your first Concurrent Network license, please read the following to determine whether you should have an activatable or certificate license. Then follow one option or the other, not both.
Activatable LicenseThis type is suitable for most installations. You receive an Activation ID from us and you use our Server Manager program to activate it on your server. Many organizations can do this through Automatic Activation, where your server communicates directly with our license server to complete the activation. Other organizations use Manual Activation, where the Server Manager creates a Request File, you send that to us via email or our Web site, you receive a Response File, and the Server Manager uses the Response File to complete the activation. The activatable license is most flexible, because you can move it to a different server or split it among servers on your own. There’s also no need for periodic renewals in a commercial setting. (Academic course licenses are typically sold for one or two academic years and would have to be renewed in any case.) 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, click . Server Manager will prompt you for the Activation ID; enter the one that you received via email. 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. 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. This involves 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. 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. |
Certificate LicenseThis type is designed for two special circumstances:
Don’t ask for a certificate license unless you actually need one according to those criteria or you have some other specific reason. Why? Certificate licenses are less flexible than activatable licenses: they can’t be moved to a different server, and they must be renewed periodically. (There’s no charge for renewing a commercial certificate license, but still there’s the inconvenience of having to do it at least once a year.) To obtain or update a certificate license:
|
After completing Server Step 3 for the first time, or after changing server name or port number, click to create the Palisade_NetworkClient.ini file that is needed for client install. (For 5.x licenses, the file is named Client.ini.) Server Step 5 below tells you how to use this file.
You may or may not need to create a new .ini file after subsequent license installs with Server Step 3. Here are the rules:
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 .
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. Please see Can clients reach our server by FQDN or IP address?
To install the software on a client, you need two files:
They must be in the same folder during the client install. That folder can be anywhere you like—in a network share, on a USB stick, burned to a CD, etc. If you have multiple Concurrent Network products, you can set up the client installs in the same folder or in different folders, as you prefer. Each Enterprise Network client installer must be in its own folder.
Full administrative rights are required for the client install.
Browse to the network share or other location that you chose in Server Step 5 above. Then, either run the installer there, or copy the installer and the .ini file to the client computer and run the installer there. Either way, in Windows 7 or Vista you should right-click the installer and select ; in Windows XP you can just double-click the installer.
For system requirements on client computers, please see Which Platforms Are Supported by Palisade?
Concurrent Network Client SetupThere is no limit to the number of client installs. The client installer doesn’t need a connection to your server at install time. Instead, at install time it records the server information that was in the .ini file. Then at run time the application gets its license from the specified server or servers. (Server information is stored in the client’s System Registry, and it is not automatically updated if you change the .ini file later.) See Can a client get its license from multiple servers? to specify servers in the .ini file or change them afterward. 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 » » and select the shortcut for the software.
If the Palisade_NetworkClient.ini file contains incorrect server information, the client software will say that it cannot reach the server. To correct this information on the client, see How do I change port numbers or server name on existing Concurrent Network clients? |
Enterprise Network Client SetupFor Enterprise Networks, your license specifies the number of clients you may activate. The installer will try a client activation using your server and Activation ID as shown in the Palisade_NetworkClient.ini file. If the activation succeeds, then when the user runs the software it will start up without any licensing messages. The activation could fail during install if your server or Activation ID is incorrect, or if the licensed number of users have already been activated, or if your server is unreachable. The software will still be installed, but a message will tell you that the client could not be activated. To fix this, on the client click » » and then select the application. In the application, click » and then .
|
Yes, if it is a Concurrent Network. Perform Server Setup Procedure first, and then Client Setup Procedure. The programs for end users are all placed in a separate group called in the Start menu; end users will not need access to the group.
Enterprise Network client software cannot run in a Citrix, Terminal Services, or Remote Desktop environment.
Yes. Most administrators with virtual servers find that an activatable or certificate license works just fine. But a small minority have found that an activatable license does not work: it seems to activate successfully, but then it cannot be used, possibly after the service is stopped and restarted or after the virtual server is rebooted.
This problem does not occur on most virtual servers, and we have not been able to reproduce it or isolate the cause. The activatable type of license does write to the machine’s boot record, so possibly the disk emulation is less than perfect with some VM software.
If you have a virtual server and would like to test the activatable license type, please don’t activate your production license. Palisade Technical Support will be happy to create a test license for you on request. Or you could just use a certificate license and avoid the whole issue, even though the odds that it would affect your server are low. See Server Step 3: Activate License or Obtain Certificate to obtain a certificate license.
Certificate licenses are not available for Enterprise Networks, and therefore we suggest you consider a physical server with an 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.
The clients do not need an Internet connection.
While you are activating or deactivating a license, your server needs an Internet connection to Palisade’s server if you want to use Automatic Activation or Automatic Deactivation.
If your server has no Internet connection, or your firewall does not allow a direct connection to Palisade’s server, you can use Manual Activation instead. If you still want to use Automatic Activation or Automatic Deactivation, please see How should I set up my firewalls?
The server software does not need the Internet at any other time.
Most of our customers don’t need to make any changes in their firewall settings at all.
If Automatic Activation of your license fails owing to your firewall, we recommend that you use the Manual Activation procedure rather than make firewall changes to perform the one-time operation of activation. Please see Activatable License for Manual Activation instructions. If you prefer to change server firewall settings and perform Automatic Activation, here is the relevant information:
If your firewall prevents communication between your server and your end users, that is more of an issue. The simplest solution is to list lmgrd.exe and Palisade.exe as exceptions on the server’s firewall, and PalFlexServer6.exe as an exception on the client’s firewall if necessary.
If you prefer to open specific ports, on the server you need to open the outgoing ports that are listed in Port Numbers. If necessary, open those same port numbers as remote ports in the client’s firewall.
Yes, these are both compatible with the FLEXnet licensing software. After you create the Palisade_NetworkClient.ini file (Server Step 4), and before you install the client software, edit that file. On the SERVERNAME line, change the host name to the desired FQDN (fully qualified domain name) or IP address. Be careful to keep the @ sign.
If you wish, you can have one Palisade_NetworkClient.ini file for clients that are on your LAN and another for client computers that need to get a license from your server but are not on your LAN.
If a given client is usually on your LAN but occasionally goes off network and needs to run the software, borrowing may be a simpler approach. Please see Can a user borrow a Concurrent Network license for use off network?
For an Enterprise Network, the issue does not arise because the license is obtained in a one-time activation rather than dynamically when the application is run.
For a Concurrent Network, the answer is yes, but you must edit the .ini file before running the client install. (Server Step 4: Create Palisade_NetworkClient.ini File explains how to create that file.) On the SERVERNAME line, you can list multiple servers, separated by semicolons.
Example: SERVERNAME=27000@Alpher;@Bethe;27000@Gamow
A network
client installed with that information will look first to server
Alpher, using
port 27000 only; then to server Bethe, dynamically using any port 27000–27009;
and lastly to server Gamow, using port 27000 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 Concurrent Network clients that are already installed, follow this process:
As an alternative to step 4, you can edit the System Registry and add the new server information to the license path. Please see How do I change port numbers or server name on existing Concurrent Network clients? for details of the license path in the System Registry.
This Network Server release does not support a redundant server configuration for either type of network.
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 alter any of the lines written by Server Manager, or the license may not function correctly.
Because Palisade.opt is the default name, the Server.lic file doesn’t need an OPTIONS field. In fact, when Server Manager rewrites the file after you change options, it will remove an OPTIONS specification if it finds one.
MAX_BORROW_HOURS appears in the Palisade.opt file but does not have the same meaning that is given in the FLEXnet documentation. Please use Server Manager, not the options file, to set your borrowing policies.
INCLUDE, EXCLUDE, and similar option lines are not supported in this release. If you place them in the Palisade.opt file, the license may become unusable.
Palisade network licenses are built on FLEXnet Publisher, release 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.)
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.
If you’re just adding a license, there’s no need to run the server install. Follow this shorter procedure:
If you’re upgrading the server software itself, or reinstalling the server software for some reason, you can run the server install without first uninstalling the existing 6.x server software. Here’s how:
Whether you are replacing a 5.x network with an upgrade to 6.x, or keeping your 5.x network license and adding a 6.x network license, you’ll use the 6.x Palisade Server Manager to manage all 5.x and 6.x licenses. Follow the normal 6.x Server Setup Procedure.
The first time you launch Server Manager, if you have any 5.x licenses it will ask your permission to take over management of them. This is necessary before you can activate any 6.x licenses. With your permission, the 5.x service will be stopped. For a brief period, while you set a couple of options in Server Manager, clients already running can continue to run but no new clients can get licenses; typically this should be on the order of a minute or two. As soon as you select your options and click OK, the new background license process will be started and client licenses will again be available. The 5.x license service will be deleted, but all files will remain. You can delete them if you wish, either through » (look for a product name followed by “Network Edition”) or by deleting the containing folder. The default location is the C:\Program Files (x86)\FLEXnet\Palisade file or the C:\Program Files\FLEXnet\Palisade file. Please don’t create a new 5.x license process; that may render all your licenses unusable.
If your 6.x network license is an upgrade to replace a 5.x network license, your initial Activation ID for 6.x will be a temporary one. This allows for a transition period while you convert server and clients from 5.x to 6.x. At the end of the transition period, you will receive and activate your production Activation ID. For step-by-step procedures, please see Upgrading Palisade Software.
There were two types of 1.x/4.x Concurrent Network licenses, FLEXnet certificate licenses that were pre-activated, and “Palisade concurrent” licenses that required authorization and operated through a network share. If you’re not sure which type you have, please contact Palisade Technical Support.
Palisade 5.x or 6.x network licenses can’t coexist on the same server with 1.x or 4.x certificate licenses. Either remove the older license and uninstall the software, or choose a different server for your 6.x license.
The “Palisade concurrent” licenses did not use FLEXlm or FLEXnet and will not conflict with Palisade 5.x or 6.x network licenses.
This release does not support access controls.
In an Enterprise Network, the Activation ID in the Palisade_NetworkClient.ini file, used during client install, determines which product and edition will be usable on that client.
In a Concurrent Network, the end-user software gets its license dynamically from your server. An end user with Palisade client software can browse available licenses on the same server through » and . (The end-user software remembers which license was used in the previous session, so users should not need to do this, but the possibility is always there.)
If you want to differentiate between groups of Concurrent Network users, you can put different licenses on different servers. Then connect each user to the appropriate server via the Palisade_NetworkClient.ini file at client install time. You can later grant access to a different product or an additional product by updating that client’s server connection, as explained in How do I change port numbers or server name on existing Concurrent Network clients?
Here is the procedure:
(This section applies only to Concurrent Network clients. Enterprise Network clients don’t connect to your server after activation, so there’s no need to update them when you change port number or server name.)
Please see Port Numbers for changes on the server.
If you change or specify the Palisade port (vendor daemon port) on the server, you probably don’t need to do anything on the existing clients. However, if you had to open the old port as a remote port on the clients’ firewalls, you will need to update their firewall settings to open the new port.
If you change the communication port (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. In 32-bit Windows it’s HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE, and in 64-bit Windows it’s HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE. That information comes from the Palisade_NetworkClient.ini file at install time. You can change it later through License Manager in the end-user software, or directly in the System Registry.
If you have only a few installed clients, it’s probably easiest to change the information through the software:
As an alternative to steps 4 and 5, you can select the old server information in the list and click .
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 may prefer to
change the lmgrd port number by editing the System
Registry key mentioned above.
If the lmgrd port number is specified on the server, the data in the
client’s System Registry key should be in the form
portnumber@servername;PalisadeSystemFolder
If the lmgrd port is Dynamic on the server, the System Registry
data on the client should have the form
@servername;PalisadeSystemFolder
There could be multiple servers, separated by semicolons.
The Palisade System folder is the System folder under the main
folder where the Palisade client software is installed.
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 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"
or 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"
If the lmgrd port on the server is not specified (communication port is Dynamic in Server Manager), omit the port number but keep the @ sign in the .REG file.
You must deactivate every Enterprise Network client before you can move an Enterprise Network to a new server. There is no need to reinstall the client software.
Yes to both, and you will not need to reinstall the software. Please see Changing a 6.x Standalone Copy to a Concurrent Network Client or Changing a 6.x Standalone Copy to an Enterprise Network Client.
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 see Changing a 6.x Network Client to a Standalone License.
When a user checks out a license to use it off network for a specified time, this is called borrowing. A typical use is where a user is away from the office, overnight or for an extended period, and needs to run the software on a laptop.
Borrowing is disabled initially, but you can enable it if you wish; see Server Step 2: Set Options. For end-user instructions, please see Borrowing a 6.x Concurrent Network License for Use Off Network.
The license will automatically be returned to the pool at the end of the borrowing period, whether the client computer is on or off network. But a user who returns to the office earlier than expected can return the borrowed license by following instructions in the same article.
When the underlying Concurrent Network license is the certificate type, a borrowed license can be used only by the user who borrowed it. When the underlying license is the activatable type, a borrowed license can be used by any user on that computer. See Server Step 3 for the certificate and activatable license types.)
Simply activate the additional purchased users, or obtain a new license certificate that includes them. See Server Step 3: Activate License or Obtain Certificate.
If you have a current maintenance contract, there is no charge for the upgrade. Please contact your Palisade sales manager for your free upgrade or for a price quote if your maintenance has lapsed. When you receive your upgrade, please see What if I already have a Palisade 5.x license on this server? for instructions.
Most information is displayed when you click the button in Server Manager. For additional details, click in .
For details of interpreting the display, please see the descriptions of thse two buttons in the Reference section, below.
No specific action is necessary.
If a 6.x client crashes and the same client re-runs the software within ten minutes after the crash, that client will automatically reuse the same license that it was using when it crashed. As usual, when the client closes Excel its license returns to the available pool.
If a 6.x client crashes and the same client does not re-run the software, then after ten minutes the license is automatically recovered by the server software and returns to the pool of available licenses.
A 5.x client crash is handled in a different way. After 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. But the license is automatically returned to the pool of available licenses at the end of that time.
When you launch the Palisade Server Manager, it presents two categories of information on the main screen: information about the server, and information about the licenses on the server.
However, if the Server Manager detects a Palisade 5.x license process running, before it can present that screen it will need your permission to shut down that process and start up the 6.x license service. Please see What if I already have a Palisade 5.x license on this server?
This box shows current information known to Server Manager: your server name, the lmgrd port, and so on. The status of the license service is also shown.
(Server Manager does not show the Palisade vendor daemon port in this box. To see that port, please follow the procedure in Port Numbers.)
Click this button after you replace Server.lic with a new license file (certificate) from Palisade. That will cause the license service to read the new license file, and Server Manager will then update both sections of the display.
Please be patient. FLEXnet can take up to 60 seconds to reread licenses, and during that time the title bar of Server Manager may display “Not Responding”.
This button adds further information in the Network Server Information box.
If you have any Enterprise licenses on this server, a brief Enterprise License Status section appears. It shows each Enterprise Network Activation ID, with the number of activated users and the total number of users allowed on the license. To see which clients have activated Enterprise Network licenses, follow the directions in View.
The long Concurrent License Status section is a pass-through from the FLEXnet software’s lmstat program. It shows the license files, the status of the license service, and the status of the Palisade vendor daemon. Then it lists the Concurrent Network licenses, showing the number of concurrent users allowed (“licenses issued”) and the combined number currently using the license on network or with a borrowed license (“licenses in use”). There’s no indication whether a given license is the certificate type or activatable type, but you can see that information in the “Network Licenses Installed” box below.
After each license that has a nonzero licenses in use, there’s one line for each current on-network or off-network user. (For the history of license use by your end users, see View.) The three possibilities are:
If you stop and restart the license service, borrowed licenses may not be shown for an activatable type of Concurrent Network license. 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 “Network Licenses Installed” box below always shows the total number of concurrent users licensed.
To update this status information, click , not .
If the license service is currently running, the next button says . If the license service is not currently running, the button says .
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 to start the license 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. It is also useful to force the license process to recognize a new vendor daemon port number.
This button opens a dialog where you can set the lmgrd port and determine whether to allow borrowing. See Server Step 2: Set Options for the meanings of these options.
If you change server options, Server Manager will stop and restart the license service automatically. This should not have any effect on clients that are currently using the software.
This box lists activated and certificate licenses, both Concurrent and Enterprise type, with the details of each.
For some license types, the license information may extend past the right edge of the screen. In that case, just click once on the license of interest and hover your mouse over the text box to display the full description of the selected license. If you prefer, you can resize the Server Manager window.
You may see the same Activation ID listed more than once. Here’s an example. Suppose you have a Concurrent Network license with ten concurrent users allowed. Over time your organization grows and you buy an additional five concurrencies. These will be added to the same Activation ID, and after you activate them you will have two entries in the list for that Activation ID, one showing 10 users and one showing 5.
An expired or broken license is not shown here; see Unusable Licenses….
To activate a license, click Activate. You’ll find full details of the activation process in Activatable License under Server Step 3: Activate License or Obtain Certificate.
To deactivate a license, select the license from the list and then click . Select or . After the deactivation, Server Manager will update the display.
When would you want to deactivate a license?
If an Activation ID is listed more than once, that means you originally split its activations; see Network Licenses Installed on This Server above. 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.
Why might deactivation fail?
The client installers require a Palisade_NetworkClient.ini or Client.ini file during client install, so that the client software knows where to obtain a license. Click this button to create the needed .ini file for the license that is selected in the panel at left.
Please see Server Step 4: Create Palisade_NetworkClient.ini File for further details of when and how to use this button.
The Network Licenses box lists licenses that are currently activated on this server and are usable. If you also have any unusable licenses, will appear. Click it to display a list.
The most common reason for a license to be unusable is that it was a time-limited license and has expired. Other possibilities for an activatable license include changes in server hardware after the license was activated. For a certificate license, editing the certificate (except as directed in this Guide) or moving it to a different server will make it unusable.
If you have an unusable license and you can’t determine why it is unusable, Palisade Technical Support will be happy to help you.
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:
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.
The 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.
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 button displays the server name and Ethernet address(es) as they are known to the FLEXnet licensing software. In rare circumstances, Palisade Technical Support may ask you to send this information.
The button is for use by Palisade Technical Support during a remote support session.
Server Manager 6.1.2 has no significant functional changes from previous releases.
Server Manager 6.1.1 has no significant functional changes from Server Manager 6.0.1.
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.
Document updated 2013-09-09