Menu
PIXMA MX459PIXMA TS8120PIXMA TS5120PIXMA TS9020PIXMA MX492PIXMA TS8020PIXMA MX532PIXMA MG3620PIXMA MG7520PIXMA MG3222PIXMA MG6320PIXMA MG4220PIXMA MG6420PIXMA MX522MAXIFY MB2120PIXMA MG2520PIXMA TS9120PIXMA TS3120MAXIFY MB2720PIXMA MG2922PIXMA MG3520PIXMA MX452PIXMA TS9520PIXMA TS5020MAXIFY MB5120PIXMA TS6020PIXMA MG5522PIXMA MG2220PIXMA MP230PIXMA MX372PIXMA MG3220MAXIFY MB5320MAXIFY MB2320PIXMA MG3522PIXMA MX722PIXMA TS8220MAXIFY MB2020MAXIFY MB5020PIXMA MG5422PIXMA TR7520PIXMA MX479.
![]()
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? 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 and.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). 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 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.
Network utility free download - Network Utility, Network Profiles Utility, Network Profiles Utility, and many more programs.
This method affords zero downtime, but there are extra steps to obtain and activate a 30-day temporary license.Contact 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.On the new server, install Server Manager, activate the temporary license, and post the client installer and the INI file. See procedure.Redirect the existing clients (end user computers) to the new server for licensing.
![]()
See.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 PalisadeNetworkClient.ini file from the new server; see procedure. You can use the same installer on new clients as well.On the old server, run Server Manager, write down the Activation ID and number of concurrencies, and deactivate the license; see. Uninstall Server Manager or not, as you choose.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.Contact with your serial number and request the Server Manager and client installers. You don't need a new license.On the old server, run Server Manager, write down the Activation ID and number of concurrencies, and deactivate the license; see.
Uninstall Server Manager or not, as you choose.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 procedure.Redirect the existing clients (end user computers) to the new server for licensing. See.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 procedure. You can use the same installer on new clients as well.Certificate Licenses – Transfer Procedure. If you have only a few installed clients, it's probably easiest to change the information through the software:. Run @RISK (or other licensed Palisade software), with full administrative rights.
To do this, right-click the shortcut or desktop icon and click Run as administrator.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |