Network Licensing Installation Guide

This document describes how to install the PipelineStudio network license server software
on your network server PC. This document should be read fully before undertaking the
installing, upgrade or migration of the Safenet network license manager.
These instructions apply to network licenses only. If you have a standalone hardware key
(bitlock), refer instead to the document under
Start | Programs | Energy Solutions | PipelineStudio | Standalone Licensing Help.

Contents
Contents ............................................................................................................................... 1
Requirements ....................................................................................................................... 1
Updating or Migration of Existing Installations of the Network License Server Software ........ 1
Installing the Network License Server Software .................................................................... 2
Installing Your License Codes ............................................................................................... 3
Storing a Backup of Your License Codes .......................................................................... 6
Performance Tuning ............................................................................................................. 6
Setting addresses in the hosts file ..................................................................................... 6
Setting the LSFORCEHOST environment variable ............................................................ 7
Uninstalling the License Manager Server .............................................................................. 7
Remote Commuter Licensing ................................................................................................ 7
Step 1: Getting a Remote Commuter Locking Code .......................................................... 8
Step 2: Checking Out a Remote Commuter Authorization ................................................. 8
Step 3: Installing a Remote Commuter Authorization ........................................................ 9
Troubleshooting .................................................................................................................... 9
Notation ................................................................................................................................ 9

Requirements
PipelineStudio supports installing the Sentinel RMS license manager server on a PC running
Windows Server 2008 or Windows Server 2012.

Updating or Migration of Existing Installations of the

Network License Server Software
This release of PipelineStudio contains an updated version of the network license server
software.

1
If you do NOT already have the Sentinel LM (or Sentinel RMS) license manager server
software installed on your PC server, use the instructions in the section titled Installing the
Network License Server Software.
If you already have the Sentinel LM (or Sentinel RMS) license manager server software
installed on your PC server, you should update the installation using the following process.
Login to the license server PC using an account with Administrator privileges
1. Make sure that no licenses are checked out.
If licenses are checked out the NLM will detect this as license tampering and the
client machine will be locked from accepting licenses in future.
2. Stop the Sentinel RMS License Manager service from the services control panel
3. Install the new release of the license manager server (follow the instructions in the
following section titled Installing the Network License Server Software)
4. After installing the new release of the license manager server refer to the sections
titled Installing Your License Codes and Performance Tuning
5. After the new release of the Sentinel RMS License Manager has been found to work
correctly the older version of the Sentinel RMS License Manager should be removed
using the Add or Remove Programs functionality in the Windows operating system

Installing the Network License Server Software

To install the network license server software on a server PC, use the following instructions.
The software you need can be found on the PipelineStudio CD or the installation files that
you downloaded from our website under the folder networklicensing.
Note: We do not recommend installing the license server software on a PC which you also
want to be a PipelineStudio client.
1. Install the Sentinel bitlock driver by running the installer at the following location,
where x.x.x represents the version number of the drivers, which may vary between
releases of PipelineStudio as the drivers are updated:
<your CD drive>\networklicensing\Driver\Sentinel System Driver
Installer x.x.x.exe
2. Read and accept the license agreement and choose the Complete install option
3. You may now connect the network license bitlock that you received to the server PC
4. Run the setup program found on the PipelineStudio CD or download:
<your CD drive>\networklicensing\Server\Setup\setup.exe
5. Following the prompts, we recommend that you select the application can be used by
Anyone using the machine (All Users) and select a Complete install. Select to
unblock the firewall. If you have the windows firewall running and you choose not to
unblock the firewall, clients will not be able to connect until the settings are performed
manually.
6. You may be asked to restart your computer, if asked reboot the server PC
7. Copy the contents of the following folders to the server for future reference.
Admin.net contains utilities for use with your license server. See the documentation
in the Manuals folder to learn more about these tools:

2
 <your CD drive>\networklicensing\Admin.net
<your CD drive>\networklicensing\Manuals
8. If you are installing the software on a new or secondary license server, then in order
for existing installations of PipelineStudio to find the new license server, users should
choose the menu item Clear License Server List on Exit (available on the
PipelineStudio Tools menu when no PipelineStudio documents are open) and then
re-start PipelineStudio.
If you have never run PipelineStudio, this step is not necessary.

Installing Your License Codes

