Lenovo ThinkVantage (Client Security Solution 8.21) - Manual (Page 13)

After ownership of the system is configured, each additional Windows user that logs into the system is
automatically prompted with the Client Security sSetup wizard in order to enroll and initialize the user’s
security keys and credentials.
Software emulation of the Trusted Platform Module
Client Security Solution has the option to run without a Trusted Platform Module on qualified systems. The
functionality will be the same except it will use software-based keys instead of using hardware-protected
keys. The software can also be installed with a switch to force it to always use software-based keys instead
of leveraging the Trusted Platform Module. The use of this switch is an installation-time decision, and cannot
be reversed without un-installing and reinstalling the software.
The syntax to force a software emulation of the Trusted Platform Module is:
InstallFile.exe “/v EMULATIONMODE=1”
Installation procedures and command-line parameters
The Microsoft Windows Installer provides several administrative functions through command-line
parameters. The Windows Installer can perform an administrative installation of an application or product to
a network for use by a workgroup or for customization. Command-line options that require a parameter must
be specified with no space between the option and its parameter. For example:
setup.exe /s /v"/qn REBOOT=”R”"
is valid, while
setup.exe /s /v "/qn REBOOT=”R”"
is not.
Note: The default behavior of the installation when executed alone (running setup.exe without any
parameters) is to prompt the user to reboot at the end of the installation. A reboot is required for the program
to function properly. The reboot can be delayed through a command line parameter for a silent installation
as documented in the preceding section and in the example section.
For the Client Security Solution installation package, an administrative installation unpacks the installation
source files to a specified location.
To run an administrative installation execute the setup package from the command line using the /a
parameter:
setup.exe /a
An administrative installation presents a wizard that prompts the administrative user to specify the locations
for unpacking the setup files. The default extract location is C:\. You can choose a new location which may
include drives other than C:\. For example, other local drives or mapped network drives. You can also
create new directories during this step.
To run an administrative installation silently, you can set the public property TARGETDIR on the command
line to specify the extract location:
setup.exe /s /v"/qn TARGETDIR=F:\TVTRR"
or
msiexec.exe /i "Client Security - Password Manager.msi" /qn TARGERDIR=F:\TVTRR
Note: If your version of Windows Installer is not current, setup.exe is configured to update the Windows
Installer engine to Version 3.0. This update will cause the installation action to prompt for a reboot even with
an administrative extract installation. Use the reboot properly to prevent a reboot in this situation. If the
Windows Installer is at least version 3.0, setup.exe will not attempt to update the Windows Installer engine.
Once and administrative installation has been completed, the administrative user can make customizations
to the source files, such as adding settings to the registry. To install from the unpacked source after
Chapter 2 . Installation 7