Installing Siemens

PLM Software
Licensing V4.0 for
Windows
Proprietary & Restricted Rights Notice

This software and related documentation are proprietary to Siemens Product Lifecycle
Management Software Inc.
© 2011 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.

Siemens and the Siemens logo are registered trademarks of Siemens AG. NX is a trademark or
registered trademark of Siemens Product Lifecycle Management Software Inc. or its subsidiaries
in the United States and in other countries. All other trademarks, registered trademarks or service
marks belong to their respective holders
Table of Contents

PREFACE .................................................................................................................................... III

INTENDED AUDIENCE ............................................................................................................................................... III
SCOPE OF THIS GUIDE ............................................................................................................................................... III
CONVENTIONS .......................................................................................................................................................... III
BASIC WINDOWS TECHNIQUES ................................................................................................................................. IV
INTRODUCTION......................................................................................................................... 3
BACKGROUND ............................................................................................................................................................3
PRE-INSTALLATION CONSIDERATIONS ........................................................................... 5
WINDOWS SYSTEM .....................................................................................................................................................5
LICENSE FILE ..............................................................................................................................................................5
ADMINISTRATOR PRIVILEGE .......................................................................................................................................5
FILE SYSTEM REQUIREMENTS .....................................................................................................................................6
TCP/IP NETWORK SERVICES ......................................................................................................................................6
INSTALLATION INSTRUCTIONS .......................................................................................... 8
USING THE MAINTENANCE OPTIONS ..........................................................................................................................9
USING THE MAINTENANCE OPTIONS ..........................................................................................................................9
UNATTENDED INSTALLATIONS......................................................................................... 10

UNINSTALLING COMMON LICENSING ............................................................................ 13

LMTOOLS UTILITY ................................................................................................................ 13

TROUBLESHOOTING ............................................................................................................. 14
WINDOWS DIAGNOSTIC TOOLS ................................................................................................................................ 14
CREATING INSTALLATION LOG FILES ....................................................................................................................... 15
CHECKING THE LICENSE SERVICE ............................................................................................................................ 16
USING THE LMUTIL UTILITY ...................................................................................................................................... 17
CHECKING SERVER LINES ......................................................................................................................................... 18
SECURITY DEVICE NOT INSTALLED .......................................................................................................................... 19
 Version 4.0

Preface

Intended Audience
This guide was written for system administrators at your site responsible for installing and
managing Siemens PLM Software Common Licensing. Those responsible need a good
knowledge of Windows system administration procedures.

Scope of this Guide

This online guide covers the installation of Siemens PLM Software Common Licensing on
supported Windows workstations.

To install Siemens PLM Software Common Licensing, you may need to know basic Windows
commands. This material is not covered in this document.

Conventions
All references to "Windows" in this manual refer to (32 or 64-bit) versions of Windows XP,
Windows Vista and Windows 7.

All references to “Common Licensing” in this manual refer to Siemens PLM Software Common
Licensing.

The “UGS” company name has changed to “Siemens PLM Software”. However, program
names, folder names and the product kit name retain the old UGS name.

Windows menu items and commands will be written in bold letters.

When presenting a series of choices from a Windows pull-down menu, an arrow will be used
to represent the series of submenus, (e.g., Start Programs Accessories Windows
Explorer).

Version 4.0 Installing Common Licensing for Windows iii

Version 4.0

Basic Windows Techniques

This document may require you to use some basic Windows techniques to perform certain
actions. For example, you may need to use Windows Explorer to browse disks and folders, or
you may need to use the tools in the Control Panel to check or change some system settings. You
can reach the Control Panel folder either via your My Computer icon, or through
Start Settings Control Panel. Finally, you may need to use the Windows Task Manager to
check that certain programs are running properly. You can display the Task Manager by right
clicking in an unoccupied area of the Taskbar and then choosing Task Manager. If you are not
familiar with these techniques, please consult your Windows documentation or Help.

iv Installing Common Licensing for Windows Version 4.0

 Version 4.0

Introduction

This document explains how to install Common Licensing on Windows (32 or 64-bit)
operating systems.

The following topics are covered in this document:

 Pre-installation Considerations
 Installation Instructions
 Unattended Installations
 Uninstalling Common Licensing
 LMTOOLS utility
 Troubleshooting

Background
This document describes the installation and running of Common Licensing on Windows
operating systems.