1. Launch the following utility:
networklicensing\Admin.net\Win32\WlmAdmin.exe
2. Find your server name in the tree view on the left of the WlmAdmin window and
Right Click on it
3. Choose the menu option Add Feature | From A File | To Server and its File (See
screen shot below);

3
4. Use the Open file dialog to select the licence file lservrc which you should have
received either via email or on a disk:

5. Select to [Open] the file. You may then have to [OK] a message box similar to the
one below:

6. You may now close the WlmAdmin utility. You can use the WlmAdmin utility at any
time (also from other machines) to view the status of the available licenses.
7. If you have added license codes for a new product to the file, then in order for
existing installations of PipelineStudio to find the new license codes, users should
choose the menu item Clear License Server List on Exit (available on the
PipelineStudio Tools menu when no PipelineStudio documents are open) and then
re-start PipelineStudio.
If you have never run PipelineStudio, this step is not necessary.

4
8. If you start PipelineStudio from a client computer and get the message No Licenses
found:

9. Click the [Cancel] button and try the following:

In the client computer:
a. Search for the file hosts under:
C:\WINDOWS\system32\drivers\etc
b. Open the hosts file using "Notepad" (or another text editor), and add the IP
address and the name of the Network License Server. After editing save and
close the hosts file.
Note: There is no need to reboot the PC after changing the hosts file
c. Restart PipelineStudio, if it does not work continue with the next steps
d. The license server setting can be set manually via the Windows Registry.
Click on the [Start] button, select "Run", then type "regedit" and press the
[OK] button
e. Navigate to the following location: My
Computer\HKEY_CURRENT_USER\Software\Energy Solutions
International\Pipeline Studio\4.x\Licensing\License Servers
f. Right click on the right pane of the registry, from the New menu select
String Value and type: Gas if you have PipelineStudio Gas, Liquid if you
have PipelineStudio Liquid, or GASandLIQUID if you have a dual
PipelineStudio Gas and Liquid licenses

5
 g. Right click on the item you have just added (Gas, Liquid, or GASandLIQUID)
and from the menu select Modify. In the Edit String dialog for Value data:
type the server name or the server IP address, (see the screen captured
below) close the dialog and close the registry

h. Start PipelineStudio, if the problem persists please contact your own

companys IT team to make sure that the IP address that you have entered
above is correct.
i. Start PipelineStudio, if the problem persists please ensure you have also
followed the instructions in the section titled Performance Tuning.
j. Start PipelineStudio, if the problem still persists please contact the
PipelineStudio technical support team at ESI.Support@emerson.com for
further assistance.

Storing a Backup of Your License Codes

To make retrieving/finding your license codes quick and easy in the future create a new
directory called Network License and copy the file lservrc to this location.
C:\Program Files\Common Files\SafeNet Sentinel\Network License
It is also a good idea to keep a backup of your license codes elsewhere.

Performance Tuning
Setting addresses in the hosts file

It is best to include the IP address and name of the server in the hosts file on all client PCs.
Ideally, the server hosts file should also include the IP address and name of all client
machines in its hosts file, although this requires using static IP addresses for client PCs.
The hosts file can be found in the following folder:
<windows directory>\system32\drivers\etc
There is no need to reboot PCs after changing the hosts file.

6
Setting the LSFORCEHOST environment variable

It may be necessary to set the LSFORCEHOST environment variable on client PCs. This is
especially important if the client PC is located on a different sub-network than the sub-
network where the Network License Manager is installed.
The LSFORCEHOST environment variable can be set on client PCs as follows:
Windows 7:
1. Click Start, right-click on My Computer and select Properties
2. Select Advanced system settings
3. Select the Advanced tab
4. Click Environment Variables
5. Create a new User environment variable or a new System environment variable by
clicking the New button. Enter LSFORCEHOST in the Variable name field and
include the hostname of the network server containing the network license manager
in the Variable value field. Click OK on the New User Variable window
6. Click OK on the Environment Variables window
7. Click OK on the System Properties window

Uninstalling the License Manager Server

The License Manager Server may be uninstalled via the Add/Remove Programs feature in
Control Panel (it is recommended that you stop the service before uninstalling). Of course,
after uninstalling the server, licenses will no longer be available to client PCs.

Remote Commuter Licensing

