Palisade Enterprise Activation Server ReadMe
Version 5.7.1
July 2011
Palisade Corporation
All Rights Reserved

Contents
About This Product
Release Notes
Quick Overview
Server Setup
Client Setup
License Activation
Technical Support Information

	
About This Product

The Enterprise Activation Server permits the licensed Palisade application to be activated and de-activated from a block of licenses on the customer's license server, rather than using Palisade's license server.

Release Notes

Macrovision FLEXnet v11.4
This Network release is based on version 11.4 of Macrovision's FLEXnet.

Trusted Storage
Rather than the certificate-based (.LIC file) scheme used in earlier Palisade Network versions, this 5.7.1 release uses Trusted Storage for saving and retrieving license information.

Fully-Qualified Paths
Whenever the path to a file or folder needs to be specified, Palisade strongly recommends using a fully-qualified path, rather than a mapped drive letter.  Mapped drives may change over time, and may resolve differently on different computers.

Redundant Server Configuration Not Supported
This release does not support a redundant server configuration.

Additional Tasks
For additional tasks not covered in this file -- such as moving your license server to a new computer -- please contact Palisade's Technical Support Department.

Quick Overview

•	run the Server Installer to place files and folders onto your server.
•	transfer licenses from the Palisade license server to your server.
•	establish the FLEXnet license manager on your server.
•	run Client Installer on the end-users' computers.
•	activate license on end-users' computers.

Server Setup

Plan ahead!  If you will be installing on a "test" server, please contact Palisade for a time-limited set of licenses.  This will permit you to become familiar with the procedures and try out the
software in your environment without having to return the test licenses to Palisade's server.  Just email support@palisade.com and explain your situation.  We are more than happy to provide
test licenses to help your deployment go more smoothly.

Note that this release is based on FLEXnet v11.4.  If you have an existing license server running pre-11.4 FLEXnet, Palisade strongly recommends that the existing server be left in place,
and this release be installed on a different server.

Before installing end-user software, your server needs to be set up to host licenses.  The steps are:
1. 	Run the Server Installer to unpack files and folders onto your server.
2. 	Transfer licenses from the Palisade license server to your server.
3. 	Verify license transfer.
4. 	Establish a FLEXnet License Manager process.
5. 	Make the Client Installer available.

Server Step 1: Run the Server Installer

1)	Log onto your server using an account with full Administrator privileges.  You should have several files on CD or in a source folder, including:

•	ServerSetup.exe
•	Server.ini
•	Server.lic
•	TransferLicenses.bat

2)	Double-click ServerSetup.exe.  It will read information from the Server.ini file and also make use of the other files.

3)	Choose the directory where FLEXnet License Manager files will be stored.  By default, a Palisade folder is created beneath your specified FLEXnet folder (e.g., C:\Program Files\FLEXnet\Palisade).  The Palisade folder will contain subfolders based on the serial numbers of each Palisade network product you have purchased.

Server Step 2:  Transfer Licenses from Palisade Server to Your Server

1)	Open a DOS shell, and change directory to the folder whose name matches the serial number of the license you are installing.  By default, the folder will be named something like C:\Program Files\FLEXnet\Palisade\5001234

For convenience, this directory will be referred to as the SN folder in the remainder of this document.

2)	Make sure your firewall is set to allow communication with http://service.palisade.com
This may mean that you need to temporarily grant an exception for this communication to occur.  After the licenses have been transferred to your server, the exception can be removed.

3)	To initiate the license transfer, run the .BAT file in the DOS shell:

TransferLicenses

4)	You will see a series of progress messages.  You may see several "Polling for response" "Waiting for response" pairs of messages while communication is attempted with the Palisade license server.  Please allow at least 60 seconds for the license transfer to complete.  The last line should be "TRANSFER REQUEST SUCCESSFULLY PROCESSED".

5)	If the last message indicates the license transfer succeeded, skip ahead to Server Step 3: Verify License Transfer

6)	If communication problems prevented a direct connection between the Palisade license server and your server, they will need to be resolved.  Do not proceed with Server Step 3 until you have been able to successfully transfer the licenses to your server.

7)	One alternate procedure is to generate and process XML files.  Open a browser and go to the page:
https://activations.palisade.com/useractivation/

8)	You generate the first XML file by running

Request_Palisade.BAT

from within a DOS shell.  This will create the file REQUEST_PALISADE.XML, which you will process using the interactive web page.  Please follow the instructions on the web page.  Typically it will involve saving a RESPONSE.XML file and running RESPONSE.BAT to process the answer from Palisade's license server.  You may need to run Request_Palisade.BAT a second time and process another REQUEST_PALISADE.XML file.

9)	Once the Palisade license has been transferred, you will also need to use the interactive web page with

Request_Enterprise.BAT

and create/process XML files, as well.

10)	If all of this seems a bit length and involved, you're right!  It is!  In most cases it is simplest to temporarily enable a direct Internet connection between your license server and Palisade's server, so that all of these transactions can take place via the TransferLicenses.BAT file.

11)	If you still have questions or problems, please send an email to support@palisade.com -- making sure to include your Activation ID and a description of the steps you have taken.  The licenses *must* be transferred to your server in order to deploy the software.  There is no way to bypass this step.

Server Step 3:  Verify License Transfer

1)	Within the DOS shell whose current directory is the SN folder, type:

palserveractutil -view

2)	Look for the line that begins "Activatable:", for it will contain the number of licenses now on your server available for activation on end user computers.  Also verify the product and version.

3)	You should also see an entry for one Concurrent license of Palisade_Network50.  This one license is for your Enterprise Activation Server, and it will remain on your server.

4)	Do not proceed to the next step until you have verified both the Palisade Network license and your product licenses have been transferred from the Palisade server to your server.

***  NOTE  ***  Once the licenses have been transferred from Palisade's license server to your server, the licenses become your responsibility to manage.  Do not erase the hard drive, re-image the computer, or take any action that would erase the licenses from Trusted Storage.  If you should need to move the licenses to a different server, please contact Palisade Tech Support for instructions.

Server Step 4:  Establish a FLEXnet License Manager Process

1)	Launch LMTOOLS.EXE within the SN folder by double-clicking it.  Make the System Settings tab active, and note the name of your server in the Computer/Hostname field.

2)	Edit the file SERVER.LIC in the SN folder, and change "this_host" to the name of your server that is displayed in the Computer/Hostname field.  Save the modified SERVER.LIC file.

3)	Within LMTOOLS, make the Config Services tab active.  Enter a new Service Name, then use the Browse buttons to populate the 3 empty fields:

-	Identify the LMGRD.EXE file located within the SN folder
-	Identify the SERVER.LIC you modified with your server name in the SN folder
-	You can specify any name and location for the log file.  For consistency you may wish to locate it within the SN folder

4)	Check the box to Use Services.  Check the box to Start Server at Power Up.  Then press Save Service.

5)	Make the Start/Stop/Reread tab active;  select the service you just added;  and press Start Server.

6)	To verify that the FLEXnet License Manger (LMGRD) process has been set up correctly and is now running:

-	Make the Server Status tab active
-	Press Perform Status Inquiry

7)	Scroll through the output text.  Note that if Perform Status Inquiry is used multiple times, the old text remains in the dialog and the new text is added at the bottom.  You should see that the FLEXnet License Manager is running, and that a license of Palisade_Network50 is available.  The activatable licenses will not show up in this dialog.  At this point you may close LMTOOLS if you wish.

Server Step 5:  Make Client Installer Available

Within the SN folder is a "ClientInstaller" folder, which contains a product installer and a file named CLIENT.INI

