Home → Network Guide → Server Setup → Step 4: Prepare the Client Install
Disponible en español: Paso 4: Preparar la instalación del Cliente
Applies to:
Palisade Server Manager 5.x/6.x/7.x/8.x
After completing Server Step 3 for the first time, or after changing server name or port number, click Create Client.ini to create the Palisade_NetworkClient.ini file that is needed for client install. (For 5.x licenses, the file is named Client.ini.) Server Step 5 tells you how to use this file.
You may or may not need to create a new .ini file after subsequent license installs with Server Step 3.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:
After you install your first Concurrent Network license or any new Enterprise Network license on this server, Server Manager will remind you to create the .ini file for the new license. But you can create the .ini file at any time: click the appropriate license in the list, and then click Create Client.ini.
In some unusual setups, clients will need a fully qualified domain name, or an IP address, to find the server. If your network is set up in this way, simply edit the Palisade_NetworkClient.ini file after creating it and before doing the client installs. See Can clients reach our server by FQDN or IP address?
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: 2020-07-06