HP ZCentral Software Licensing Guide
SUMMARY
This document describes licensing of HP ZCentral Remote Boost Software and HP ZCentral Connect Software. Remote
Boost licensing applies to Remote Boost Sender only; Remote Boost Receiver can be used freely.
Legal information
© Copyright 2013–2015, 2017–2020 HP
Development Company, L.P.
Linux® is the registered trademark of Linus
Torvalds in the U.S. and other countries.
Windows is either a registered trademark or
trademark of Microsoft Corporation in the
United States and/or other countries.
Condential computer software. Valid license
from HP required for possession, use or
copying. Consistent with FAR 12.211 and
12.212, Commercial Computer Software,
Computer Software Documentation, and
Technical Data for Commercial Items are
licensed to the U.S. Government under vendor's
standard commercial license.
The information contained herein is subject to
change without notice. The only warranties for
HP products and services are set forth in the
express warranty statements accompanying
such products and services. Nothing herein
should be construed as constituting an
additional warranty. HP shall not be liable
for technical or editorial errors or omissions
contained herein.
Seventh Edition: September 2020
First Edition: February 2013
Third-party software notice
Third-party source code and licenses are
redistributed, if required, with HP ZCentral
Software.
Document Part Number: M26122-xx1
User input syntax key
Text that you must enter into a user interface is indicated by fixed-width font.
Table User input syntax key
Item Description
Text without brackets or braces
<Text inside angle brackets>
[Text inside square brackets]
{Text inside braces}
|
...
Items you must type exactly as shown
A placeholder for a value you must provide; omit the brackets
Optional items; omit the brackets
A set of items from which you must choose only one; omit the braces
A separator for items from which you must choose only one; omit the vertical bar
Items that can or must repeat; omit the ellipsis
iii
Table of contents
1 Remote Boost licensing overview..........................................................................................................................................1
Remote Boost License types .............................................................................................................................................1
Remote Boost oating licenses.........................................................................................................................................1
Remote Boost version number..........................................................................................................................................2
Remote Boost license version date ................................................................................................................................... 3
Remote Boost license policy..............................................................................................................................................3
2 Installing a local license key le ............................................................................................................................................4
Conguring Remote Boost Sender to access a local license key le on Windows............................................................4
Conguration during Remote Boost Sender installation..........................................................................................4
Conguration after Remote Boost Sender Installation.............................................................................................4
Conguring Remote Boost Sender to access a local license key le on Linux..................................................................5
3 Installing and conguring the FLEXnet license server.......................................................................................................... 6
Before you install the license server ................................................................................................................................. 6
License server port conguration .....................................................................................................................................7
Installing the license server on Windows.......................................................................................................................... 7
Starting and stopping the license server on Windows......................................................................................................7
Using LMTOOLS..................................................................................................................................................................8
Installing the license server on Linux................................................................................................................................ 8
Accessing the Remote Boost oating license .................................................................................................................10
Conguring Remote Boost Sender to access a oating license..............................................................................10
Down, missing, or moved oating license servers..........................................................................................................10
Hosting multiple license key les....................................................................................................................................11
4 Connect licensing overview .................................................................................................................................................12
Connect license types......................................................................................................................................................12
Connect version number..................................................................................................................................................12
Connect license version date...........................................................................................................................................13
Connect license policy .....................................................................................................................................................13
Providing a hostname and quantity................................................................................................................................14
Installing a ZCentral Connect license le.................................................................................................................14
Appendix A Troubleshooting licensing ...................................................................................................................................15
Troubleshooting Remote Boost Sender licensing...........................................................................................................15
Troubleshooting the FLEXnet license server ..................................................................................................................15
Troubleshooting Connect licensing.................................................................................................................................15
iv
Contacting HP for licensing support................................................................................................................................16
Appendix B Cleaning registry references to the Flexnet license server ................................................................................17
Appendix C Uninstalling the FLEXnet License Server on Windows........................................................................................18
Appendix D Uninstalling the FLEXnet License Server on Linux..............................................................................................19
Index ........................................................................................................................................................................................20
v
vi
Remote Boost licensing overview1
This section describes licensing of HP ZCentral Remote Boost Software. Remote Boost licensing applies to
Remote Boost Sender only; Remote Boost Receiver can be used freely.
NOTE: Remote Boost does not require a license on HP Z series desktop workstations or HP ZBook mobile
workstations.
For detailed Remote Boost information, see the latest version of the HP ZCentral Remote Boost Software
User Guide that is bundled with HP ZCentral Remote Boost, available at http://www.hp.com/go/zcentral. This
website might also contain a more recent version of this licensing guide.
Remote Boost Sender licensing is based on a license key that is obtained from HP after you purchase Remote
Boost. The license key is saved in a license key le, which is checked each time a Remote Boost connection is
established.
You can download, install, and run Remote Boost Sender to verify connection without a license key le. If the
license key le is missing or invalid, you will still be able to view and interact with the remote desktop, but a
notication will be displayed in your viewing window indicating that the Remote Boost Sender is unlicensed.
Remote Boost License types
The following Remote Boost license types are available.
● Local license—A local license key le must be stored on each computer running Remote Boost Sender.
The following local license types are available:
– Standard license—This license type fully activates a single instance of Remote Boost Sender on any
supported computer.
– Trial license—HP also oers a free, 60-day trial license for Remote Boost Sender.
● Floating license—Floating licenses are stored on a license server. This license type is ideal for
deployments with many potential Remote Boost users but limited simultaneous use. Licenses are
checked out on a concurrent-use basis up to the number purchased. For details, see Remote Boost
oating licenses on page 1.
For information about downloading Remote Boost and purchasing a license, go to http://www.hp.com/go/
zcentral.
NOTE: Except for the 60-day trial license, Remote Boost licenses never expire. However, a new license
purchase is required to upgrade to a newer major version of Remote Boost. For more information, see
Remote Boost license policy on page 3.
Remote Boost
When you purchase oating licenses, you receive a pool of Remote Boost Licenses. These licenses are
dynamically allocated on a rst-come, rst-served basis whenever Remote Boost Receiver attempts to
connect to Remote Boost Sender. A oating license is checked out when you establish a connection to Remote
Boost Sender and is checked in when the connection terminates.
oating licenses
Remote Boost licensing overview
1
If multiple receivers are connecting to a single sender (for example, when conducting a collaboration session),
only one license is used by Remote Boost Sender. This happens when the rst Remote Boost connection is
established.
Floating licenses allow a company to purchase, for example, 75 licenses but support a user community of
perhaps hundreds of users, as long as no more than 75 users ever attempt to establish connections with
separate Remote Boost Senders simultaneously.
Floating licenses require a license server, which can be installed on one of the computers running Remote
Boost Sender, or the license server can be installed on a separate computer. Remote Boost includes an
installer for the FLEXnet license server. For installation information, see Installing and conguring the
FLEXnet license server on page 6.
Remote Boost version number
The Remote Boost version number contains the three components shown in this section.
NOTE: The version numbering changed between HP Remote Graphics Software (RGS) and HP ZCentral
Remote Boost. The last version of RGS is 7.7.x and the rst version of Remote Boost is 2020.0.
Figure 1-1 Remote Boost version number components
Table 1-1 Remote Boost version number components
Item Description
1. Primary release number—A primary release contains suicient changes such that interoperability with the prior primary
2. Minor release number—When the number is not zero, it represents a minor release, which typically introduces new
3. Patch release number—When the number is not zero, it represents a patch release, which is typically only for xing major
release is not guaranteed by HP. For example, a connection between dierent primary releases of HP ZCentral Remote
Boost Sender and HP ZCentral Remote Boost Receiver might not function at an acceptable quality, or at all.
features or enhances existing functionality, as well as including changes from any previous patch releases. A connection
between dierent minor releases (but the same primary release) of HP ZCentral Remote Boost Sender and HP ZCentral
Remote Boost Receiver should function at an acceptable level of quality.
security issues or defects. A connection between dierent patch releases (but the same primary release) of HP ZCentral
Remote Boost Sender and HP ZCentral Remote Boost Receiver should function at an acceptable quality.
NOTE: Each release of Remote Boost is a complete release of the entire product, regardless of which
components have changed.
2
Chapter 1 Remote Boost licensing overview
Remote Boost license version date
Each release of Remote Boost has a license version date that the Remote Boost licensing uses. For example,
the Remote Boost 7 license version date is 1 November 2019, which is formatted 2019.1101 (YYYY.MMDD).
Viewing the license version date might assist in troubleshooting any licensing issues. Follow the steps
outlined here to view the license version date.
1. Right-click the Remote Boost Sender icon in the Windows notication area, and click About.
2. Locate the line License Version Date like in the following example:
License Version Date: 2019.1101
NOTE: The license version date should not be confused with the build date. The build date is not used
by the Remote Boost licensing mechanism.
Remote Boost license policy
You are only required to purchase a new license for Remote Boost when the version date changes, and the
version date only changes for primary releases, such as RGS 7.0 and Remote Boost 2020.0. Therefore, when
you purchase a license for Remote Boost, you are entitled to free upgrades to all future minor and patch
releases.
For example, if you purchased an RGS 7 license, you are entitled to free upgrades to versions 7.x.x. However,
you would have to purchase a new license to upgrade to Remote Boost 2020.0.
NOTE: Remote Boost licenses also work with older versions of RGS. For example, a Remote Boost 2020.0
license can be used with RGS 7.
The following table demonstrates example RGS and Remote Boost version numbers and license version dates.
IMPORTANT: The values in this table might not match actual releases of Remote Boost or RGS.
Table 1-2
Version number Release type License version date
2020.1 Minor release 2019.1101
2020.0.1 Patch release 2019.1101
2020.0 Primary release 2019.1101
7.1 Minor release 2014.0401
7.0.1 Patch release 2014.0401
7.0 Primary release 2014.0401
Remote Boost and RGS version number and license version date examples
Remote Boost license version date 3
Installing a local license key le2
This chapter describes how to install a local license key le.
Conguring Remote Boost Sender to access a local license key le
on Windows
Remote Boost Sender can be
installation.
congured to access a local license key le either during installation or after
Conguration during Remote Boost Sender installation
During Remote Boost Sender installation (as described in the HP ZCentral Remote Boost User Guide), you will
be presented with a dialog box that asks you to install the Remote Boost Sender license. For local licenses,
select Install a license le on this system, and click Next.
Browse to the location where you saved your license key le, select it, and select Open.
NOTE: License key les must end with the .lic suix.
The license key le will be copied from the location you specied to the Remote Boost Sender installation
directory:
Default location:
C:\Program Files\HP\Remote Graphics Sender
Conguration
If, during Remote Boost installation, you select I do not yet have a license le, you can specify the location of
the license key le post-installation in one of two ways.
after Remote Boost Sender Installation
The rst way to specify the location of the license key le post-installation is to copy the license le into the
Remote Boost Sender installation directory:
Default location:
C:\Program Files\HP\Remote Graphics Sender
The second way to specify the location of the license key le post-installation is by using the
LM_LICENSE_FILE environment variable. To set this environment variable:
1. In Windows Search, type env, and choose Edit the system environment variables.
2. Select Environment Variables.
3. Under System variables, click New. This opens the New System Variable dialog box.
4. Type LM_LICENSE_FILE as the variable name.
4
Chapter 2 Installing a local license key le
5. Enter the path to the local license key le as the variable value. You can enter multiple paths. Separate
them by semicolons, such as:
C:\licenses;C:\backuplicenses
Remote Boost Sender will sequentially examine each folder from left to right until it nds a folder
containing a valid local license key le.
NOTE: If a license key le is specied and found during Remote Boost Sender installation, it will be
copied into the folder C:\Program Files\HP\Remote Graphics Sender. License key les
found in folders specied by the LM_LICENSE_FILE environment variable are not copied; they are
read in place.
If a license key le location is specied during Remote Boost Sender installation and is also specied
by the LM_LICENSE_FILE variable, Remote Boost Sender will look in both locations for a valid local
license key le at startup.
Conguring
on Linux
For Remote Boost Sender on Linux to nd the local license key le, it must be saved in this directory on the
remote computer:
/etc/opt/hpremote/rgsender
Remote Boost Sender to access a local license key le
Conguring
Remote Boost Sender to access a local license key le on Linux
5
3
Installing and conguring the FLEXnet license
server
The FLEXnet license server is required only if you are using the HP Remote Boost oating license.
Before you install the license server
This section provides information to help you plan your installation of the FLEXnet license server.
● The 64-bit version of the FLEXnet license server is provided with Remote Boost.
● Remote Boost FLEXnet server version 11.14.1.1 is required beginning with RGS 7.4. If you have a previous
version installed, it must be uninstalled rst. Previous versions of RGS will still be able to check out
licenses from the newer license server. Licenses from older license servers can be used on newer servers.
NOTE: The FLEXnet license server included with Remote Boost can be run only on Windows and Linux®
operating systems.
● The license server is usually installed on a computer other than one of the computers running Remote
Boost Sender. However, nothing prohibits installing the license server on an Remote Boost Sender
computer.
● When the license server is active on Windows, the following processes will be running:
– HPQ.exe
– Imgrd.exe (x2)
NOTE: Two separate lmgrd.exe processes will be running, one as a service.
NOTE: The FLEXnet license server for Linux has two associated processes, lmgrd and HPQ.
● The HPQ.exe vendor daemon interfaces with Remote Boost Sender and provides license server functions
specic to HP, such as counting Remote Boost oating licenses.
● NOTE: Other products, such as HP OpenView, also have a vendor daemon named HPQ.exe. The
dierent HPQ.exe executable les might not be interchangeable. Furthermore, only one HPQ.exe vendor
daemon at a time can execute on the license server computer. Therefore, a single computer cannot run
two FLEXnet license servers simultaneously.
NOTE: Both processes, lmgrd and HPQ, might require port forwarding in rewalled environments. You
can customize these ports in the license key le.
The Remote Boost license does not support FLEXnet's three-server redundancy capability, also known as
triad license servers.
● During license server installation on Windows, the FLEXnet administration utility, LMTOOLS, is installed.
LMTOOLS provides a graphical user interface that allows you to administer the license server. See Using
LMTOOLS on page 8.
6
Chapter 3 Installing and conguring the FLEXnet license server
License server port conguration
For a Remote Boost Sender to connect to a license server that's behind a rewall, two ports need to be
opened. One for the license server manager and one for the vendor daemon. These ports can be specied in
the oating license key le.
For the license server manager port, if no TCP/IP port number is specied in the oating license key le, one of
the default ports in the range of 27000 - 27009 is used.
For the vendor daemon port, if no TCP/IP port number is specied in the oating license key le, the port is
chosen by the operating system at run-time. There is no set range.
To change the default ports, specify the ports in the oating license key le in this format:
SERVER MyLicenseServer.hp.com <manager port>
VENDOR HPQ PORT=<vendor port>
The following example will set the manager port to 27010 and the vendor port to 27020:
SERVER MyLicenseServer.hp.com 27010
VENDOR HPQ PORT=27020
IMPORTANT: Only modify the ports in the oating license key le. Further modications can invalidate the
license key.
Installing the license server on Windows
To install the license server, perform the following steps.
1. Locate the FLEXnet installation executable, Setup.exe, in the following location in the Remote Boost
installation package:
/flexlm/Setup.exe
2. Move the Setup.exe le to your license server computer.
3. Double-click Setup.exe to begin installation of the license server. If an installation of an older version
of the license server is detected, you will be prompted to uninstall it. If you uninstall the older server
this way, you might be prompted to restart after the uninstall nishes. If you select to restart, you
must restart the installation of the new server when the system starts up again. The default installation
folder, C:\Program Files\HP\Remote Graphics FlexLM, can be changed to another folder.
If the installation is successful, a notication indicating InstallShield Wizard Complete will be displayed.
Starting and stopping the license server on Windows
You can start and stop the license server in two ways:
● Using Windows Services—Open the Windows Control Panel, select Administrative Tools, and then select
Services, which brings up the Services dialog box. Next, open the properties dialog box for the Remote
Graphics FlexLM License Server Service, and click Start. Because the license server is installed with a
Startup type of Automatic, the license server will also start when the computer is restarted. To stop the
license server, click Stop.
License server port
conguration
7
● Using the Service Control (SC) command—The SC command can be used in a Command Prompt window
when run as an administrator to start and stop the license server.
sc start "Remote Graphics FlexLM License Server Service"
sc stop "Remote Graphics FlexLM License Server Service"
Using LMTOOLS
LMTOOLS can be executed from the Start menu as follows:
For Windows 7:
Start>All Programs>HP>Remote Graphics FlexLM>lmtools
For Windows 10:
Start >HP >lmtools
LMTOOLS can be used for tasks such as the following:
● Conguring the license server
● Adding licenses
● Re-reading the license le
● Viewing system information and the license server status
● Troubleshooting issues with the license server
NOTE: Although LMTOOLS provides the Start Server and Stop Server buttons (under the Start/Stop/Reread
tab), HP recommends that the license server be started and stopped using the methods described in Starting
and stopping the license server on Windows on page 7.
For detailed information about this license server and LMTOOLS, go to http://www.revenera.com.
NOTE: LMTOOLS is available on Windows only.
Installing the license server on Linux
Follow the steps outlined here to install the license server on Linux.
● Copy the FlexLM server package to a directory (for example, /opt/hpremote/licensing).
● Extract the tar archive with the command:
/usr/bin/tar xvf flexlm-server.tar.gz
● Change ownership of the directory and executable les to the user account that will run the daemon
(FlexLM recommends using a non-root account).
● Copy the license le or les to a directory that is accessible by the owner of the license tools (For
instance, /opt/hpremote/licensing).
● Create a script that launches lmgrd at boot time as described in the next steps.
8
Chapter 3 Installing and conguring the FLEXnet license server
● On UNIX, or any SysV system, edit the appropriate boot script, which might
be /etc/rc.boot, /etc/rc.local, /etc/rc2.d/Sxxx, /sbin/rc2.d/Sxxxx. Include commands similar to the
following. See the notes section for a full explanation.
/bin/su daniel -c 'echo starting lmgrd
> /opt/hpremote/licensing/boot.log'
/bin/nohup /bin/su daniel -c 'umask 022; \
/opt/hpremote/licensing/flexlm-server/64-bit/lmgrd -c \
/opt/hpremote/licensing/license.dat >> \
/opt/hpremote/licensing/boot.log'
/bin/su daniel -c 'echo exiting >> /opt/hpremote/licensing/boot.log'
● On any UNIX/LINUX SystemD system (RHEL/CENTOS 7.* and up), create a new service unit le
at /etc/systemd/system/exlic.service with the following content:
[Unit]
Description= HP RGS Flexnet License Start Service
After=network.target
[Service]
Type=simple
ExecStart=/opt/hpremote/licensing/start.sh TimeoutStartSec=0
[Install]
WantedBy=default.target
Run the commands systemctl daemon-reload and systemctl enable flexlic.service
to allow service to start at next, and every, system boot.
NOTE: An alternative method to creating a service enabled at boot is to set an @reboot cron job.
However, the license server will be dependent on the cron service working properly.
● Create a boot script at /opt/hpremote/licensing/start.sh with commands like the following:
#!/bin/bash
/bin/su daniel -c 'echo starting lmgrd
> /opt/hpremote/licensing/boot.log'
/bin/su daniel -c 'umask 022; \
/opt/hpremote/licensing/flexlm-server/64-bit/lmgrd -c \
/opt/hpremote/licensing/license.dat >> \
/opt/hpremote/licensing/boot.log'
/bin/su daniel -c 'echo exiting >> /opt/hpremote/licensing/boot.log'
● Please Note the following about how these scripts were written:
Installing the license server on Linux
9
● All paths must be specied in full because paths cannot be assumed at boot time.
● The su command is used to run lmgrd as a non-root user daniel. It is recommended that lmgrd not be run
as root since it is a security risk to run any program as root that does not require root permissions. lmgrd
does not require root permissions.
● Daniel has a csh login, so all commands executed as daniel must be in csh syntax. All commands not
executed as daniel must be in /bin/sh syntax since that is what is used by the boot scripts.
● The use of nohup and sleep are required on some operating systems, notably HP-UX. These are not
needed on Solaris and some other operating systems but are safe to use on all.
Accessing the Remote Boost oating license
This section describes how to access the Remote Boost oating license. After you obtain your oating
license key le, store it on the license server in accordance with the FLEXnet license server conguration
requirements.
NOTE: When you acquire an Remote Boost oating license key, you provide your license server hostname.
The signature included in the license key le reects the hostname that you provide; changing the hostname
within the license key le to a dierent license server invalidates the license key. If you need to change your
license server hostname, contact the appropriate HP Regional License Center.
Conguring Remote Boost Sender to access a oating license
Remote Boost Sender can be congured to access a oating license by setting the LM_LICENSE_FILE
environment variable to point to the Remote Boost license server. Specify the location of the license server in
this format:
<port>@<host>
NOTE: This location should match the values from the SERVER line in the oating license le.
If a port number isn’t specied, the default port 27000 is used. See the following examples:
@MyLicenseServer.hp.com
@15.2.21.129
27002@MyLicenseServer.hp.com
Multiple server locations can be entered, separated by colons, as in the following example:
27000@15.232.16.2:@MyLicenseServer.hp.com:27002@BackupServer.hp.com
NOTE: Remote Boost Sender will sequentially examine each listed license server from left to right until it
nds a license server containing a valid Remote Boost license.
Down, missing, or moved
oating license servers
10
If a license server is down, missing, or has been moved, a Remote Boost connection might fail. Depending
on where the license server is listed in LM_LICENSE_FILE, Remote Boost might wait until a network timeout
occurs when trying to communicate with the license server.
Chapter 3 Installing and conguring the FLEXnet license server
If the timeout is greater than Remote Boost Receiver's Dialog timeout (defaulted to 15 seconds), then a
connection will not be made because Remote Boost expects the connection to be made before the timeout is
reached.
To correct this issue, increase the timeout to 60 seconds or remove the reference to moved or nonexistent
license servers in the LM_LICENSE_FILE environment variable. If the license server is down, resolve that issue
and then retry using Remote Boost.
If you still experience issues, you might need to clean the Windows registry. See Cleaning registry references
to the Flexnet license server on page 17 for more information.
Hosting multiple license key les
If you have multiple license key les, possibly due to purchasing a new Remote Boost version or even licenses
from dierent vendors, they can be hosted in a few dierent ways.
● Multiple license servers, each hosting one license le. Congure the client computers to look to all servers
that host licenses.
● One license server hosting multiple license les. Each license le and associated vendor application
(HPQ.exe for Remote Boost) must be valid for the version of the license server. License les should be
listed in a semicolon-delimited list when running lmgrd.
NOTE: If you are running the license server as a service on Windows, you can edit the service
parameters in LMTOOLS under Cong Services. Select the Service Name to edit, and modify the Path to
the license le to point to the directory where the license les are located. Select Save Service to save
the changes. You must restart the service for changes to take eect.
The service does not allow a semicolon-delimited list of license le names. Instead, all licenses found in
the specied path will be used.
● One license server hosting a combined license le. To be able to combine licenses, they must have been
originally created with the same server information. This means that the SERVER lines must be the same
in all the license les. If the licenses meet these conditions, then you can create a single le by copying
the contents of all the les to a single le. Delete any redundant SERVER or VENDOR lines. Be sure that
you don't edit the content or it will invalidate the license signature.
NOTE: To use multiple licenses of the same product, the license key le might have to be regenerated.
This means that the FEATURE and INCREMENT lines in the license key le describe the license mode for a
product. Only the rst FEATURE line for a feature name is processed by the vendor daemon. If you want
to have additional copies of the same feature, then you must get the license key le re-generated with
multiple INCREMENT lines instead.
For further information about license server congurations, go to http://www.revenera.com.
Hosting multiple license key
les
11
Connect licensing overview4
This section describes licensing of HP ZCentral Connect Software. ZCentral Connect licensing applies to the
Manager software only. Complimentary software, ZCentral Connect Agent and ZCentral Connect Client can be
installed and used without an additional license.
ZCentral Connect licensing is based on a license key le that is obtained from HP after you purchase a LTU
(License to Use) license. The license le is checked by the Manager software each time a user starts a new
session with a host. New sessions will be denied once the licensed maximum is reached. This number is
dened in the license le, denoted as "Qty=N".
For detailed ZCentral Connect information, see the latest version of the HP ZCentral Connect User Guide
bundled with HP ZCentral Connect, available at http://www.hp.com/go/zcentral. You can go visit this website
for information on how to download a free 60 day trial license supporting up to ve connections, or for
information about purchasing and renewing a license.
NOTE: You can download, install, and run ZCentral Connect without a license. However, you cannot
establish any new sessions between a user and host without a valid license le.
Connect license types
ZCentral Connect uses a local license le to license the software and does not support conguring a license
server.
The following ZCentral Connect license types are available:
● License to Use—You can purchase this license type from HP to support the number of concurrent
connections needed for your deployment.
● Trial license—HP oers a free, 60-day trial license for ZCentral Connect which supports up to 5
concurrent connections.
For more information about downloading ZCentral Connect and purchasing a license, go to http://
www.hp.com/go/zcentral.
NOTE: Except for 60-day trial license, ZCentral Connect licenses never expire. However, a new license
purchase is required to upgrade to a newer primary version of ZCentral Connect. For more information, see
Connect license policy on page 13.
Connect version number
The ZCentral Connect version number contains the four components show in the following example.
12
Chapter 4 Connect licensing overview
Figure 4-1 ZCentral Connect version number components
Table 4-1 ZCentral Connect version number components
Item Description
1. Primary release number—A primary release typically contains upgrades and changes signicant enough that
2. Minor release number—When the number is not zero, it represents a minor release, which typically introduces new features
3. Build number—This number represents a build within a release. It is an incremental value that helps HP identify the specic
4. Patch release number—When the number is not zero, it represents a patch release, which is typically only xing major
interoperability with previous primary releases is not guaranteed by HP.
or enhances existing functionality, as well as including changes from any previous patch releases.
build of a release.
security issues or defects.
NOTE: Each release of ZCentral Connect is a complete release of the entire product, regardless of which
components have changed.
NOTE: Connect and Remote Boost are part of the same software solution called ZCentral. While the best
user experience requires customers to have the most up-to-date versions of ZCentral software, ZCentral
Connect supports older versions of Remote Boost, formerly known as HP RGS. Using ZCentral Connect with
an older Remote Boost version will limit some of its management and brokering functionality.
Connect license version date
The license version date in your license le can be located on the rst FEATURE line. It is formatted as
YYYY.MMDD and typically corresponds to the date your license was generated. This version date is used by the
ZCentral Connect licensing mechanism to determine which primary release your license le supports.
NOTE: The license version date should not be confused with the build date. The build date is not used by
the ZCentral Connect licensing mechanism.
Connect license policy
You are only required to purchase a new license for ZCentral Connect when a new primary version of the
software is released, such as ZCentral Connect 20.0. Therefore, when you purchase a license for ZCentral
Connect you are entitled to free upgrades to all future minor and patch releases.
For example, if you purchased an ZCentral Connect 20.0 license, you are entitled to free upgrades to versions
20.x.x.x. However, you would have to purchase a new license to upgrade to the next primary release of
ZCentral Connect.
NOTE: You can view the version of your ZCentral Connect software by logging on to the Administrator
Portal of the ZCentral Connect Manager and viewing the About section.
Connect license version date
13
Providing a hostname and quantity
When you acquire a ZCentral Connect Manager license le, you will need to provide the server hostname
where you intend to install and run the Manager on. To nd the hostname of the server, type 'hostname' into a
Windows Command Prompt.
You will also need to provide a quantity which represents the number of concurrent sessions you wish to
support. The typical use case is to redeem the entire quantity purchased, however it is possible to redeem
partial quantities to provide licensing for sessions in multiple ZCentral Connect Managers.
NOTE: The signature included in the license le reects the hostname and quantity that you provided.
Changing either eld within the license le will invalidate the license key. If you need to change your
Manager server hostname, or if you wish to increase your number of connections, contact the appropriate
HP Regional License Center: https://myhplicensing.hp.com/cwp-ui/static/contactus
Installing a ZCentral Connect license le
Follow the steps outlined here to install a ZCentral Connect license le.
● Copy the license le to the ZCentral Connect Manager data directory:
%PROGRAMDATA%\HP\ZCentralConnectManager
● As administrator, use the Services.msc app to restart the HP ZCentral Connect Manager service.
NOTE: The ZCentral Connect Agent and ZCentral Connect Client do not require a license le.
NOTE: License les must end with the .lic suix.
NOTE: ZCentral Connect licensing mechanism is limited to checking out a single license le at a time. After
upgrading your license, it is recommended that you keep only the latest license in the data directory.
14
Chapter 4 Connect licensing overview
Troubleshooting licensingA
In this section, you learn how to troubleshoot licensing issues.
Troubleshooting Remote Boost Sender licensing
To help debug licensing problems, Remote Boost Sender records licensing failures in a log le.
TIP: The default log le is rg.log, but it might vary if you did custom logging conguration. See the HP
ZCentral Remote Boost User Guide for more information about Remote Boost Sender logging.
If licensing fails, the string FlexLM will be added to the log le. The remainder of the entry will indicate where
Remote Boost Sender is searching for the license key le.
● For local licenses, the location will be the path you specied either during or after installation (see
Installing a local license key le on page 4).
● For oating licenses, the location will be the hostname and port number used to contact the license
server (see Accessing the Remote Boost oating license on page 10).
However, in both cases, the log entry does not identify the specic cause of a licensing failure. For local
licenses, failure to locate the Remote Boost license key le is not dierentiated from an Remote Boost license
key le that is found but contains an invalid license. Likewise, for oating licenses, failure to contact the
license server is not dierentiated from a license server that is contacted but has an invalid Remote Boost
license.
Troubleshooting the FLEXnet license server
To help debug licensing problems, check the license server log le.
NOTE: The log le name and location can vary based on installation.
● For Windows license servers, you can use LMTOOLS to view the log le and server status. You can query
the current status of the license server under Server Status. For license servers running as a service, you
can view the service logs under Cong Services.
● For Linux license servers, the log le is specied in the script that launches lmgrd.
Troubleshooting Connect licensing
There are several reasons licensing can fail for the service account:
1. The license le is not located in the correct directory. Verify that the license le is located in:
%PROGRAMDATA%\HP\ZCentralConnectManager
2. The license le is expired. Check your license le for its expiration date found on the rst line, in the
format DD-MMM-YYYY.
NOTE: This only applies to a trial license type.
Troubleshooting licensing
15
3. The current software version is not supported by the license le. See Connect license version date on
page 13 for details.
4. The license le has been edited. If any of the text in the license le has been edited, the signature
becomes invalid.
5. The license le has a hostname other than the server where you are running the Manager. Verify that
the server where you installed the Manager has the same hostname that you provided during the license
redemption process. See Providing a hostname and quantity on page 14 for details.
NOTE: A trial license does not require a hostname.
To help debug licensing problems, ZCentral Connect Manager records licensing checkout failure warnings in a
log le. The log le, Manager.log, is located in:
%PROGRAMDATA%\HP\ZCentralConnectManager
If a licensing checkout fails, an entry containing the string “License Checkout warning for feature:” will be
added to the log le. The remainder of the entry will indicate which checkout error occurred.
NOTE: These warnings are intended to provide insight. It is sometimes expected to have a license warning
written to the log. The system can write a warning about failure to check out an LTU license, but successfully
check out a Trial license for example. This is the intended behavior.
Contacting HP for licensing support
If you have questions or need assistance with Remote Boost licensing, go to the following:
https://myhplicensing.hp.com/cwp-ui/static/contactus
16
Appendix A Troubleshooting licensing
B
Cleaning registry references to the Flexnet license server
This appendix provides supplemental information about removing FlexLM references from the Windows
registry. The registry keys listed in this appendix are not removed during uninstallation of Remote Boost and
might need to be removed manually if you are experiencing issues using a Flexnet server.
CAUTION: Back up the registry prior to making any changes. See Windows documentation for more
information.
When a FlexLM license server is used with RGS, the FlexLM libraries will add the license server information to
the following registry keys:
● HKLM\SOFTWARE\FLEXlm License Manager\HPQ_LICENSE_FILE
● HKLM\SYSTEM\ControlSet001\Control\Session
Manager\Environment\LM_LICENSE_FILE
● HKLM\SYSTEM\ControlSet001\Control\Session
Manager\Environment\HPQ_LICENSE_FILE
● HKLM\SYSTEM\ControlSet002\Control\Session
Manager\Environment\LM_LICENSE_FILE
● HKLM\SYSTEM\ControlSet002\Control\Session
Manager\Environment\HPQ_LICENSE_FILE
● HKLM\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment\LM_LICENSE_FILE
● HKLM\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment\HPQ_LICENSE_FILE
● HKEY_USERS\.DEFAULT\Software\FLEXlm License Manager\LM_LICENSE_FILE
NOTE: Some keys might not be present in your registry.
In some cases, FlexLM might use other registry entries. To nd them, search the registry for keys named
either LM_LICENSE_FILE or HPQ_LICENSE_FILE. The value of these keys will be the license server paths, as
specied by the environment variables. See Conguring Remote Boost Sender to access a oating license on
page 10 for details on these values and how they are set.
CAUTION: Any registry keys named LM_LICENSE_FILE can be used by any application that accesses a
Flexnet license server on the system. If other applications besides Remote Boost are using a Flexnet license
server, they might be adversely impacted by any changes made to the LM_LICENSE_FILE registry entries. Any
registry keys named "HPQ_LICENSE_FILE" can be used by any HP application that accesses a FlexLM license
server. If other HP applications besides Remote Boost are using a Flexnet license server, they could be
adversely aected by any changes made to the HPQ_LICENSE_FILE registry entries.
Cleaning registry references to the Flexnet license server
17
C
Uninstalling the FLEXnet License Server on Windows
Follow the step here to uninstall the FLEXnet License Server on Windows.
▲ Open the Programs and Features item in Control Panel, and uninstall the entry corresponding to HP
Remote Graphics FlexLM.
18 Appendix C Uninstalling the FLEXnet License Server on Windows
D
Uninstalling the FLEXnet License Server on Linux
Follow the step here to uninstall the FLEXnet License Server on Linux.
▲ Remove the lmgrd, lmutil, and hpq les that were provided in the FlexLM server package. Other cleanup
steps might be required, depending on how the license server was installed (see Installing the license
server on Linux on page 8).
Uninstalling the FLEXnet License Server on Linux 19
Index
F
FlexLM license server....................... 8
FLEXnet license server..................... 6
L
LMTOOLS...........................................8
local license key le
conguring RGS Sender on Linux5
conguring RGS Sender on
Windows.................................4
installing......................................4
20 Index
Loading...