The installation of Common Licensing is accomplished using the supplied setup.exe

program. This program (if you accept the defaults) installs the files into your system‟s
Program Files folder e.g:

C:\Program Files\UGS\UGSLicensing {Windows 32-bit default location}

C:\Program Files (x86)\UGS\UGSLicensing {Windows 64-bit default location}

Note Only a 32-bit version of Common Licensing is available. It may be installed on 64-bit
machines. However, on 64-bit machines the Microsoft OS will enforce their convention
of putting 32-bit products in the “Program Files (x86)” folder.

Common Licensing is a common license server. It is intended to be shared by Siemens

PLM Software products. It is not backward compatible with the old license servers
previously used by Siemens PLM Software products. However, both the old and new
license servers may be installed on the same system.

Version 4.0 Installing Common Licensing for Windows 3

Version 4.0

Common Licensing is implemented as a Windows service called “UGS License Server

(ugslmd)”. Common Licensing uses a client-server architecture in which the license
manager daemon (lmgrd) and the vendor daemon (ugslmd) provide (i.e. serve) license
information to Siemens PLM Software application programs (called clients). The lmgrd
daemon handles the initial contact with the application program (via TCP/IP) then passes
the connection to the ugslmd daemon. Lmgrd also starts and restarts ugslmd. The UGS
License Server (ugslmd) service may be run on your local computer or another computer
on your network.
Note The Common Licensing installation is only required on license server nodes. It is not
necessary to install this service on clients unless the client is also serving licenses, e.g. a
standalone laptop.

Note Some Siemens PLM Software products may support a ”Standalone Licensing” scenario,
whereby there is no Windows license server service required and licensing information is
acquired directly from a file. This requires access to a specially locked license file called
a “Standalone License” file. In this scenario it is not necessary to install the Common
Licensing product.

4 Installing Common Licensing for Windows Version 4.0

 Version 4.0

Pre-installation Considerations

Windows system
The Common Licensing product installation is supported on (32 or 64-bit) versions of
Windows XP, Windows Vista and Windows 7.

Note Networking Protocol. The UGSLicensing V4.0 installation distributed with NX 8.0,
does not support the IPV6 networking protocol. The IPV6 networking must be disabled
for the Common Licensing daemon (ugslmd) to work. This can be accomplished by
going to the Microsoft web page: http://support.microsoft.com/kb/929852 and selecting
the option to disable IPV6.

License file
Prior to beginning the Common Licensing installation, you must have the license file.
The file should have already been provided via e-mail from Siemens PLM Software. It
does not exist on the software media and is not generated by the install. We recommend
that you save the e-mailed license file as a text file in your temporary directory
%TEMP% and that you name this file ugs4.lic. The file may have any name and may
exist anywhere on your system but the install uses the default location for the license file
prompt: %TEMP%\ugs4.lic.

Note Please make sure you have the license file available on your system before beginning the
installation. The installation will not be possible without a license file.

Note Merging Siemens PLM Software license files with any other license file is not supported.

Administrator privilege
To install Common Licensing, you must use the Administrator account or an account
with full Administrator privileges.

Version 4.0 Installing Common Licensing for Windows 5

Version 4.0

File System requirements

The Common Licensing product must be located on an NTFS file system partition; it will
not work correctly on the older FAT file system.

Common Licensing must be installed on a locally mounted disk drive; the Windows OS
will not allow the installation of a “service” on a remotely mapped drive.

TCP/IP Network Services

Note Networking Protocol. The UGSLicensing V4.0 installation distributed with NX 8.0,
does not support the IPV6 networking protocol. The IPV6 networking must be disabled
for the Common Licensing daemon (ugslmd) to work. This can be accomplished by
going to the Microsoft web page: http://support.microsoft.com/kb/929852 and selecting
the option to disable IPV6.

TCP/IP services are required to run Common Licensing. Please make sure that TCP/IP
services are set up and configured for your system. To do this, click on
Start Settings Control Panel Network Connections Local Area
Connection Properties button. TCP/IP should be displayed as one of the installed
protocols.

Siemens PLM Software applications use the TCP/IP network protocol to communicate
with the license server. Even if the UGS License Server (ugslmd) is running on the same
computer, TCP/IP is still used.