Previous versions of PipelineStudio required that the computer that will use a commuter
authorization be physically connected to the network at some point to check out the
commuter authorization. In some cases this is not practical (for example if a traveler is
delayed on a trip and needs a new license).
There is a utility WCommute which allows a network client to check out a commuter
authorization and send it to a remote user.
A utility WRCommute is also provided to allow the remote user to generate a commuter
locking code to send to the local user checking out the commuter authorization from the
SentinelLM license server, and also to install the commuter authorization received from the
network user.
Here is an overview of how to obtain and install a remote commuter authorization:
1. A remote user runs WRCommute to generate a commuter locking code for the
remote computer, and sends the commuter locking code to the local user who has
access to the SentinelLM license server.
2. The local user runs WCommute (entering the remote users commuter locking code)
to check out a remote commuter authorization from the SentinelLM license server,
and sends it to the remote user.
3. The remote user runs WRCommute to install the remote commuter authorization.
7
Step 1: Getting a Remote Commuter Locking Code

The remote user must generate a commuter locking code for his or her remote computer
and send it to the network user.
Note: The commuter locking code used to lock a commuter authorization is not the same
as the locking code displayed by echoid or wechoid - you must use WRCommute to obtain
it.

Getting a Commuter Locking Code with WRCommute

WRCommute is located in the below folder:

<your PLS installation directory>\PLStudio\Licensing
Run WRCommute and click the Get Locking Code tab. You see the commuter locking
code for the current computer.
To copy the commuter locking code to the Windows Clipboard, click the Copy to
Clipboard button.
To save the commuter locking code to a file, click the Save to file button.
To display the commuter locking code in a separate window, click the Display
button.
To send the commuter locking code as an e-mail message, type an e-mail address in
the E-mail address text box and click Send.

Step 2: Checking Out a Remote Commuter Authorization

The next step is to use WCommute on a computer connected to the network containing the
SentinelLM license server to check out a commuter authorization for the remote user.

Checking out a Remote Authorization with WCommute

WCommute is located in the below folder:

networklicensing\Admin.net\Win32\
1. Run WCommute and select the commuter authorization you want to use from the
network as you normally would.
2. Select the Check out authorization for remote machine check box and click Check
Out.
3. Now WCommute displays the Locking Code for Remote Machine dialog box.
4. Entering the remote computers Commuter Locking Code:
To type the commuter locking code received from the remote user, select Enter
the locking code for remote machine and type it in the text box.
To paste the commuter locking code from the Windows Clipboard, click the Paste
from Clipboard button.
To choose the commuter locking code from a file, select Get locking code for
remote machine from file and type the file name in the text box or use the
Browse button to find it.

8
 5. Click OK. Next you see the Remote Commuter Licensing dialog box.
Saving the Remote Commuter Authorization:
To save the commuter authorization to a file, click the Save to File button.
To send the commuter authorization as an e-mail message, type an e-mail
address in the E-mail address text box and click Send.

Step 3: Installing a Remote Commuter Authorization

Once the commuter authorization has been checked out and sent to the remote user, the
remote user needs to install it.
Note: A remote commuter authorization cannot be checked back into the license server, but
will simply expire on the remote computer.

Installing a Remote Commuter Authorization with WRCommute

WRCommute is located in the below folder:

<your PLS installation directory>\PLStudio\Licensing
1. Run WRCommute and click the Install Remote Authorization Code tab.
Installing a Commuter Authorization:
To type the authorization code received from a network user, select Enter
remote authorization code and type it in the text box.
To install the authorization code from a file, select Get remote authorization
code(s) from file and type the file name in the text box or use the Browse
button to find it.
To paste the authorization code from the Windows Clipboard into the text box,
click the Paste from Clipboard button.
2. Click Install.

Troubleshooting
Should you encounter any problems please contact the PipelineStudio technical support
team at ESI.Support@emerson.com.

Notation
PipelineStudio, TNet and Energy Solutions are registered trademarks of Energy Solutions International.
Windows, Excel and SQL Server are registered trademarks of Microsoft Corporation.
Intel is a registered trademark of Intel Corporation.
SentinelRMS* 1989-2008 SafeNet, Inc. All rights reserved
SafeNet, Sentinel, SentinelLM, and Sentinel RMS are either trademarks or registered trademarks of SafeNet, Inc.
All other product names referenced herein are trademarks or registered trademarks of their respective
manufacturers.