User guide

RGS overview 18
2-2 RGS version numbering
The RGS version (for example, version 5.2.0) contains the following three numbers:
1. Version major number
2. Version minor number
3. Version patch number
Figure 2-2 shows the positioning of the three version numbers.
Figure 2-2 RGS version numbering
NOTE: Each patch release is a complete release of the entire RGS product, regardless of what components
have changed. For example, if a patch release is needed to make an RGS Sender security fix available, the
entire RGS product (including both the RGS Sender and Receiver) would be included in the patch release.
2-3 RGS licensing
Beginning at RGS 5.2.0, HP implemented a licensing mechanism for RGS based on FLEXnet Publisher (“FLEXnet”)
by Acresso Software. FLEXnet, formerly known as FLEXlm, uses files (called license files) that contain information
such as the type of license and the MAC address of the licensed computer(s).
IMPORTANT: RGS licensing applies to the RGS Sender only. The RGS Receiver is a free download and can be
used on any number of computers. Therefore, the following discussion of RGS licensing applies only to the RGS
Sender. For detailed information on RGS licensing, see the HP Remote Graphics Software Licensing Guide,
available at www.hp.com/support/rgs_manuals
.
Two types of licenses are supported by the RGS Sender:
1. Floating licenses—With floating licenses, a pool of RGS licenses is purchased, which are dynamically
allocated on a first-come, first-serve basis whenever an RGS Receiver attempts to connect to an RGS Sender.
In licensing terminology, a floating license is checked-out when a connection is established to the RGS
Sender, and is checked-in when the connection terminates.
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 an RGS connection
simultaneously.
major.minor.patch
# # #
Releases in which the major version number
changes contain significant new functionality
such that interoperability with the previous
major release stream is not guaranteed. For
example, RGS Sender version 5.2.0 is not
guaranteed to interoperate with RGS Receiver
version 4.2.0.
Patch releases are generated only for a
security issue or for a major defect in a
feature. A patch release is indicated by this
number being non-zero
. Therefore, RGS 5.2.1
would be a patch release, while RGS 5.2.0
would not be a patch release.
RGS 5.2.0
Minor releases introduce new RGS features
and functionality. Minor releases will also
include (roll up) the changes in any prior
patch releases. RGS 5.2.0 is a minor release.