If your computer does not have an Ethernet Card configured, you must install the
Microsoft Loopback Adapter, which is a "virtual" network adapter that will allow your
computer to "talk to itself" via TCP/IP.

You may use the ping utility to check that your TCP/IP connection is operational. On the
computer where you will be running the Siemens PLM Software application, open a
Command Prompt window, and type
ping <hostname>
where <hostname> is the name of the computer you will be using as your License
Server. If the network connection is working correctly, several lines of diagnostic output
will be displayed, indicating the time required to transmit packets of data.

If the network connection is not working, you will receive an error message. You must be
able to ping your License Server (and vice versa) in order to run Siemens PLM Software
applications. For help with the ping utility, please consult your Windows documentation
or Help.

6 Installing Common Licensing for Windows Version 4.0

 Version 4.0

Hardware Security Device

{Windows 32-bit only. Hardware keys are not supported on Windows 64-bit}
Individual features of a license file may be node locked to an Ethernet card‟s physical
address or to a hardware security device, also known as a hardware key or dongle. If
individual licenses are node locked to a hardware key, you must attach the hardware key
to the parallel port or USB port of the workstation using those license features. The
Sentinel device driver that communicates with the hardware key must also be installed on
the workstation.
On node-locked Common Licensing clients or Standalone Licensing workstations, the
Sentinel driver must be manually installed. To check the status of the Sentinel driver, see
the section titled Security Device Not Installed.
Note The Sentinel driver installation file can be found on the license server in the following
(default) installation path:
C:\Program Files\UGS\UGSLicensing\Hardware_Key\sentinelsystemdriver.msi

Note The Common Licensing installation will automatically install the “Sentinel” driver by
default on 32-bit machines. If you are not using a hardware key, the “Sentinel” driver
may be safely removed with Add/Remove programs.

Note Hardware keys are not a valid hostid for a license server. The Composite Hostid (CID) is
the only valid hostid for a Common License server.

Version 4.0 Installing Common Licensing for Windows 7

Version 4.0

Installation Instructions

It is assumed that you have checked all of the pre-installation considerations and are
ready to begin the installation.

Use the following steps to perform the installation from disk or DVD:

1. Log into the system using an account with Administrator privileges.

2. Place the media into the DVD drive on your system

3. Select Install License Server from the media Launch screen (if available). {A
media launch screen may not be available, or may be disabled on your system}

OR

Using Windows Explorer, navigate into the ugslicensing040 folder on the DVD
drive, and double click on setup.exe to start the setup program.

4. Welcome dialog - At the welcome dialog, click Next to continue. Clicking on the
Cancel button at anytime during the installation will discontinue (and roll back)
the install.

5. Destination directory - Enter the destination directory path or accept the default
directory path provided. The installation will create the directory if it does not
exist. Click the Browse button to change the destination location.

6. License file - Enter the path to the license file stored on your system or accept the
default path provided. Click the Browse button to change the license file path.

7. Confirmation - The final dialog is the Setup Confirmation screen. To change the
license file path or destination directory, use the Back button to return to the
appropriate dialog.

The setup will install Common Licensing in the destination directory and will be
immediately available to serve licenses.

8 Installing Common Licensing for Windows Version 4.0

 Version 4.0

Using the Maintenance Options

After completing an installation, any subsequent executions of setup.exe will present the
„Maintenance‟ screen. This prompt will offer the option to „Repair‟, „Modify‟ or
„Remove‟ the installation of the product.
The Repair option will attempt to reinstall or correct any files that do not match the
original installation. Be advised that this option can be very slow because it relies on
individual file comparisons.
The Remove option will uninstall the product completely.

Version 4.0 Installing Common Licensing for Windows 9

Version 4.0

Unattended Installations

The installation of Common Licensing can also be accomplished by an unattended (a.k.a.

silent) install. This feature may aid those System Administrators with a large number of
site installations.

Caution Use of this type of installation is intended for experienced installers only.

The unattended installation is controlled by the Windows system component,

msiexec.exe. In order to install silently you must pass switches and Common Licensing
specific properties to msiexec.exe on the command line. The msiexec.exe program has
several command line switches. For full documentation on these switches, see the
Microsoft help documentation (Help and Support) for msiexec.

A few of the commonly used command line switches for msiexec are:

/h – msiexec help, will list available switches.

/i – specifies the input .msi file to be used for installation.