Now that your server has been set up, the client software may be installed on the end user computers.  You may copy or distribute the contents of the ClientInstaller folder to your end users in whatever manner is most appropriate for your environment.  In other words, the ClientInstaller folder can be copied to a different computer, to a shared folder, etc.  The only restriction is that it is important to have the CLIENT.INI file in the same folder as the product installer, because when the product installer launches it will search for the CLIENT.INI file and use the values for server name, Activation ID, etc.

Client Setup

1)	While logged on to an end user computer with full Administrator privileges, double-click the product installer.  The product installer will read the values in the CLIENT.INI file and proceed with the installation.  Once installation has been completed with an Administrator account, users with normal privileges may log on and run the software in Trial mode.

2)	After you have verified the software has been installed and runs properly in Trial mode, proceed with License Activation.

License Activation

Now that the software has been installed on the end user's computer, the license needs to be activated.  The activation process will use one license from the block of licenses on your server.  The NLICENSE utility is used for activating and de-activating licenses on end user computers.

NLICENSE Utility
Palisade provides a standalone utility for activating and de-activating licenses.  You may decide whether or not to distribute this utility;  it is not installed on end users' computers by default.  The NLICENSE utility is copied into the SN folder as part of the server installation process.  To place NLICENSE on a client computer, simply copy it into the Palisade System folder:  C:\Program Files\Palisade\System

The procedure to activate a license is:

1)	Launch NLICENSE by double-clicking on it
2)	Select your local server in the "Network License Server(s)" box
3)	Select the license you wish to activate in the "Borrow License" box
4)	Set the end date for the borrowing period.  On the date specified the license will automatically be returned to the Enterprise server and will be unavailable on the local computer.
5)	Press "Borrow License"

The procedure to de-activate a license is:

1)	Launch NLICENSE by double-clicking on it
2)	Select the license you wish to return in the "Client Licenses in Use" box
3)	Press "Return License"

Important Concepts
•	A license must be de-activated (returned to the server) before a computer is taken out of service or has its hard drive erased.  Failure to de-activate a license will permanently remove it from the block of available licenses until the end of the borrowing period is reached.
•	The client computer must be connected via the network to the local license server for license activation and de-activation.

Technical Support Information

Palisade is dedicated to providing quality technical support for our customers. If requesting technical support via our website, fax, email, or post, please be sure to supply the following information:
1. 	Your name, serial number, and a return email address, phone number, or fax number.
2. 	The Palisade product and version number you are using (e.g. @RISK 5.0.0, Network).
3. 	The version of the Windows operating system you are using (e.g. Windows XP).
4. 	If relevant, the version of Office software you are using (e.g. Office 2003).
5. 	A description of the problem.  Please be as specific as possible.

World Wide Web:
Palisade’s web site is www.palisade.com.  The site contains a technical support knowledgebase (a searchable database of technical support questions and answers).  The site also contains all the latest product information, news, and software demos.

Email:
Palisade technical support can be reached at support@palisade.com  For general sales questions contact: sales@palisade.com, sales@palisade-europe.com, or sales@palisade.com.au.

Fax:
Palisade’s fax number is (607)-277-8001 in the USA, +44 1895 425051 in Europe, and +61 2 9954 3882 in Australia.

Phone:
Palisade technical support can be reached via phone at (607)-277-8000, Monday through Friday 8:30am-5:00pm EST in the USA.  In Europe, technical support is available at +44 1895 425050, Monday through Friday from 9:00am-5:00pm GMT.   Asia-Pacific customers may call our Australia office at +61 2 9929 9799 from 0900h to 1700h AEST.
Please note: telephone technical support is not available for student versions of Palisade products.

Post:
Palisade technical support can be reached via mail at

	Palisade Corporation
	Department of Technical Support
	798 Cascadilla Street
	Ithaca, NY 14850
	USA

	Or

	Palisade Europe UK Ltd.
	31 The Green
	West Drayton
	Middlesex
	UB7 7PN
	United Kingdom
	
	Or

	Palisade Asia-Pacific Pty Limited
	Department of Technical Support
	Suite 101, Level 1
	8 Cliff Street
	Milson Point NSW 2061
	Australia