{e.g. msiexec /i “UGSLicensing.msi” will install Common Licensing}

/q – specifies the User Interface level. /qn+ specifies no dialogs except

for the ending “install done” dialog {recommended}. /qn specifies a silent
installation with no dialogs. If this option is used there is no indication
when the install completes, you must use the Task manager to monitor the
“msiexec.exe” process.

/L – specifies a logfile to be created, and the level of the messages to be

written to the logfile. {e.g. msiexec /L*v “logfile”} This example give
the most verbose log file, see msiexec switches for various log switch
options. The log file option can be very useful in troubleshooting
installation problems.

/x – specifies the input .msi file to be used for de-installation.

{e.g. msiexec /x “UGSLicensing.msi” will uninstall Common Licensing}

10 Installing Common Licensing for Windows Version 4.0

 Version 4.0

The configurable properties for the Common Licensing install are:

INSTALLDIR – this property sets the directory where the Common

Licensing files will be installed.

If not specified the default is: “C:\Program Files\UGS\UGSLicensing” or

“C:\Program Files (x86)\UGS\UGSLicensing”.

LICENSEDIR – this property sets the value of the folder containing the
license file to use. If not specified the default is the %TEMP% folder for
your login account.

e.g. for Administrator: C:\Documents and Settings\Administrator\Local

Settings\Temp

LICENSEFILENAME – this property sets the value of the name of the

license file to use. If not specified it will default to ugs4.lic.

Note To specify a complete path to your license file, you must specify BOTH the
LICENSEDIR and LICENSEFILENAME. These two properties are concatenated to
produce the full path.

If you place your license file in %TEMP%\ugs4.lic, you will not need to
specify either parameter.

Caution If the install cannot find the license file, it will not complete.

The following are examples of silent installations.

Caution These examples may appear on multiple lines because of document formatting but
they must be entered on your computer as one line. Any arguments with imbedded
spaces must be quoted.
Default install - The following example installs silently using a default installation. It
will install in the default location and attempt to locate the license file at
%TEMP%\ugs4.lic. The “/qn+” switch will cause one ending message dialog to appear.

msiexec.exe /qn+ /i "UGSLicensing.msi"

Version 4.0 Installing Common Licensing for Windows 11

Version 4.0

Custom Destination - The following example installs silently, to a customized

destination folder. It will attempt to locate the license file at the default location. The
“/qn” switch will cause no dialogs to appear

msiexec.exe /qn /i "UGSLicensing.msi" INSTALLDIR="E:\Test Folder\License

Test”

Custom License file - The following example installs silently, to the default destination
folder but specifies a full path to the license file. The “/qn+” switch will cause one ending
message dialog to appear.

msiexec.exe /i "UGSLicensing.msi" LICENSEDIR=c:\temp

LICENSEFILENAME=YourLicense.txt /qn+

Fully customized install - The following example installs silently, to a custom

destination folder with a custom path to the license file. The “/qn+” switch will cause one
ending message dialog to appear.

msiexec.exe /i "UGSLicensing.msi" INSTALLDIR="E:\Test Folder\License Test”

LICENSEDIR=c:\temp LICENSEFILENAME=YourLicense.txt /qn+

Log switch - The “/L*v” switch can be added to any example above and will cause a
verbose log file to be generated in the location specified in the next argument. Note that
there is no space in the “/L*v” switch. The following example shows a customized
installation with one ending dialog and with a verbose log file in c:\temp\install.log. See
also msiexec help for various log switch options

msiexec.exe /i "UGSLicensing.msi" INSTALLDIR="E:\TestFolder\LicenseTest”

LICENSEDIR=c:\temp LICENSEFILENAME=YourLicense.txt /qn+ /L*v
c:\temp\install.log {There is no space in /L*v but there is a space after the „v‟}

Uninstall - The following example shows an uninstall. Only an ending dialogue will
appear. It is not necessary to specify a previous custom INSTALLDIR.

msiexec.exe /qn+ /x "UGSLicensing.msi"

Note The uninstall does not remove the license file or log file.

12 Installing Common Licensing for Windows Version 4.0

 Version 4.0

Uninstalling Common Licensing

To remove the Common Licensing product, run the Common Licensing setup and select
“Remove” or use the Windows Add/Remove utility and select:

Start Settings Control Panel Add/Remove UGSLicensing

You may also use the msiexec silent install option “/x” to uninstall Common Licensing
{e.g msiexec.exe /x “UGSLicensing.msi” /qn+}

It is not necessary to reboot after uninstalling Common Licensing.

The uninstall does not remove the license file or log file.
There is no separate uninstall program or shortcut.

Lmtools utility

The Common Licensing install will install the lmtools utility and provide a Start Menu
shortcut.

The LMTOOLS interface combines license administration tools and the utilities in the
lmutil executable.
To run from Start menu, double click on the program icon under:
Start Programs UGS Licensing lmtools

Refer to the Macrovision FLEXnet Licensing End User Guide for additional information
on LMTOOLS.

Note The Macrovision company name was changed to Acresso and then again to Flexera.

Version 4.0 Installing Common Licensing for Windows 13

Version 4.0

Troubleshooting

Windows Diagnostic Tools

Windows provides a variety of tools that you can use to understand how your computer is
working and diagnose problems. Some examples are:

Windows System Can be found via Start Programs Accessories System

Info Tools System Information. It provides information about
your system, and allows you to print this information, or save
it in a file. You can also run Windows Diagnostics by typing
winmsd in a Command Prompt window.
Event Viewer Provides you with a log showing various low-level events that
have occurred while your system has been running. Again, you
can typically access this utility via Start Settings Control
Panel Administrative Tools.
System Properties The System Properties item in Control Panel lets you check
and modify the values of environment variables that affect the
behavior of your system. Variables are located under
Start gs
Panel Advanced Environment Variables.
Net Commands Windows provides a wide variety of commands for diagnosing
networking problems, which can affect the system‟s ability to
communicate with the license service. For more information,
you might start by looking up the ping and netstat utilities in
Windows Help, or type net help in a Command Prompt
window.

If you need help with any of these tools, please consult your Windows documentation or
Help.

14 Installing Common Licensing for Windows Version 4.0

 Version 4.0

Creating Installation Log Files

If the installation does not complete successfully, error logs of the installation may
provide helpful information. In a command prompt window enter:

setup.exe /v”/L*v c:\LogFile2.txt”

{where LogFile2 is the full path to your log file. Note: there is no space after the
“/v” switch. This example shows using “setup.exe” to start the log. Setup
actually passes these switches to msiexec.exe}

See also log file examples in the section Unattended Installation of Common Licensing.

Note The msiexec.exe program supports many levels of log file information from terse
start/stop messages to the very verbose log example shown above. See “Help and
Support” on msiexec for information on the levels of logging available.

Version 4.0 Installing Common Licensing for Windows 15

Version 4.0

Checking the License Service

Check that the UGS License Server (ugslmd) service is running, either using Task
Manager or Services.

In Task Manager, you should see running process entries for two lmgrd.exe
processes and one ugslmd.exe process.

Using Control Panel Administrative Tools Services, you should see

UGS License Server (ugslmd) with a status of "Started".

If the service is present, but not running, you may attempt to start it manually. Control
Panel Administrative Tools Services. Right-click the service name "UGS License
Server (ugslmd)", and click Start.

If the UGS License Server (ugslmd) service is unable to start, there may be other
problems. Choose Start Programs UGS Licensing LMTOOLS. In the
Service/License File section, select "Configuration using Services". Click on the "Config
Services" tab. The "UGS License Server (ugslmd)" service should appear in the Service
Name field. Verify that all "path to" entries are valid.

These entries displayed on the LMTOOLS screen should not be blank. If these entries are
blank, enter the correct service name as shown above. Use the browse button to search
the drive for the location of the installed license program (lmgrd.exe). Browse for the
correct license file. The default location for the log file should be set to C:\Program
Files\UGS\UGSLicensing\ugslicensing.log, provided that the directory path is where you
installed Common Licensing. Use the browse button to update this field. Make sure the
two checkboxes, “Start Server at Power Up” and “Use Services”, are both checked (after
checking “Use Services”, “Start Server at Power Up” will become available). Click the
“Save Service” button.

To start the license service from LMTOOLS, open the Start/Stop/Reread tab. Click the
Start button.

Note The graphically-oriented license administration utility LMTOOLS is also available on the
Siemens PLM Software Licensing client if installed.

16 Installing Common Licensing for Windows Version 4.0

 Version 4.0

Using the lmutil utility

The lmutil utility is a command line license administration tool similar to the graphically-
oriented LMTOOLS utility. To use lmutil, open a Command Prompt window to use this
utility and change directory to the appropriate folder. Run the command

lmutil lmstat -c 28000@<hostname> –a

{where 28000 is the default port number and <hostname> is the hostname of the
Common license server}

from the server machine to verify that the vendor daemon is alive. Run the same
command from a client machine to verify the connection across the network from client
to vendor daemon. Other information may be extracted using different switches or
options; these are documented in the Macrovision FLEXlm End User Manual.

For example:

cd /d c:\Program Files\UGS\UGSLicensing {default Windows 32 server

location}

cd /d c:\Program Files (x86)\UGS\UGSLicensing {default Windows 64 server

location}

lmutil lmstat -c 28000@<hostname> –a

{where 28000 is the default port number and <hostname> is the hostname of the
Common license server}

Version 4.0 Installing Common Licensing for Windows 17

Version 4.0

Diagnostic messages will appear telling you some possible sources of your problem.

Some possible outputs:

License File Could Not If you are receiving your license data file via e-mail, you
Be Read need to save it in text format. Some users using MSWord as
their reader may receive garbage in the license file (ugs4.lic)
when it is received in mail. To verify if a license file is
corrupted:
cd /d c:\Program Files\UGS\UGSLicensing
lmutil lmcksum –c ugs4.lic | findstr BAD
See ugslicensing.log When the lmgrd service is started, the log file
ugslicensing.log is created. The ugslicensing log can give
you the best information on the state of the license server.
This file is a text file that can be opened with standard text
editors. Errors may be a result from a corrupted license file,
the lmhostid not matching the license file, or networking
problems involving TCP/IP or DNS configuration. Use the
instructions given earlier to check that there is a working
TCP/IP network connection to your Common License
Server. The log file is located by default at:
c:\Program Files\UGS\UGSLicensing\ugslicensing.log {Win 32}
c:\Program Files (x86)\UGS\UGSLicensing\ugslicensing.log
{Win 64}

Checking Server lines

Check that the real hostname of the license server is on the SERVER line of the license
file. The license file is electronically provided by Siemens PLM Software with
'YourHostname' or 'this_host' on the SERVER line as a placeholder for the real hostname
of the license server. The installation will edit the license file to automatically change
"YourHostname" or "this_host" keyword to the actual hostname of the license server.
However, this field must be edited manually for any subsequent updates of the license
file and for redundant server configurations (i.e. license files containing 3 SERVER
lines).

18 Installing Common Licensing for Windows Version 4.0

 Version 4.0

Security Device Not Installed

{Windows 32-bit only. Hardware keys are not supported on Windows 64-bit.}

If the Hardware Key is not installed properly or if the Sentinel System Driver is not
installed and started, when a node-locked feature is attempted to be checked out, an error
message similar to the following will be displayed:
FLEXnet Licensing error: -9
Invalid host
The hostid of this system does not match the hosted specified in the license file.
Feature: gateway
Hostid: UG_HWKEY_ID=13625
License path: 28000@server1
FLEXnet Licensing error: -9,333

In addition, the debug log ugslicensing.log file will contain errors like the following:

DENIED: “gateway” fred@barney (INVALID error code (-9999,333)

DENIED: “gateway” fred@barney (Invalid host. (-9,333)

In these cases, check the following:

Make sure the Hardware Key is plugged in securely.
Make sure that the license file (e.g. ugs4.lic) has the same number in the
UG_HWKEY_ID field that is printed on the Hardware Key itself.
Check the status of the Sentinel driver:
For a Parallel Port hardware key, make sure that the “Sentinel” Windows device
driver appears in Device Manager and is in its Started state
Control Panel System Hardware Device Manager View Show
Hidden Devices Non-plug and Play Drivers Sentinel (double-click)
For a USB hardware key, make sure that Device Manager shows an entry for
Rainbow USB SuperPro key.
Control Panel System Hardware Device Manager Universal
Serial Bus Controllers Rainbow USB SuperPro
If the Sentinel driver is missing, manually install it; the Sentinel driver installation file
can be found on the license server in the following (default) installation path:
C:\Program Files\UGS\UGSLicensing\Hardware_Key\sentinelsystemdriver.msi

Version 4.0 Installing Common Licensing for Windows 19