HP t620 Flexible Thin Client Guide

HP ThinPro 5.2

Administrator Guide

© Copyright 2015 Hewlett-Packard

Development Company, L.P.

Citrix and XenDesktop are trademarks of Citrix

Systems, Inc. and/or one more of its subsidiaries, and may be registered in the

United States Patent and Trademark Office and in other countries. Linux

®

is the registered trademark of Linus Torvalds in the U.S. and other countries. Microsoft, Windows, Windows

Vista, and Windows Server are trademarks of the Microsoft group of companies. UNIX is a registered trademark of The Open Group.

VMware and Horizon View are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.

Confidential 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.

First Edition: May 2015

Document Part Number: 824313-001

Open source software

This product includes software licensed under an open source software license, such as the GNU General

Public License and the GNU Lesser General Public License or other open source license. To the extent HP has an obligation or, in its sole discretion, chooses to make the source code for such software available under the applicable open source software license, source code for the software may be obtained from the ftp: ftp://ftp.hp.com/pub/tcdebian/pool/thinpro52/source/ .

iii

iv Open source software

About this guide

This guide uses the following styles to distinguish elements of text:

Style

<variable>

[optional parameters]

“literal value”

Definition

Variables or placeholders are enclosed in angle brackets. For example, replace <pathname> with the appropriate path, such as C:\Windows\System. When typing the actual value for the variable, omit the brackets.

Optional parameters are enclosed in square brackets. When specifying the parameters, omit the brackets.

Command line text that appears inside quotation marks should be typed exactly as shown, including the quotation marks.

v

vi About this guide

Table of contents

1 Welcome ....................................................................................................................................................... 1

Finding more resources ......................................................................................................................................... 1

Comparison of ThinPro and Smart Zero ................................................................................................................ 1

Document organization ......................................................................................................................................... 2

2 Getting started ............................................................................................................................................. 3

Choosing a management service .......................................................................................................................... 3

Starting HP ThinPro for the first time .................................................................................................................... 3

3 Navigating the interface ................................................................................................................................ 5

Using the taskbar ................................................................................................................................................... 5

Using the Connection Manager controls ............................................................................................................... 6

Viewing system information .................................................................................................................................. 7

Hiding the system information screens .............................................................................................. 7

4 Control Panel configurations .......................................................................................................................... 8

Control Panel overview .......................................................................................................................................... 9

Client aggregation ............................................................................................................................................... 12

Configuring client aggregation ......................................................................................................... 13

Configuring the aggregation clients ............................................................................... 13

Configuring the aggregation server ............................................................................... 14

Display preferences ............................................................................................................................................. 14

Configuring printers ............................................................................................................................................. 14

Redirecting USB devices ...................................................................................................................................... 15

Network settings ................................................................................................................................................. 15

Wired network settings ..................................................................................................................... 16

Wireless network settings ................................................................................................................ 16

DNS settings ...................................................................................................................................... 17

IPSec rules ......................................................................................................................................... 17

Configuring VPN settings .................................................................................................................. 18

Configuring HP Velocity ..................................................................................................................... 18

Component Manager ........................................................................................................................................... 18

Removing components ..................................................................................................................... 19

Undoing a change .............................................................................................................................. 19

Applying the changes permanently .................................................................................................. 19

Customization Center .......................................................................................................................................... 19

vii

viii

HP ThinState ........................................................................................................................................................ 20

Managing an HP ThinPro image ........................................................................................................ 20

Capturing an HP ThinPro image to an FTP server .......................................................... 20

Deploying an HP ThinPro image using FTP or HTTP ...................................................... 21

Capturing an HP ThinPro image to a USB flash drive ..................................................... 21

Deploying an HP ThinPro image with a USB flash drive ................................................. 21

Managing a ThinPro profile ............................................................................................................... 22

Saving a ThinPro profile to an FTP server ...................................................................... 22

Restoring a ThinPro profile using FTP or HTTP .............................................................. 22

Saving a ThinPro profile to a USB flash drive ................................................................. 23

Restoring a ThinPro profile from a USB flash drive ........................................................ 23

VNC Shadowing .................................................................................................................................................... 23

Certificates ........................................................................................................................................................... 24

Certificate Manager ........................................................................................................................... 24

SCEP Manager .................................................................................................................................... 24

DHCP options ....................................................................................................................................................... 25

5 Common connection configurations .............................................................................................................. 26

Common connection settings .............................................................................................................................. 26

Kiosk mode .......................................................................................................................................................... 27

6 Citrix connections ........................................................................................................................................ 28

Citrix Receiver features ........................................................................................................................................ 28

HDX MediaStream .............................................................................................................................. 29

HP True Graphics ............................................................................................................................... 30

HP True Graphics server-side requirements .................................................................. 30

XenApp/XenDesktop .................................................................................... 30

HDX 3D Pro .................................................................................................... 30

Verifying server compression options ......................................................... 30

HP True Graphics client-side configuration .................................................................... 30

Compression settings ................................................................................... 30

Window settings ........................................................................................... 31

Monitor layout and hardware limitations .................................................... 31

Citrix connection support matrix ......................................................................................................................... 31

Citrix general settings ......................................................................................................................................... 31

Citrix connection-specific settings ...................................................................................................................... 34

7 RDP connections .......................................................................................................................................... 36

RDP features ........................................................................................................................................................ 36

RDP general settings ........................................................................................................................................... 36

RDP connection-specific settings ........................................................................................................................ 36

Using RemoteFX with RDP ................................................................................................................................... 40

Using multi-monitor sessions with RDP .............................................................................................................. 41

Using multimedia redirection with RDP .............................................................................................................. 41

Using device redirection with RDP ....................................................................................................................... 42

Using USB redirection with RDP ........................................................................................................ 42

Using mass storage redirection with RDP ......................................................................................... 42

Using printer redirection with RDP .................................................................................................... 43

Using audio redirection with RDP ...................................................................................................... 43

Using smart card redirection with RDP ............................................................................................. 44

8 VMware Horizon View connections ................................................................................................................ 45

VMware Horizon View settings ............................................................................................................................ 45

Using multi-monitor sessions with VMware Horizon View ................................................................................. 48

Using keyboard shortcuts with VMware Horizon View ....................................................................................... 48

Using Multimedia Redirection with VMware Horizon View ................................................................................. 48

Using device redirection with VMware Horizon View .......................................................................................... 48

Using USB redirection with VMware Horizon View ............................................................................ 48

Using mass storage redirection with VMware Horizon View ............................................................ 48

Using printer redirection with VMware Horizon View ....................................................................... 49

Using audio redirection with VMware Horizon View ......................................................................... 49

Using smart card redirection with VMware Horizon View ................................................................ 49

Using webcam redirection with VMware Horizon View .................................................................... 50

Changing the VMware Horizon View protocol type ............................................................................................. 50

VMware Horizon View HTTPS and certificate management requirements ........................................................ 50

9 Web Browser connections ............................................................................................................................. 52

Web Browser general settings ............................................................................................................................ 52

Web Browser connection-specific settings ......................................................................................................... 52

10 Additional connection types (ThinPro configuration only) ............................................................................. 53

TeemTalk connection settings ............................................................................................................................. 53

XDMCP connection settings ................................................................................................................................. 55

SSH connection settings ...................................................................................................................................... 55

Telnet connection settings .................................................................................................................................. 57

Custom connection settings ................................................................................................................................ 57

11 HP Smart Client Services ............................................................................................................................ 58

Supported operating systems ............................................................................................................................. 58

Prerequisites for HP Smart Client Services ......................................................................................................... 58

ix

x

Obtaining HP Smart Client Services .................................................................................................................... 58

Viewing the Automatic Update website .............................................................................................................. 59

Creating an Automatic Update profile ................................................................................................................. 59

Updating thin clients ........................................................................................................................................... 59

Using the broadcast update method ................................................................................................ 59

Using the DHCP tag update method ................................................................................................. 60

Example of performing DHCP tagging ............................................................................ 60

Using the DNS alias update method ................................................................................................. 60

Using the manual update method .................................................................................................... 60

Performing a manual update .......................................................................................... 61

12 Using the Profile Editor .............................................................................................................................. 62

Accessing the Profile Editor ................................................................................................................................. 62

Loading a ThinPro profile .................................................................................................................................... 62

Modifying a ThinPro profile ................................................................................................................................. 62

Selecting the platform for a ThinPro profile ..................................................................................... 63

Configuring a default connection for a ThinPro profile .................................................................... 63

Modifying the registry settings of a ThinPro profile ........................................................................ 63

Adding files to a ThinPro profile ........................................................................................................ 63

Adding a configuration file to a ThinPro profile ............................................................. 64

Adding certificates to a ThinPro profile ....................................................... 64

Adding a symbolic link to a ThinPro profile .................................................................... 64

Saving the ThinPro profile ................................................................................................................. 65

Configuring a serial or parallel printer ................................................................................................................ 65

Obtaining the printer settings ........................................................................................................... 65

Setting up printer ports ..................................................................................................................... 65

Installing printers on the server ....................................................................................................... 66

13 Troubleshooting ........................................................................................................................................ 67

Troubleshooting network connectivity ............................................................................................................... 67

Troubleshooting firmware corruption ................................................................................................................. 67

Reimaging thin client firmware ......................................................................................................... 68

Troubleshooting Citrix password expiration ....................................................................................................... 68

Using system diagnostics to troubleshoot .......................................................................................................... 68

Saving system diagnostic data ......................................................................................................... 68

Uncompressing the system diagnostic files ..................................................................................... 68

Uncompressing the system diagnostic files on Windows-based systems .................... 68

Uncompressing the system diagnostic files in Linux- or Unix-based systems ............. 69

Viewing the system diagnostic files .................................................................................................. 69

Viewing files in the Commands folder ............................................................................ 69

Viewing files in the /var/log folder ................................................................................. 69

Viewing files in the /etc folder ........................................................................................ 69

Appendix A USB updates ................................................................................................................................. 70

Appendix B BIOS tools ..................................................................................................................................... 71

BIOS settings tool ................................................................................................................................................ 71

BIOS flashing tool ................................................................................................................................................ 71

Appendix C Resizing the flash drive partition .................................................................................................... 72

Appendix D Customizing the Smart Zero login screen ........................................................................................ 73

Customizing the screen background ................................................................................................................... 73

Common attributes ........................................................................................................................... 73

Elements ............................................................................................................................................ 75

Image ................................................................................................................................................. 77

Text .................................................................................................................................................... 78

Appendix E Registry keys ................................................................................................................................ 81

root > Audio ......................................................................................................................................................... 82 root > CertMgr ...................................................................................................................................................... 82

root > ComponentMgr ......................................................................................................................................... 83 root > ConnectionManager .................................................................................................................................. 83 root > ConnectionType ........................................................................................................................................ 83 root > ConnectionType > custom ...................................................................................................... 83

root > ConnectionType > firefox ....................................................................................................... 86

root > ConnectionType > freerdp ...................................................................................................... 90

root > ConnectionType > ssh ............................................................................................................. 98

root > ConnectionType > teemtalk ................................................................................................. 102

root > ConnectionType > telnet ...................................................................................................... 105

root > ConnectionType > view ......................................................................................................... 109

root > ConnectionType > xdmcp ..................................................................................................... 116

root > ConnectionType > xen .......................................................................................................... 119

root > CpuMgr .................................................................................................................................................... 131 root > DHCP ........................................................................................................................................................ 131 root > Dashboard ............................................................................................................................................... 131

root > Display ..................................................................................................................................................... 132

root > Network ................................................................................................................................................... 134

root > SCIM ......................................................................................................................................................... 139 root > ScepMgr ................................................................................................................................................... 139

root > Search ...................................................................................................................................................... 140

xi

xii

root > Serial ....................................................................................................................................................... 141 root > SystemInfo .............................................................................................................................................. 141

root > TaskMgr ................................................................................................................................................... 142 root > USB .......................................................................................................................................................... 142 root > auto-update ............................................................................................................................................ 142

root > background ............................................................................................................................................. 144

root > config-wizard .......................................................................................................................................... 145 root > desktop ................................................................................................................................................... 145 root > entries ..................................................................................................................................................... 145

root > keyboard ................................................................................................................................................. 146

root > logging .................................................................................................................................................... 147 root > mouse ...................................................................................................................................................... 147 root > restore-points ......................................................................................................................................... 147 root > screensaver ............................................................................................................................................. 147

root > security ................................................................................................................................................... 148

root > sshd ......................................................................................................................................................... 149 root > time ......................................................................................................................................................... 149

root > touchscreen ............................................................................................................................................. 150 root > translation ............................................................................................................................................... 150

root > usb-update .............................................................................................................................................. 151 root > users ........................................................................................................................................................ 151

root > vncserver ................................................................................................................................................. 153

Index ........................................................................................................................................................... 156

1 Welcome

This guide is intended for administrators of HP thin client models that are based on the HP ThinPro operating system. It is assumed that you are using the latest image provided by HP and that you log on as an administrator when making configurations or accessing administration utilities.

Finding more resources

Resource

HP support website http://www.hp.com/support

Contents

Image updates and add-ons

Documentation for HP software not covered in detail in this guide

TIP:

If your search results cannot locate the software you are looking for, search for the thin client model instead.

Documentation for Microsoft software not covered in detail in this guide Microsoft support website http://support.microsoft.com

Citrix support website http://www.citrix.com/support

VMware support website http://www.vmware.com/support

Documentation for Citrix software not covered in detail in this guide

Documentation for VMware software not covered in detail in this guide

Comparison of ThinPro and Smart Zero

Beginning with HP ThinPro 5.0, ThinPro and Smart Zero are two different configurations of the same operating system image. You can easily switch between the two configurations using an option in the Control

Panel. See the following table for a comparison of ThinPro and Smart Zero.

Default available connection types

NOTE:

You can change which connection types are available using the registry key priorityInConnectionLists for each connection type. See

root > ConnectionType on page 83 for more information.

ThinPro

●

Citrix

●

RDP

●

VMware Horizon View

●

Web Browser (Firefox)

●

TeemTalk

●

XDMCP

●

SSH

●

Telnet

●

Custom

Number of connections supported simultaneously

Multiple

Configured for kiosk mode by default

No

Smart Zero

●

Citrix

●

RDP

●

VMware Horizon View

●

Web Browser (Firefox)

One

Yes

Finding more resources 1

Document organization

This guide is divided into the following chapters and appendixes:

●

Getting started on page 3

—Describes the basic steps to deploy a thin client running HP ThinPro.

●

Navigating the interface on page 5 —Provides an overview of the different components of the

interface.

●

Control Panel configurations on page 8

—Describes the connection-related settings and configurations in the Control Panel and details some of the more advanced configurations.

●

Common connection configurations on page 26

—Describes settings that are common to all connection types and configuring a thin client for kiosk mode.

●

Citrix connections on page 28

—Describes the settings and configurations for the Citrix connection type.

●

RDP connections on page 36

—Describes the settings and configurations for the RDP connection type.

●

VMware Horizon View connections on page 45

—Describes the settings and configurations for the

VMware Horizon View connection type.

●

Web Browser connections on page 52

—Describes the settings for the Web Browser connection type.

●

Additional connection types (ThinPro configuration only) on page 53

—Describes the settings for the

TeemTalk, XDMCP, SSH, Telnet, and Custom connection types.

●

HP Smart Client Services on page 58 —Describes how to use HP Smart Client Services to remotely

manage large numbers of thin clients using Automatic Update.

●

Using the Profile Editor on page 62 —Describes using the Profile Editor to set up and edit ThinPro

profiles, which contain connection information, settings, and files used in the self-configuration process.

●

Troubleshooting on page 67 —Describes common troubleshooting issues and solutions.

●

USB updates on page 70 —Describes how to install add-ons and profile updates from a USB flash

drive.

●

BIOS tools on page 71

—Describes how to view and update BIOS settings and flash a new BIOS version.

●

Resizing the flash drive partition on page 72

—Describes how to increase the size of the flash drive partition.

●

Customizing the Smart Zero login screen on page 73 —Describes the common attributes and elements

used in customizing the Smart Zero login screen.

●

Registry keys on page 81

—Lists the paths, functions, and options for the HP ThinPro registry keys.

2 Chapter 1 Welcome

2 Getting started

Choosing a management service

Thin clients running HP ThinPro can be managed by either HP Smart Client Services or HP Device Manager

(HPDM). You can use whichever management service is best for your deployment.

HP Smart Client Services is optimized for use with Smart Zero. This option allows for zero management.

HPDM is ideal for large environments that contain thin clients with a variety of different operating systems.

This option provides more visibility to thin clients and a greater variety of management options.

Starting HP ThinPro for the first time

When you first turn on a new thin client running HP ThinPro, a setup utility runs.

First, the setup utility checks for a network connection. If specific network settings are required, click the

Network Settings button to open the Network Manager (see Network settings on page 15 for more

information).

The setup utility then checks to see if the thin client is being managed by either HP Smart Client Services or

HP Device Manager (HPDM). If the thin client is being managed by either program, the setup utility exits and the management program performs predefined configurations to the thin client.

NOTE:

For more information about HP Smart Client Services, see

HP Smart Client Services on page 58

. For more information about HPDM, go to http://www.hp.com/go/hpdm .

If the thin client is not being managed by either HP Smart Client Services or HPDM, the utility checks whether there is an image update available from HP. If there is, click Install now on the Software Update tab to update the image.

TIP:

If you want to maintain your own internal site for image updates, you can customize where the operating system looks for updates by changing the following registry key: root/config-wizard/FirmwareUpdate/firmwareUpdateURL

If you want to verify whether service packs or package updates are available, click Easy Update to launch HP

Easy Tools.

If you need to manually configure the HPDM Agent or the Automatic Update settings for HP Smart Client

Services, click the Device Management tab of the setup utility and choose the appropriate option.

TIP:

If you want to check for software updates every time the thin client starts up, enable the Check for

software updates every boot option.

If you want to preserve your thin client configuration when you upgrade your image version, enable the

Preserve thin client configuration option.

After you close the setup utility, if no connections are configured, you are prompted to configure a connection.

NOTE:

This initial connection wizard offers a quicker setup process than the standard Connection Manager wizard.

Choosing a management service 3

If you plan to configure a single thin client and then copy and deploy its configurations to other thin clients

using HP ThinState (see HP ThinState on page 20

), use the Control Panel to make all of the desired

configurations first. See Navigating the interface on page 5 and

Control Panel configurations on page 8

for more information.

4 Chapter 2 Getting started

3 Navigating the interface

This chapter discusses the following topics:

●

Using the taskbar

●

Using the Connection Manager controls

●

Viewing system information

Using the taskbar

7

8

Table 3-1 Taskbar components

1

2

3

4

5

6

Search—Lets you search for and run configured connections, connection managers, Control Panel utilities, and power functions.

Connection Manager—Lets you start, stop, add, edit, and delete connections. See

Using the Connection

Manager controls on page 6 for more information.

Control Panel—Lets you configure the thin client, switch between Administrator Mode and User Mode, and

check for software updates. See Control Panel overview on page 9

for more information.

System Information—Lets you view system, network, and software information about the thin client. See

Viewing system information on page 7

for more information.

Application area—Displays the icons for the currently open applications.

TIP:

You can hold down Ctrl + Alt and then press Tab repeatedly to select an application to bring to the foreground.

System tray—Provides quick access to or provides information about certain utilities, applications, and functions. Items in the system tray can include the following, but some items might not appear depending on the system configuration:

●

Audio mixer

●

Virtual keyboard

●

Network status

●

Automatic Update status—A green icon with a checkmark indicates that Automatic Update finished successfully. A yellow icon with an exclamation point indicates that the Automatic Update server was not found or that there are some problems with the server-side settings. A red icon with an X indicates that

Automatic Update failed, such as when a package or profile is invalid. A blue icon with a spinning arrow indicates that Automatic Update is currently checking for updates.

●

Smart Common Input Method (SCIM) controls

●

Citrix applications

Date and time—Displays the current date and time. Click to access the date and time settings.

Power button—Lets you log out of, restart, or shut down the thin client.

Using the taskbar 5

Using the Connection Manager controls

1

2

3

4

5

6

Start—Starts the selected connection.

Stop—Stops the selected connection.

Edit—Opens a Connection Manager specific to the selected connection type (such as the Citrix Connection

Manager), allowing you to edit settings that are specific to the selected connection only.

Delete—Deletes the selected connection.

Add—Lets you add a new connection.

NOTE:

See Comparison of ThinPro and Smart Zero on page 1 for a list of the available connection types.

Settings—Lets you edit general settings for Citrix, RDP, or Web Browser connections. These settings apply to all connections of that type.

For more information about configuring connections, see the following:

●

Common connection configurations on page 26

●

Citrix connections on page 28

●

RDP connections on page 36

●

VMware Horizon View connections on page 45

●

Web Browser connections on page 52

●

Additional connection types (ThinPro configuration only) on page 53

6 Chapter 3 Navigating the interface

Viewing system information

Click the System Information button on the taskbar to view system, network, and software information about the thin client. The following table describes the information that is displayed on each tab.

Table 3-2 System Information tabs

Tab Description

General

Network

Net Tools

Software Information

System Logs

Displays information about the BIOS, operating system, CPU, and memory.

Displays information about the network interface, gateway, and DNS settings.

Provides the following tools for monitoring and troubleshooting purposes:

●

Ping—Specify an IP address of another device on the network to attempt to establish contact.

●

DNS Lookup—Use this tool to resolve a domain name into an IP address.

●

Trace Route—Use this tool to track the path that a network packet takes from one device to another.

Displays a list of installed add-ons on the Service Packs tab and software version information on the Software Installed tab.

TIP:

You can also access the Administrator Guide (this document) from this screen.

Displays the following logs:

●

Network Manager

●

Smart Client Services

●

DHCP Wired Leases

●

DHCP Wireless Leases

●

Kernel

●

X Server

●

Connection Manager

The debug level can be changed to display additional information that might be requested by HP support for troubleshooting purposes.

Click Diagnostic to save a diagnostic file. For more information, see Using system diagnostics to troubleshoot on page 68 .

Hiding the system information screens

See

root > SystemInfo on page 141 for information about registry keys that can be used to hide the System

Information screens.

Viewing system information 7

4 Control Panel configurations

This chapter includes the topics as follows:

●

Control Panel overview

●

Client aggregation

●

Display preferences

●

Configuring printers

●

Redirecting USB devices

●

Network settings

●

Component Manager

●

Customization Center

●

HP ThinState

●

VNC Shadowing

●

Certificates

●

DHCP options

8 Chapter 4 Control Panel configurations

Control Panel overview

The Control Panel provides access to utilities for configuring the thin client. All of the utilities are accessible in

Administrator Mode. When in User Mode, only the utilities that are enabled by the administrator for use by users are accessible.

To switch between Administrator Mode and User Mode:

▲

Select Administrator/User Mode Switch in the Control Panel.

The first time you switch to Administrator Mode, you will be prompted to set up an administrator password.

The administrator password must be entered to switch to Administrator Mode every subsequent time.

TIP:

When in Administrator Mode, the screen is surrounded by a red border.

The following tables describe the Control Panel utilities available in each of the menu categories.

TIP:

To specify which utilities standard users have access to, select Setup > Customization Center in the

Control Panel and select or deselect utilities in the Applications list.

Table 4-1 Control Panel > Peripherals

Menu option

Client Aggregation

Display Preferences

Keyboard Layout

Sound

Mouse

Printers

Touch Screen

USB Manager

SCIM Input Method Setup

Description

Lets you combine thin clients to create additional screen real estate.

For more information, see

Client aggregation on page 12

.

Lets you configure and test options for both a primary and secondary display.

For more information, see

Display preferences on page 14 .

Lets you change the keyboard layout to accommodate the language used by the keyboard.

Lets you control the playback and input audio levels.

Lets you configure the mouse speed and whether mouse input is right-handed or left-handed.

Lets you set up local and network printers. Local printers can be shared across the network.

For more information, see

Configuring printers on page 14

.

Lets you configure touch screen options.

Lets you configure the redirection options for USB devices.

For more information, see

Redirecting USB devices on page 15

.

Lets you configure the Smart Common Input Method (SCIM) for

Chinese, Japanese, and Korean input.

For more information on this open source program, go to http://sourceforge.net/apps/mediawiki/scim/index.php?

title=Main_Page .

Control Panel overview 9

Table 4-2 Control Panel > Setup

Menu option

Background Manager

Date and Time

Language

Network

Screensaver

Security

Customization Center

Table 4-3 Control Panel > Management

Menu option

AD/DDNS Manager

HPDM Agent

Automatic Update

Component Manager

Easy Update

Description

Lets you configure the background theme.

Lets you configure the time zone and the date and time options.

Lets you display the HP ThinPro interface in a different language.

Lets you configure network settings.

For more information, see Network settings on page 15

.

Lets you configure a screensaver.

Lets you set up or change system passwords for the thin client administrator and user.

Lets you do the following:

●

Switch between the ThinPro and Smart Zero configurations

●

Configure desktop and taskbar options

●

Select which connection types and control panel utilities standard users have access to

For more information, see Customization Center on page 19

.

Description

Lets you add the thin client to an organizational unit of the Active

Directory server and enable automatic Dynamic DNS updates of the thin client's name and IP address association.

NOTE:

This utility does not enable authentication against the

Active Directory database.

Lets you configure the HP Device Manager (HPDM) Agent.

For more information about HP Device Manager, see the HP Device

Manager Administrator Guide.

Lets you configure the Automatic Update server manually.

For more information, see HP Smart Client Services on page 58

.

Lets you remove system components.

For more information, see Component Manager on page 18 .

Opens the Easy Update wizard. Easy Update is a component of HP

Easy Tools that lets you install the latest software updates for the thin client.

TIP:

Selecting Preserve thin client Configuration when performing an image update preserves all previously configured settings.

For more information about HP Easy Tools, see the HP Easy Tools

Administrator Guide.

Lets you restore the thin client to its default factory configuration.

Factory Reset

10 Chapter 4 Control Panel configurations

Table 4-3 Control Panel > Management (continued)

Menu option

Snapshots

SSHD Manager

ThinState

VNC Shadow

Wireless Statistics

Table 4-4 Control Panel > Advanced

Menu option

Certificates

Description

Lets you restore the thin client to a previous state or to its default factory configuration.

Enables access through a secure shell.

HP ThinState lets you make a copy of or restore the entire operating system image or just its configuration settings.

For more information, see

HP ThinState on page 20 .

Lets you configure VNC Shadowing options.

For more information, see

VNC Shadowing on page 23 .

Lets you view information about wireless access points.

CPU Manager

DHCP Options

SCEP Manager

Serial Manager

Keyboard Shortcuts

Task Manager

Text Editor

X Terminal

Table 4-5 Control Panel > Miscellaneous

Menu option

Snipping Tool

Description

Opens the Certificate Manager, which lets you easily import, view, or remove certificates.

For more information, see

Certificate Manager on page 24

.

Lets you choose between Balanced and High Performance CPU performance.

Lets you configure DHCP options.

For more information, see

DHCP options on page 25 .

Allows for network-based certificate management.

Lets you configure serial devices.

Lets you create, modify, and delete keyboard shortcuts.

Lets you monitor the CPU usage and the CPU usage history for the thin client.

Opens a basic text editor for viewing and editing text files.

Lets you execute Linux commands.

Description

Lets you take a snapshot of a rectangular selection of the screen, a specific window, or the entire screen.

Control Panel overview 11

Client aggregation

Thin clients running HP ThinPro support up to four monitors, depending on the hardware model. If you need additional screen real estate, client aggregation allows up to four thin clients to be combined together making it possible to have a total of 16 monitors controlled by a single keyboard and mouse, without the need for additional hardware or software.

Assume that you have four thin clients, each with four monitors configured as a 2x2 array as shown below.

Client aggregation allows you to arrange the four thin clients on a 4x4 grid. The following illustration shows one possible arrangement.

When moving the mouse pointer off the right side of the thin client A monitors, for example, the pointer will appear on the left side of the thin client C monitors. Likewise, keyboard input will be redirected from thin client A to thin client C.

The following illustration shows another possible arrangement.

12 Chapter 4 Control Panel configurations

In this configuration, moving the mouse pointer off the right side of the thin client A monitors will cause it to appear on the upper 1/3 of the left side of the thin client D monitors. Similarly, moving the mouse pointer off the right side of the thin client B monitors will cause it to appear in the middle 1/3 of the left side of the thin client D monitors. Finally, moving the mouse pointer off the right side of the thin client C monitors will cause it to appear in the lower 1/3 of the left side of the thin client D monitors.

NOTE:

Desktop windows cannot span or be moved between thin clients. Typically, each thin client will create windows based on its connection to an associated remote computer, and there won’t be a need to move windows between thin clients.

The thin client physically connected to the keyboard and mouse is referred to as the aggregation server. The other thin clients are referred to as aggregation clients. When the mouse pointer is on one of the aggregation clients, the mouse and keyboard inputs (from the aggregation server) are encrypted and sent over the network to that aggregation client. The aggregation client decrypts the mouse and keyboard inputs and passes the inputs to the local desktop of the aggregation client.

Client aggregation is based on an open source software package called Synergy, with encryption provided by a package called stunnel.

Configuring client aggregation

Client aggregation configuration is a two-step process:

1.

Configuring the aggregation clients on page 13

2.

Configuring the aggregation server on page 14

Configuring the aggregation clients

Perform this procedure on each aggregation client:

1.

Select Peripherals > Client Aggregation in the Control Panel.

2.

Click Client.

3.

Type the server hostname or IP address of the aggregation server in the field.

4.

Click Apply.

Client aggregation 13

Configuring the aggregation server

To configure the aggregation server:

1.

Select Peripherals > Client Aggregation in the Control Panel.

2.

Click Server.

3.

The aggregation server is displayed in a blue box that contains its hostname. Click and drag the aggregation server to the desired location in the 4x4 grid.

4.

Click the location in the 4x4 grid where you want to place the first aggregation client, type its hostname or IP address, and then press Enter . The aggregation client is displayed in a green box.

5.

Add up to two additional aggregation clients in the 4x4 grid, if desired.

Placement of the aggregation server and the aggregation clients in the 4x4 grid can be modified at any time by clicking and dragging the corresponding box to a new location.

Once the aggregation clients and the aggregation server have been configured, they automatically attempt to establish encrypted communications with each other. Click Status to view the connection status between computers.

Display preferences

HP ThinPro allows you to create profiles for display preferences and apply different profiles to different monitors. A profile includes resolution, refresh rate, bit depth, and orientation.

To configure display profiles:

1.

Select Peripherals > Display Preferences in the Control Panel.

2.

Configure the options as necessary, and then click Apply.

NOTE:

The options may differ depending on the hardware model.

See the following tips about when customizing display profiles would be useful:

●

Some applications might require a specific resolution or bit depth to function properly.

●

Some applications might require the display to be rotated.

●

Using a 16-bit color depth should improve Citrix and RDP connection performance because less data has to be transmitted over the network or sent to the graphics chip.

●

AMD-based platforms (t520, t610, t620) offer only 32-bit color depth. The t505 and t510 offer either

16-bit or 32-bit color depth. In all cases, 32-bit color depth actually uses 24 bits.

●

An administrator might want to standardize on one display profile, even though there are many different monitors across the organization.

Configuring printers

To configure a printer:

1.

Select Peripherals > Printers in the Control Panel.

2.

In the Printing dialog, click Add .

3.

In the New Printer dialog, select the printer to configure, and then click Forward.

14 Chapter 4 Control Panel configurations

NOTE:

If you select a serial printer, be sure to input the correct settings on the right side of the dialog, or the printer might not function correctly.

4.

Select the make of the printer. If you are unsure, select the Generic (recommended) option, and then click Forward.

5.

Select the model of and driver for the printer, and then click Forward.

NOTE:

If you are unsure of the printer model or which driver to use, or if the model of your printer is not listed, click Back and try using the Generic (recommended) option for the make of the printer.

If using the Generic (recommended) make, be sure to select text-only (recommended) for the model and Generic text-only printer [en] (recommended) for the driver.

6.

Fill in optional information about the printer, such as its name and location.

NOTE:

HP recommends that you enter in the correct driver name into the Windows Driver box.

Without a driver to map to when connecting to a remote session, Windows might not use the correct driver and printing might not work. The driver must also be installed on the Windows server for the printer to work properly.

7.

Click Apply, and then print a test page if desired.

Repeat this process to configure additional printers if necessary.

TIP:

The most common problem is that the wrong driver is being used for the printer. To change the driver, right-click the printer and select Properties, and then change the make and model.

Redirecting USB devices

To redirect USB devices:

1.

Select Peripherals > USB Manager in the Control Panel.

2.

On the Protocol page, select a remote protocol.

If the setting is Local, you can also specify the options allow devices to be mounted and mount devices

read-only.

3.

On the Devices page, you can enable or disable redirection for individual devices if necessary.

4.

On the Classes page, you can select specific device classes to be redirected to remote sessions.

5.

When finished, click OK.

Network settings

Network settings can be configured using the Network Manager. To open the Network Manager:

▲

Select Setup > Network in the Control Panel.

See the following sections for more information about the different tabs in the Network Manager:

●

Wired network settings

●

Wireless network settings

●

DNS settings

●

IPSec rules

Redirecting USB devices 15

●

Configuring VPN settings

●

Configuring HP Velocity

Wired network settings

The following table describes the options available in the Wired tab of the Network Manager.

Option

Enable IPv6

Ethernet Speed

Connection Method

MTU

Security Settings

Description

Enables IPv6. IPv4 is used by default, and they cannot be used at the same time.

Lets you set the Ethernet Speed. If your switch or hub does not have a special requirement, leave this at the default setting of Automatic.

Lets you choose between Automatic and Static. If your network environment is using DHCP, then the

Automatic option should work without any further configurations needed.

If Static is selected, the Static Address Configuration settings will become available. Be sure to input these values according to whether you are using IPv4 or IPv6.

Allows you to enter the maximum transmission unit (in bytes).

Lets you set the authentication setting to one of the following:

●

None

●

802.1X-TTLS

●

802.1X-PEAP

●

802.1X-TLS

Note the following about TTLS and PEAP:

●

The Inner Authentication option should be set to whatever your server supports.

●

The CA Certificate setting should point to the server’s certificate on the local thin client.

●

The Username and Password are the user’s credentials.

Note the following about TLS:

●

The CA Certificate setting should point to the server’s certificate on the local thin client.

●

If your Private Key file is .p12 or .pfx, then the User Certificate setting can be left blank.

●

The Identity setting should be the username that corresponds to the user certificate.

●

The Private Key Password setting is the password of the user’s private key file.

Wireless network settings

The following table describes the options available in the Wireless tab of the Network Manager.

NOTE:

This tab is available only if the thin client has a wireless adapter.

Option

Scan AP

SSID

SSID Hidden

Enable IPv6

Description

Scans for available wireless networks.

Use this box to manually enter the SSID of the wireless network if it is not found by the scan.

Enable this option if the SSID of the wireless network is set to be hidden (not broadcasting).

Enables IPv6. IPv4 is used by default, and they cannot be used at the same time.

16 Chapter 4 Control Panel configurations

Option

Enable Power Management

Connection Method

Security Settings

Description

Enables the power management feature for the wireless adapter.

Lets you select between Automatic and Static. If your network environment is using DHCP, then the

Automatic option should work without any further configurations.

If Static is selected, the Static Address Configuration settings will become available. Be sure to input these values according to whether you are using IPv4 or IPv6.

Lets you set the authentication setting to one of the following:

●

None

●

WEP

●

WPA/WPA2-PSK

●

802.1X-TTLS

●

802.1X-PEAP

●

802.1X-TLS

●

EAP FAST

For WEP and WPA/WPA2-PSK, you just need to enter the network key and click OK.

For EAP-FAST, set Anonymous Identity, Username, Password, and Provisioning Method. You do not need to change the PAC file settings.

See Wired network settings on page 16

for more information about TTLS, PEAP, and TLS.

DNS settings

The following table describes the options available in the DNS tab of the Network Manager.

Option

Hostname

DNS Servers

Search Domains

HTTP Proxy

FTP Proxy

HTTPs Proxy

Description

This is generated automatically according to the MAC address of the thin client. You can alternatively set a custom hostname.

Use this box to set custom DNS server information.

Use this box to restrict the domains that are searched.

Use these boxes to set proxy server information using the following format: http://<ProxyServer>:<Port>

HP recommends using the http:// prefix for all three proxy settings because it is supported better.

NOTE:

The proxy settings are set to the http_proxy, ftp_proxy, and https_proxy environmental variables for the system.

IPSec rules

Use this tab to add, edit, and delete IPSec rules. An IPSec rule should be the same for each system that uses

IPSec to communicate.

When configuring an IPSec rule, use the General tab to set the rule’s information, addresses, and authentication method. The Source Address is the IP address of the thin client, and the Destination Address is the IP address of the system that the thin client is going to communicate with.

Network settings 17

NOTE:

Only the PSK and Certificate authentication types are supported. Kerberos authentication is not supported.

Use the Tunnel tab to configure settings for tunnel mode.

Use the Phase I and Phase II tabs to configure advanced security settings. The settings should be the same for all peer systems that communicate with each other.

NOTE:

An IPSec rule can also be used to communicate with a computer running Windows.

Configuring VPN settings

HP ThinPro supports two types of VPN:

●

Cisco

●

PPTP

Enable the Auto Start option to start the VPN automatically.

Note the following about creating a VPN using Cisco:

●

The Gateway is the gateway’s IP address or hostname.

●

The Group name and Group password are the IPSec ID and IPSec password.

●

The Domain setting is optional.

●

The User name and User password are the user credentials that have rights to create a VPN connection on the server side.

●

The Security Type should be set the same as it is on the server side.

Note the following about creating a VPN using PPTP:

●

The Gateway is the gateway’s IP address or hostname.

●

The NT Domain setting is optional.

●

The User name and User password are the user credentials that have rights to create a VPN connection on the server side.

Configuring HP Velocity

Use the HP Velocity tab to configure HP Velocity settings. Go to http://www.hp.com/go/velocity for more information about the HP Velocity modes.

Component Manager

The Component Manager lets you remove system components that are not going to be used in your environment, which might be desirable to reduce the image size. For example, if Citrix connections are never used in your environment, you might want to remove the Citrix component.

As components are removed, the new configuration can be tested before you apply the changes permanently.

You can also undo changes that were made, if the changes have not yet been applied permanently.

IMPORTANT:

After the new configuration is applied permanently, all snapshots are removed and a new factory snapshot is created. Removed components cannot be restored after this point.

To open the Component Manager:

▲

Select Management > Component Manager in the Control Panel.

18 Chapter 4 Control Panel configurations

Removing components

To remove components:

1.

In the Component Manager, select the desired components.

TIP:

To select multiple components, use Ctrl or Shift .

2.

Select Remove Component(s).

3.

If the confirmation dialog appears, select OK.

4.

After the components are removed, test the new configuration.

Undoing a change

You can undo each change, one at a time, if the changes have not yet been applied permanently. A restart of the thin client is required after each undo.

To undo a change made with the Component Manager:

1.

In the Component Manager, select Revert Last Change.

2.

Select Yes to restart the thin client.

Repeat this process for as many changes you want to undo.

IMPORTANT:

If you take a snapshot of the image while testing a new configuration, you cannot undo the changes via the Component Manager. Those changes can be undone only by restoring a previous snapshot via the Snapshots utility. However, this does not work if the changes have already been applied permanently, because that function deletes all existing snapshots. If changes have already been applied permanently, you must reinstall the operating system to restore most removed components. Some components (such as Citrix,

RDP, and VMware Horizon View) might be available as add-ons on the web and can be restored by reinstalling them.

Applying the changes permanently

To apply changes made with the Component Manager permanently:

IMPORTANT:

After the new configuration is applied permanently, all snapshots are removed and a new factory snapshot is created. Removed components cannot be restored after this point.

1.

In the Component Manager, select Apply Component Configuration.

2.

Select Yes.

Customization Center

To open the Customization Center:

▲

Select Setup > Customization Center in the Control Panel.

The button at the top of the Desktop page can be used to switch between the ThinPro and Smart Zero configurations. See

Comparison of ThinPro and Smart Zero on page 1 for more information about the

differences between the two configurations.

NOTE:

When switching from ThinPro to Smart Zero, if you have configured a single connection, that connection is used automatically as the Smart Zero connection. If you have configured multiple connections, you are prompted to select the connection to use.

Customization Center 19

The following table describes the rest of the options available on the Desktop page.

Option Description

Launch the Connection Manager at start up

Enable right-click menu

Authenticate USB Update

When enabled, the Connection Manager launches automatically at system startup.

Disable this option to disable the context menu that appears when you right-click the desktop

Allow user to switch to admin mode Disable this option to remove the Administrator/User Mode Switch option from the Control

Panel in User Mode.

Enable X host access control security When enabled, only the systems listed in the XHost Access Control List area are allowed to remotely control the thin client.

Enable USB Update Enables updates to be installed from a USB flash drive. See

USB updates on page 70

for more information.

Disable this option to allow standard users to install updates via USB.

Use the Connections and Applications pages to select which connection types and Control Panel applications are available in User Mode.

Use the Taskbar page to configure the taskbar.

HP ThinState

HP ThinState allows you to capture and deploy an HP ThinPro image or configuration (profile) to another thin client of compatible model and hardware.

Managing an HP ThinPro image

Capturing an HP ThinPro image to an FTP server

To capture an HP ThinPro image to an FTP server:

IMPORTANT:

The directory on the FTP server where you intend to save the captured image must already exist before initiating the capture.

1.

Select Management > ThinState in the Control Panel.

2.

Select the HP ThinPro image, and then click Next.

3.

Select make a copy of the HP ThinPro image, and then click Next.

4.

Select a FTP server, and then click Next.

5.

Enter the FTP server information in the fields.

NOTE:

The name of the image file is set by default to be the thin client’s hostname.

Select Compress the image if you want to compress the captured image.

NOTE:

The HP ThinPro image file is a simple disk dump. The uncompressed size is about 1 GB, and a compressed image without add-ons is approximately 500 MB.

6.

Click Finish.

When the image capture begins, all applications stop and a new window appears showing the progress.

If a problem occurs, click Details for information. The desktop reappears after the capture is complete.

20 Chapter 4 Control Panel configurations

Deploying an HP ThinPro image using FTP or HTTP

IMPORTANT:

If you abort a deployment, the previous image will not be restored and the contents of the thin client's flash drive will be corrupted.

To deploy an HP ThinPro image using FTP or HTTP:

1.

Select Management > ThinState in the Control Panel.

2.

Select the HP ThinPro image, and then click Next.

3.

Select restore an HP ThinPro image, and then click Next.

4.

Select either the FTP or HTTP protocol, and then enter the server information in the fields.

NOTE:

The Username and Password fields are not required if you are using the HTTP protocol.

5.

Select Retain HP ThinPro Configuration if you want to preserve all previously configured settings.

6.

Click Finish.

When the image deployment begins, all applications stop and a new window appears showing the progress. If a problem occurs, click Details for information. The desktop reappears after the deployment is complete.

NOTE:

An MD5sum check is done only if the MD5 file exists on the server.

Capturing an HP ThinPro image to a USB flash drive

To capture an HP ThinPro image to USB flash drive:

IMPORTANT:

Back up any data on the USB flash drive before you begin. HP ThinState automatically formats the flash drive to create a bootable USB flash drive. This process will erase all data currently on the flash drive.

1.

Select Management > ThinState in the Control Panel.

2.

Select the HP ThinPro image, and then click Next.

3.

Select make a copy of the HP ThinPro image, and then click Next.

4.

Select create a bootable USB flash drive, and then click Next.

The thin client restarts and then prompts you to enter a USB flash drive.

5.

Insert a USB flash drive into a USB port on the thin client.

6.

Select the USB flash drive, and then click Finish.

A new window displays the progress. If a problem occurs, click Details for information. The desktop reappears after the capture is complete.

Deploying an HP ThinPro image with a USB flash drive

To deploy an HP ThinPro image with a USB flash drive:

IMPORTANT:

If you abort a deployment, the previous image will not be restored and the contents of the thin client's flash drive will be corrupted. In this state, the thin client must be reimaged using a USB flash drive.

HP ThinState 21

1.

Turn off the target thin client.

2.

Insert the USB flash drive.

3.

Turn on the thin client.

NOTE:

The screen remains black for 10-15 seconds while the thin client detects and boots from the USB flash drive. If the thin client fails to boot from the USB flash drive, try unplugging all other USB devices and repeat the procedure.

Managing a ThinPro profile

A ThinPro profile contains the connections, settings, and customizations that were configured using the

Connection Manager and various Control Panel utilities. A profile is saved in a configuration file that is specific to the version of HP ThinPro in which it was created.

NOTE:

A profile can also be preconfigured and deployed using the Profile Editor and Automatic Update (see

Using the Profile Editor on page 62 and

HP Smart Client Services on page 58

for more information).

Saving a ThinPro profile to an FTP server

To save a ThinPro profile to an FTP server:

IMPORTANT:

The directory on the FTP server where you intend to save the profile must already exist before initiating the save.

1.

Select Management > ThinState in the Control Panel.

2.

Select the HP ThinPro configuration, and then click Next.

3.

Select save the configuration, and then click Next.

4.

Select on a FTP server, and then click Next.

5.

Enter the FTP server information in the fields.

6.

Click Finish.

Restoring a ThinPro profile using FTP or HTTP

To restore a ThinPro profile using FTP or HTTP:

1.

Select Management > ThinState in the Control Panel.

2.

Select the HP ThinPro configuration, and then click Next.

3.

Select restore a configuration, and then click Next.

4.

Select on a remote server, and then click Next.

5.

Select either the FTP or HTTP protocol, and then type the server information in the fields.

NOTE:

The Username and Password fields are not required if you are using the HTTP protocol.

6.

Click Finish.

22 Chapter 4 Control Panel configurations

Saving a ThinPro profile to a USB flash drive

To save a ThinPro profile to a USB flash drive:

1.

Insert a USB flash drive into a USB port on the thin client.

2.

Select Management > ThinState in the Control Panel.

3.

Select the HP ThinPro configuration, and then click Next.

4.

Select save the configuration, and then click Next.

5.

Select on a USB key, and then click Next.

6.

Select the USB flash drive.

7.

Click Browse.

8.

Navigate to the desired location on the USB flash drive and assign a file name to the profile.

9.

Click Save.

10.

Click Finish.

Restoring a ThinPro profile from a USB flash drive

To restore a ThinPro profile from a USB flash drive:

1.

Insert the USB flash drive containing the profile into a USB port on the target thin client.

2.

Select Management > ThinState in the Control Panel.

3.

Select the HP ThinPro configuration, and then click Next.

4.

Select restore a configuration, and then click Next.

5.

Select on a USB key, and then click Next.

6.

Select the USB key.

7.

Click Browse.

8.

Double-click the desired configuration file on the USB key.

9.

Click Finish.

VNC Shadowing

Virtual Network Computing (VNC) is a remote desktop program that allows you to see the desktop of a remote computer and control it with your local mouse and keyboard.

To access the VNC Shadow utility:

▲

Select Management > VNC Shadow in the Control Panel.

NOTE:

You must restart the thin client before any changes to the VNC Shadowing options will take effect.

The following table describes the options available in the VNC Shadow utility.

Option

Enable VNC Shadow

VNC Read Only

Description

Enables VNC Shadowing.

Makes the VNC session read-only.

VNC Shadowing 23

Option

VNC Use Password

VNC Notify User to Allow Refuse

VNC Show Timeout for Notification

User Notification Message

Refuse connections in default

Re-set VNC server right now

Description

Makes a password required when accessing the thin client using VNC.

Click Set Password to set the password.

Enables a notification dialog on the remote system that informs the remote user when someone is attempting to connect using VNC. The user can refuse either allow or refuse access.

Sets the length of time in seconds that the remote notification dialog is displayed.

Allows you to display a message in the notification dialog to the remote user.

If enabled, the VNC connection will be refused by default when the timer expires.

Resets the VNC server after applying the new settings.

Certificates

NOTE:

For more information about using certificates in Linux, go to http://www.openssl.org/docs/apps/ x509.html

.

Certificate Manager

To open the Certificate Manager:

▲

Select Advanced > Certificates in the Control Panel.

Use the Certificate Manager to manually install a certificate from a certificate authority (CA). This action copies the certificate to the user’s local certificate store (/usr/local/share/ca-certificates) and configures

OpenSSL to use the certificate for connection verification.

If desired, use the Profile Editor to attach the certificate to a profile, as described in Adding certificates to a

ThinPro profile on page 64

.

NOTE:

Generally, a self-signed certificate will work as long as it is valid according to specification and can be verified by OpenSSL.

SCEP Manager

To open the SCEP Manager:

▲

Select Advanced > SCEP Manager in the Control Panel.

Use the SCEP Manager when you need to enroll or renew client-side certificates from a CA.

During an enrollment or renewal, the SCEP Manager generates the thin client’s private key and certificate request, and then it sends the request to the CA on the SCEP server. When the CA issues the certificate, the certificate is returned and placed in the thin client’s certificate store. OpenSSL uses the certificate for connection verification.

NOTE:

Before enrollment, make sure that the SCEP server is configured properly.

Use the Identifying tab of the SCEP Manager to enter information about the user, if desired.

24 Chapter 4 Control Panel configurations

NOTE:

The Common Name is required and is the thin client’s Fully Qualified Domain Name (FQDN) by default. The other information is all optional. The Country or Region is entered as two letters, such as US for the United States and CN for China.

Use the Servers tab of the SCEP Manager to add SCEP servers and enroll or renew certificates.

TIP:

When entering a new SCEP server, save the server information first, and then use the Settings button to go back and do an enrollment.

DHCP options

To open the DHCP Option Manager:

▲

Select Advanced > DHCP Options in the Control Panel.

The DHCP Option Manager displays details of the DHCP options that are requested by the thin client.

TIP:

The drop-down list in the lower-left corner of the DHCP Option Manager allows you to filter which DHCP tags are displayed.

To direct the thin client to request or ignore specific DHCP options:

▲

Select or deselect the checkboxes in the Requested column.

If a pencil is shown in the DHCP Code column, the code number can be changed in case there is a conflict on your DHCP server over a particular code number.

To change a DHCP code:

▲

Double-click the DHCP code and type a new number.

NOTE:

Changeable DHCP codes can only be changed while that DHCP option is enabled in the

Requested column.

To learn more about how a DHCP option is used on the thin client and on the DHCP server:

▲

Click the icon in the Info column of that option.

DHCP options 25

5 Common connection configurations

This chapter discusses configurations that are common to all connection types.

●

Common connection settings

●

Kiosk mode

Common connection settings

The following table describes the settings that are available on the final page of the Connection Manager wizard for each connection type. These settings are connection-specific and apply to only the connection you are currently configuring.

Table 5-1 Common connection settings

Option Description

Fallback Connection

Auto start priority

Share credentials with screensaver

Auto reconnect

Wait for network before connecting

Show icon on desktop

Allow the user to launch this connection

Allow the user to edit this connection

Login dialog options

Specifies the fallback connection. If the connection fails to start, the fallback connection will attempt to start instead.

NOTE:

This option is not available for the VMware Horizon View connection type.

Determines the order that connections will auto-start. 0 means auto-start is disabled. The other values determine the startup order, with 1 being the highest priority.

Enables users to unlock the local screensaver using their credentials for that connection.

NOTE:

This option is only available for the Citrix, RDP, and VMware Horizon

View connection types.

If enabled, this connection will attempt to auto-reconnect if the connection is dropped.

NOTE:

Stopping a connection via the Connection Manager will prevent an auto-reconnection.

Disable this option if your connection doesn’t need the network to start or if you don’t want to wait for network to start the connection.

If enabled, a desktop icon will be created for this connection.

If enabled, this connection can be launched by a standard user.

If enabled, this connection can be modified by a standard user.

Enable or disable these options to configure the login dialog for the connection.

NOTE:

This option is only available for the Citrix, RDP, and VMware Horizon

View connection types.

The following options are available:

●

Show username field

●

Show password field

●

Show domain field

26 Chapter 5 Common connection configurations

Table 5-1 Common connection settings (continued)

Option Description

●

Show smartcard checkbox

●

Show ‘remember me’ checkbox

NOTE:

This option saves the user name and domain, but the password still needs to be entered each time.

●

Show ‘show password’ button

Kiosk mode

When a thin client is configured for kiosk mode, it performs an automatic login to the default connection on startup using predefined user credentials. If the connection is ever lost due to a logout, disconnect, or network failure, it reconnects automatically as soon as it can be restored.

TIP:

The remote host can be configured to auto-start applications on login, making the kiosk mode experience seamless.

The easiest way to configure a thin client for kiosk mode is to switch it to the Smart Zero configuration (see

Customization Center on page 19 ) and configure a connection. When this is done, the following settings are

set automatically:

●

The taskbar auto-hides.

●

The connection auto-starts.

●

The connection auto-reconnects.

●

The connection shares the user credentials with the local screensaver.

●

The desktop theme is set to that connection type’s default theme.

●

The USB redirection protocol in the USB Manager is set to that connection type’s protocol.

If you want to configure a thin client for kiosk mode in the ThinPro configuration (for example, if you want to use a connection type available only with ThinPro), you need to configure the following settings manually for the desired connection:

●

In the Customization Center, set the taskbar to Auto hide.

●

In the Connection Manager for the connection, do the following:

◦

Set the Auto start priority to 1.

◦

Enable Auto reconnect.

◦

Enable Share credentials with screensaver, if available.

◦

For a Web Browser connection only, select the Enable kiosk mode option.

●

In the USB Manager, set the proper USB redirection protocol, if necessary.

TIP:

When in kiosk mode, to minimize the connection and return to the local desktop, press Ctrl + Alt + End .

Kiosk mode 27

6 Citrix connections

●

Citrix Receiver features

●

Citrix connection support matrix

●

Citrix general settings

●

Citrix connection-specific settings

Citrix Receiver features

Citrix Receiver features include the following:

●

Window size and depth settings

●

Seamless window support

●

Sound quality settings

●

Static drive mapping

●

Dynamic drive mapping

●

USB redirection for XenDesktop and VDI-in-a-Box

NOTE:

Based on internal testing and validation, HP has found that a webcam connected through a

Citrix connection using basic USB Redirection performs poorly. HP does not recommend using this configuration and suggests that customers who require this function test using Citrix HDX technology to ensure satisfactory levels of performance.

●

Smart card virtual channel enablement

NOTE:

This feature is equivalent to a smart card login/authentication when using direct, non-PNAgent connections. With a PNAgent connection, smart card virtual channel enablement enables or disables the smart card virtual channel but does not provide for initial connection authentication. For a smart card authentication to XenApp and XenDesktop, use the provided Web Browser connection instead of the

Citrix connection and be sure to enable web access.

●

Printer mapping

●

Serial port mapping

●

HDX MediaStream (hardware-accelerated on most models)

NOTE:

See

HDX MediaStream on page 29 for more information.

●

HDX Flash Redirection (x86-only)

●

HDX Webcam Compression

NOTE:

HDX Webcam Compression works best on x86 units. HP has found the performance of webcams on ARM units to be poor and does not recommend using ARM units for webcam redirection.

●

HDX RealTime (MS Lync Optimization) (x86-only)

NOTE:

This is only available on Lync 2010.

28 Chapter 6 Citrix connections

●

Authentication to Citrix Access Gateway 5.0 and NetScaler Gateway 9.x/10.x using ICA Proxy mode

NOTE:

Only CA-issued SHA-1 based certificates are supported. Self-signed and SHA-2 based certificates are not supported.

●

HP True Graphics (see

HP True Graphics on page 30

)

HDX MediaStream

Whenever possible, HDX MediaStream leverages the processing power of the thin client to render the multimedia content. On the datacenter side, the compressed multimedia information is sent directly to the thin client in its native format. The experience will vary based on the processing power and multimedia capability of the thin client.

NOTE:

Certain video types might not perform well on low-end units. High-end units are recommended for

HDX media redirection.

Table 6-1 HDX MediaStream support matrix

Feature

Frame rate

Resolution

Video containers

Video codecs

Audio codecs

Support

●

24 fps

●

1080p

● 720p

●

WMV

●

AVI

●

MPG

●

MPEG

●

MOV

●

MP4

● WMV2

●

WMV3 / VC-1

● H.264 / AVC / MPEG-4 Part 10

●

MPEG-4 Part 2

● H.263

●

DivX

● Xvid

●

MPEG1

●

MP3

●

WMA

●

AAC

●

PCM

● mpeg-audio

●

MLAW / ULAW

Citrix Receiver features 29

HP True Graphics

HP True Graphics offloads rich multimedia content to the GPU, delivering high-frame-rate images and boosting efficiency.

HP True Graphics requires one of the following Citrix environments:

●

Citrix XenApp/XenDesktop 7 or newer

●

Citrix HDX 3D Pro (not running in Always Lossless mode)

HP True Graphics server-side requirements

XenApp/XenDesktop

The Citrix server must support sending session data in H.264 format. H.264 is enabled by default and is processed using the DeepCompressionV2 encoder, a CPU-based compression algorithm.

Only full desktops or non-seamless applications are currently accelerated when using HP True Graphics.

Hosted remote applications running in seamless windows do not see benefits from HP True Graphics. See HP

True Graphics client-side configuration on page 30 for information on how to force applications to run non-

seamlessly by configuring the TWI Mode setting on the thin client.

HDX 3D Pro

HDX 3D Pro desktops can use the H.264 format and benefit from using HP True Graphics, even if running older versions of XenDesktop. You might want to use HDX 3D Pro to offload the server-side H.264 encoding to the

GPU using the DeepCompression encoder. See Citrix documentation for more information.

NOTE:

HP True Graphics does not provide any performance enhancement if HDX 3D Pro is used with the visual quality set to Always Lossless, because then the graphical information is not sent to the thin client in

H.264 format.

Verifying server compression options

After connecting to a Citrix desktop, use the Citrix HDX Monitor to determine which encoder is being used for the session by examining the information under Graphics > Thinwire Advanced > Component_Encoder. If the value reads DeepCompressionV2Encoder or DeepCompressionEncoder, then the server is properly sending the data in a format that is accelerated by HP True Graphics.

NOTE:

If legacy graphics are being forced via a server policy, such as CompatibilityEncoder or

LegacyEncoder, the server is compressing graphics in a method that is compatible with older versions of Citrix clients and you will not experience enhanced performance from HP True Graphics.

HP True Graphics client-side configuration

Compression settings

H.264 compression must be enabled on the thin client for HP True Graphics to provide any benefits. To enable

H.264 compression on the thin client, select the Enable H264 Compression checkbox in the Xen Connection

General Settings Manager.

Some screen data, such as text, might be sent using methods other than H.264. In general, it is best to keep this feature enabled, but for troubleshooting or specific use cases, the following registry keys can be set to 0 to disable this feature:

● root/ConnectionType/xen/general/enableTextTracking

● root/ConnectionType/xen/general/enableSmallFrames

30 Chapter 6 Citrix connections

Window settings

Remote applications in seamless mode do not benefit from HP True Graphics. To force remote applications to be in windowed mode, set the TWI Mode option in the Xen Connection General Settings Manager to Force

Seamless Off.

Monitor layout and hardware limitations

Note the following limitations on monitor layout:

●

Currently, HP True Graphics is supported only for configurations using a maximum of two monitors at a

1920 x 1200 resolution each.

●

Rotated monitors might not display correctly.

●

Due to its default BIOS configuration, the HP t420 Thin Client uses HP True Graphics for one monitor only. See

Enabling HP True Graphics for multiple monitors on the HP t420 on page 31

for more information.

Enabling HP True Graphics for multiple monitors on the HP t420

To enable HP True Graphics for multiple monitors on the HP t420:

1.

Restart the thin client and press F10 to access the BIOS.

2.

Navigate to Advanced > Integrated Graphics.

3.

Set Integrated Graphics to Force.

4.

Set UMA Frame Buffer Size to 512M

After these steps are performed, the amount of memory available for graphics is expanded, and HP True

Graphics can be used for two monitors.

TIP:

These settings can also be configured via HPDM or via the BIOS tools included with HP ThinPro (see

BIOS settings tool on page 71

for more information).

Citrix connection support matrix

The following table describes the supported Citrix backends.

Table 6-2 Citrix connection support matrix

Access type

Direct (legacy)

PNAgent (legacy)

Web browser

StoreFront

XenApp

4.5 / 5 / 6 / 6.5

4.5 / 5 / 6 / 6.5 / 7.X

4.5 / 5 / 6 / 6.5 / 7.X

4.5 / 5 / 6 / 6.5 / 7.X

Backend

XenDesktop

4.5 / 5.5 / 5.6.5 / 7.X

4.5 / 5.5 / 5.6.5 / 7.X

4.5 / 5.5 / 5.6.5 / 7.X

VDI-in-a-Box

5.x

5.x

5.x

Citrix general settings

The following tables describe the settings available in the Xen Connection General Settings Manager. These settings are universal and apply to all Citrix connections.

Citrix connection support matrix 31

NOTE:

For information about how to locate these settings, see

Using the Connection Manager controls on page 6 .

Table 6-3 Xen Connection General Settings Manager > Options

Option Description

Enable HDX MediaStream

Enable Windows Alert Sound

ICA Acceleration (LAN Only)

Disable Info Box Before Connecting

Enables HDX MediaStream.

IMPORTANT:

For HDX MediaStream to be enabled, both this setting and the Enable MultiMedia setting must be enabled. Both settings can be found on the same page in the Xen Connection General Settings Manager.

Enable the Windows alert sound.

Enable ICA Acceleration.

Do not display the information box displayed before a connection is completed.

Use Asynchronous COM-port Polling Use asynchronous polling of the COM port.

Allow Smart Card Login for Direct and Web Connections Enables the usage of a smart card connected to the thin client for login authentication.

Enable Auto Reconnect

Enable Session Reliability

Enable automatic reconnection of dropped connections.

Enables the Citrix Session Reliability feature. See Citrix documentation for more information.

Enable MultiMedia Enables HDX MediaStream.

IMPORTANT:

For HDX MediaStream to be enabled, both this setting and the Enable HDX MediaStream setting must be enabled. Both settings can be found on the same page in the Xen Connection General Settings Manager.

NOTE:

This option might need to be disabled to support Lync RTME.

Enables clipboard redirection.

Enable Clipboard Redirection

Use Data Compression

Enable H264 Compression

Enable Middle Button Paste

User Agent String

Use data compression for this connection.

Enables H.264 compression. See Citrix documentation to determine if this method of data compression is best for your use cases.

Enables a middle mouse button click to perform a paste operation.

Specify a User Agent string to be used for requests sent to the Citrix server.

This option is useful for a NetScaler configuration.

HDX Flash Redirection

HDX Flash Server Side Content Fetch

Sound

SpeedScreen

Local Text Echo

Encryption Level

Enables HDX Flash redirection to play flash content locally.

Allows the server to fetch the flash content for redirection.

Sets the sound quality or disables sound entirely.

Controls SpeedScreen latency reduction. The recommended setting is Auto.

Controls keyboard latency reduction. The recommended setting is Auto.

Specifies the encryption level of an ICA session.

32 Chapter 6 Citrix connections

Table 6-4 Xen Connection General Settings Manager > Local Resources

Option Description

Printers

Webcam/Audio-Input

USB Drive Mapping and Redirection

Controls how local printer redirection is handled.

Controls how local webcam and audio input redirection is handled.

Controls whether or not the following options are enabled:

NOTE:

The options below can be enabled and disabled individually when

USB Drive Mapping and Redirection is enabled.

●

USB Redirection—Enables USB redirection.

●

Dynamic Drive Mapping—Enables dynamic drive mapping.

●

Static Drive Mapping (Legacy)—Enables static drive mapping, which allows you to specify drive mappings to local paths.

Table 6-5 Xen Connection General Settings Manager > Window

Option Description

TWI Mode

Default Window Size

Default Window Colors

Default 256 Color Mapping

Show the Virtual Desktop on all monitors

Left Monitor

Right Monitor

Top Monitor

Bottom Monitor

Lets you display a single seamless window on the local ThinPro desktop as if it were a native application.

When TWI Mode is set to Force Seamless Off, this controls the default window size.

Sets the default color depth.

Sets the method for color mapping if Default Window Colors is set to 256.

When enabled, the virtual desktop will be displayed across all monitors.

When Show the Virtual Desktop on all monitors is disabled, these fields let you specify how the virtual desktop is displayed across specific monitors.

Table 6-6 Xen Connection General Settings Manager > Firewall

Option Description

Proxy Type

Proxy Address

Proxy Port

Username

Password

Use Alternate Address for Firewall Connection

Specifies the proxy type.

The IP address of the proxy server.

The port for connection to the proxy server.

The username to use for connection to the proxy server.

The password to use for connection to the proxy server.

The Citrix ICA Client will request the alternate address defined for the server when contacting servers inside the firewall. The alternate address must be specified for each server in a server farm.

Citrix general settings 33

Table 6-7 Xen Connection General Settings Manager > Keyboard Shortcuts

Option Description

Enable UseLocalIM

Use EUKS Number

Handling of keyboard shortcuts

Stop Direct key handling

<List of keyboard shortcuts>

Uses the local input method to interpret keyboard input. This is supported only for European languages.

Controls the usage of Extended Unicode Keyboard Support (EUKS) on

Windows servers. Valid options are described below:

●

0—EUKS is not used.

● 1—EUKS is used as a fallback.

●

2—EUKS is used whenever possible.

Specifies how keyboard shortcuts should be handled. The following settings are available:

●

Translated—Keyboard shortcuts apply to the local desktop (client side)

●

Direct in full screen desktops only—Keyboard shortcuts apply to the remote desktop (server side), but only for a non-seamless ICA session in full screen mode

●

Direct—Keyboard shortcuts apply to the remote desktop (server side) for both seamless and non-seamless ICA sessions when their windows have the keyboard focus

Specifies the key combination that disables Direct handling of keyboard shortcuts.

Lets you add keyboard shortcuts to be handled.

Table 6-8 Xen Connection General Settings Manager > Session

Option Description

Auto Logout Delay Before App Launch

Auto Logout Delay After App Close

When using a Citrix server with multiple published resources, this specifies the number of seconds to allow a user to launch an app after login before the system automatically logs out and returns to the initial login screen.

When using a Citrix server with multiple published resources, this specifies the number of seconds between the closing of the last Xen published resource and when the user is automatically logged out and returned to the initial login screen.

Server Check Timeout To perform a basic connectivity check to the selected server and port, set this option to a value other than the default –1.

TIP:

Setting any of these values to less than 0 will disable auto-logout.

NOTE:

Citrix processing delays might increase the auto-logout time.

Citrix connection-specific settings

The following table describes the settings available in the Citrix Connection Manager. These settings are connection-specific and apply to only the Citrix connection you are currently configuring.

NOTE:

For information about how to locate these settings, see

Using the Connection Manager controls on page 6 .

34 Chapter 6 Citrix connections

Table 6-9 Citrix Connection Manager > Configuration

Option Description

Name

Service URL

Connection Mode

Auto Start Resource

Auto Start Desktop

Auto Start Single Application

Show applications on desktop

Show applications on taskbar

Auto Reconnect Applications on Login

The connection name.

The Citrix server hostname or IP address. If you are configuring a connection to a server on an HTTPS site, enter the FQDN for the site and the local root certificate in the Citrix certificate store.

Sets the connection mode to one of the following:

●

PNAgent

●

StoreFront

●

StoreFront-SmartCard

●

Direct

If set to PNAgent, StoreFront, or Direct, you can set the username, password, and domain.

If set to StoreFront-SmartCard, you can set the security module type and the action to perform if the smart card is unplugged.

Specifies the name of a resource to start automatically upon connection.

With this option selected, a desktop-type resource will start automatically upon connection, if available.

With this option selected, and if there is a single published resource, that resource will start automatically upon connection.

With this option selected, remote resources from the connection will be shown on the local ThinPro desktop.

With this option selected, remote resources from the connection will be shown on the local ThinPro taskbar.

With this option selected, resources that were open when the user last logged out will be reopened when they log in again.

TIP:

If not using the Citrix SmoothRoaming feature, disable this option to increase your connection speed.

Table 6-10 Citrix Connection Manager > Security

Ignore Certificate Check

Force HTTPS Connection

If enabled, certificates are not checked and the connection is insecure.

If enabled, the connection is forced to use the HTTPS protocol, helping to ensure a secure connection.

NOTE:

See Common connection settings on page 26 for information about the settings available on the final

page of the Citrix Connection Manager.

Citrix connection-specific settings 35

7 RDP connections

●

RDP features

●

RDP general settings

●

RDP connection-specific settings

●

Using RemoteFX with RDP

●

Using multi-monitor sessions with RDP

●

Using multimedia redirection with RDP

●

Using device redirection with RDP

RDP features

The RDP client is based on FreeRDP 1.1 and meets the following requirements for RDP 7.1:

●

Hardware-accelerated RemoteFX

●

MMR supported when connecting to Windows hosts with the Desktop Experience feature enabled

(Windows 7 or Windows Server 2008 R2)

●

USBR supported when connecting to Windows 7 Remote Desktop Virtual Hosts

●

Bidirectional audio

●

True multi-monitor support

●

Gateway and brokered connection support

RDP general settings

The following table describes the settings available in the RDP Connection General Settings Manager. These settings are universal and apply to all RDP connections.

NOTE:

For information about how to locate these settings, see

Using the Connection Manager controls on page 6 .

Table 7-1 RDP Connection General Settings Manager

Option

Send hostname as

Enable Multimedia Redirection

Description

Specifies whether to send the thin client's hostname or MAC address as the hostname specified to the remote system.

Enables multimedia redirection.

RDP connection-specific settings

The following tables describe the settings available in the RDP Connection Manager. These settings are connection-specific and apply to only the RDP connection you are currently configuring.

36 Chapter 7 RDP connections

NOTE:

For information about how to locate these settings, see Using the Connection Manager controls on page 6

.

Table 7-2 RDP Connection Manager > Network

Option Description

Name

Address

Username

Password

Domain

Allow Smartcard Login

Enable RD Gateway

Server Probe

A custom name for this connection.

The IP address or server name for this connection, or the RD Web Access feed URL. If required, the port can be appended to the server after a colon (by default, the port is

3389 for a direct RDP connection).

NOTE:

The RD Web Access feed URL must begin with https://. By default, this is added automatically as specified by the rdWebFeedUrlPattern registry key, which defines the pattern of the URL.

The username for this connection.

The password for this connection.

The domain name for this connection (optional).

Enables smart card authentication.

Enables additional RD Gateway options, such as the gateway address, port, and credentials.

Launches the Server Probe, which can be used to determine which RDP features are supported by your RDP server.

Table 7-3 RDP Connection Manager > Service

Option Description

Service Sets the RDP service to one of the following:

●

Remote Computer—When using this service, a direct RDP connection is created to a remote computer. A remote application or alternate shell can optionally be started upon connection. The following additional options are available for a

Remote Computer service:

◦

If Mode is set to Remote Application, the Application field specifies the path of the application to run.

◦

TIP:

If using RDP Seamless Windows mode, type the path of seamlessrdpshell.exe on your server, followed by a space and then the path of the application to run. See the following example: c:\seamless\seamlessrdpshell.exe c:\Program Files

\Microsoft\Word.exe

If Mode is set to Alternate Shell, the Command field specifies the command that executes the application to run in the alternate shell. For example, to run

Microsoft Word, type Word.exe.

If Mode is set to Alternate Shell, the Directory field specifies the server’s working directory path for the application’s program files. For example, the working directory for Microsoft Word is C:\Program Files

\Microsoft.

●

RD Web Access—When using this service, a list of RemoteApp resources is retrieved from the server and presented to the user, and the actual RDP connection is started when a resource is selected. The following additional options are available for RD Web Access:

RDP connection-specific settings 37

Table 7-3 RDP Connection Manager > Service

Option Description

◦

◦

Keep resource selection window open—With this option selected, users can open multiple resources simultaneously from the resource selection window.

Auto-start single resource—With this option selected, and if there is a single published resource, that resource will start automatically upon connection.

◦

Resource filter and Web Feed Browser—These can be used to limit the remote resources that will be made available to the user in the resource selection window.

NOTE:

An advantage of using RD Web Access is that it handles the details of brokered connections and the Load Balance URL automatically.

Table 7-4 RDP Connection Manager > Window

Option Description

Hide Window Decoration

Window Size

Percentage Size

Fixed Size

This setting makes sure that screen elements such as the menu bar, minimize and close options, and borders of the window pane are not displayed.

Sets the window size to full, fixed, or percent.

If Window Size is set to percent, this option sets the percentage of the screen that a desktop window occupies.

NOTE:

The resulting sizes might be rounded.

NOTE:

RemoteFX supports only a fixed list of resolutions.

If Window Size is set to fixed, this option sets the width and height in pixels that the desktop window occupies.

Table 7-5 RDP Connection Manager > Options

Option Description

Enable motion events

Enable data compression

Enable deprecated RDP encryption

Enable offscreen cache

Attach to admin console

Cross-session copy/paste

Enable buffering of RDP6 primitives

Certificate Verification Policy

If enabled, mouse motions are continuously relayed to the RDP server.

Enables bulk compression of data between the RDP server and RDP client.

Enables last-generation RDP encryption when NLA is not available.

If enabled, off-screen memory is used to cache bitmaps.

Attaches the connection to the administrator console port.

If enabled, copy and paste are enabled between different RDP sessions.

If enabled, non-RemoteFX graphics performance is increased at the cost of less frequent screen updates.

Select one of the following:

●

Accept all RDP server certificates

●

Use remembered hosts; warn if unknown or invalid certificate

●

Skip remembered hosts; warn if unknown or invalid certificate

●

Connect only to pre-approved RDP servers

38 Chapter 7 RDP connections

Table 7-5 RDP Connection Manager > Options (continued)

Option Description

Hostname to send

Load Balance Info

Normally, the thin client's hostname is used for Client Access Licenses. This field allows a different value to be sent.

TIP:

Click the ? icon next to this option for more information.

Use this option with a brokered RDP connection.

TIP:

Click the ? icon next to this option for more information.

Table 7-6 RDP Connection Manager > Local Resources

Option Description

Audio Devices

Printers

Serial/Parallel Ports

USB Storage

Local Partitions

Other USB Devices

Determines whether audio devices are redirected by high-level RDP audio redirection, low-level USB redirection, or disabled for this connection.

Determines whether printers are redirected by high-level printer redirection (which requires them to be set up via the Printers utility in the Control Panel), low-level USB redirection, or disabled for this connection.

Determines whether serial and parallel ports are redirected or disabled for this connection.

Determines whether USB storage devices such as flash drives and optical drives are redirected by high-level storage redirection, low-level USB redirection, or disabled for this connection.

Determines whether local partitions of the thin client's flash drive are redirected or disabled for this connection.

Determines whether other classes of USB devices (such as webcams and tablets) are redirected by low-level USB redirection or disabled for this connection.

Table 7-7 RDP Connection Manager > Experience

Option Description

Choose your connection speed to optimize performance

End-to-End Connection Health

Monitoring

Selecting a connection speed (LAN, Broadband, or Modem) will enable or disable the following options to optimize performance:

●

Desktop background

●

Font smoothing

●

Desktop composition

●

Show contents of window while dragging

●

Menu and window animation

●

Themes

Selecting Client Preferred Settings allows the RDP client to choose which options to use to provide the best RDP experience.

You can also select your own custom combination of options.

Select to enable the timeout options.

RDP connection-specific settings 39

Table 7-7 RDP Connection Manager > Experience (continued)

Option Description

Warning Timeout

Recovery Timeout

Error Timeout

Specifies the amount of time in seconds after receiving the last network traffic from the server before the user is warned of a lost connection. This function can be disabled by clearing the option or setting the time to zero.

With the Show Warning Dialog option selected, a warning dialog will be displayed when this timeout is reached. Otherwise, the warning is written to the connection log only.

TIP:

HP recommends increasing the timeout value for networks that experience frequent busy periods or momentary outages.

Specifies the amount of time in seconds after receiving the last network traffic from the server that the RDP client waits for the connection to recover without taking any special action. At the end of this period, the RDP client attempts a quick reconnection with the session.

Specifies the amount of time in seconds after receiving the last network traffic from the server that the RDP client waits before stopping attempts to reconnect with that server.

TIP:

Click the ? icon next to this field for more information.

Table 7-8 RDP Connection Manager > Diagnostics

Option Description

Show Connection Health Graph

USB Redirection Analysis

With this option enabled, a two-dimensional graph of response time from the RDP server will be shown when the connection is started.

TIP:

Click the ? icon next to this option for more information.

This feature determines and displays the current redirection method for each redirected

USB device.

TIP:

Click the ? icon next to this option for more information.

NOTE:

See

Common connection settings on page 26

for information about the settings available on the final page of the RDP Connection Manager.

Using RemoteFX with RDP

RemoteFX (RFX) is an advanced graphics display protocol that is designed to replace the graphics component of the traditional RDP protocol. It uses the hardware acceleration capabilities of the server GPU to encode the screen contents via the RFX codec and send screen updates to the RDP client. RFX uses advanced pipelining technologies and adaptive graphics to make sure that it delivers the best possible experience based on content type, CPU and network bandwidth availability, and rendering speed.

RFX is enabled by default. The administrator or user does not have to change any settings to enable it. The

RDP client negotiates with any RDP server it contacts, and if RFX is available, it will be used.

To disable RFX, set the following registry key to 0: root/ConnectionType/freerdp/connections/<UUID>/remoteFx

TIP:

For simplified management, HP recommends that you enable or disable RFX on the remote host.

40 Chapter 7 RDP connections

NOTE:

Some Windows RDP servers will not send RemoteFX content to thin clients enabled for RDP 7.1 without a change to Group Policy. Check the setting of the following policy:

Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components >

Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Enable

RemoteFX encoding for RemoteFX clients designed for Windows Server 2008 R2 SP1

In addition, Windows Server 2012 and Windows Server 2012 R2 require the following setting to be set to 32-

bit:

Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components >

Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Limit maximum color depth

Using multi-monitor sessions with RDP

True multi-monitor support does not require special configuration. The RDP client automatically identifies which monitor is specified as the primary monitor in the local settings and places the taskbar and desktop icons on that monitor. When a window is maximized within the remote session, the window will only cover the monitor it was maximized on.

Display preferences and monitor resolutions can be viewed but not modified within the remote session. To modify the session resolution, log out of the session and change the resolution on the local thin client.

By default, all RDP sessions will be full-screen and cover all monitors to enhance the virtualization experience. Additional window options are available in the RDP Connection Manager.

NOTE:

Remote Desktop Virtualization Host (RDVH) sessions with graphics card support might only support certain resolutions and counts of monitors. The limits are specified when the RemoteFX virtual graphics device is configured for the RDVH virtual machine.

Using multimedia redirection with RDP

Multimedia redirection (MMR) is a technology that integrates with Windows Media Player on the remote host and streams the encoded media to the RDP client instead of playing it on the remote host and re-encoding it via RDP. This technology reduces the server load and network traffic, and greatly improves the multimedia experience, supporting 24 fps playback of 1080p videos with automatic audio syncing. MMR is enabled by default. The RDP client will negotiate with any RDP server it contacts, and if MMR is available, it will be used.

MMR also uses an advanced codec detection scheme that identifies whether the thin client supports the codec being requested by the remote host before attempting to redirect it. The result is that only supported codecs will be redirected and all unsupported codecs fall back to server-side rendering.

To disable MMR on the thin client for all RDP connections, set the following registry key to 0: root/ConnectionType/freerdp/general/enableMMR

Because RemoteFX already delivers acceptable multimedia performance, you can disable MMR with RFX by setting the following registry key to 1: root/ConnectionType/freerdp/connections/<UUID>/disableMMRwithRFX

TIP:

For simplified management, HP recommends that MMR be enabled or disabled on the remote host.

Using multi-monitor sessions with RDP 41

Using device redirection with RDP

Device redirection makes sure that when a user plugs a device into the thin client, the device is automatically detected and accessible in the remote session. RDP supports redirection of many different types of devices.

Using USB redirection with RDP

USB redirection works by transmitting low-level USB protocol calls over the network to the remote host. Any

USB device plugged into the local host appears within the remote host as a native USB device, as if it were plugged in locally. Standard Windows drivers support the device in the remote session, and all device types are supported without requiring additional drivers on the thin client.

Not all devices default to USB redirection. For example, USB keyboards, mice, and other input devices usually are not set to be redirected, as the remote session expects input to come from the thin client. Some devices such as mass storage, printers, and audio devices might use additional options for redirection.

Note the following additional information about USB redirection with RDP:

●

The server must support USB redirection for it to be available to the thin client. General-purpose USB redirection is supported with RDVH servers with RemoteFX, Windows 8, and Windows Server 2012.

●

The protocol in the USB Manager in the Control Panel must be set to RDP.

●

For RDP connections, the controls in the USB Manager determine if a USB device is redirected. The settings for the individual connection determine how a USB device is redirected.

Using mass storage redirection with RDP

By default, the RDP session redirects all mass storage devices to the remote host using high-level drive redirection. When a device such as a USB flash drive, USB DVD-ROM drive, or USB external HDD is plugged into the thin client, the thin client detects and mounts the drive on the local file system. RDP then detects a mounted drive and redirects it to the remote host. Within the remote host, it will appear as a new disk drive in

Windows Explorer, with the name <device label> on <client hostname>; for example,

Bill_USB on HP04ab598100ff.

There are three restrictions to this type of redirection.

●

The device will not appear in the taskbar on the remote host with an icon to eject the device. Because of this, make sure to give the device a sufficient amount of time to sync data after a copy before removing the device to be sure that the device does not corrupt. Typically, less than one second is required after the file copy dialog finishes, but up to 10 seconds might be required depending on the device write speed and network latency.

●

Only file systems supported by the thin client will be mounted. The supported file systems are FAT32,

NTFS, ISO9660 (CD-ROMs), UDF (DVD-ROMs), and ext3.

●

The device will be treated as a directory; common drive tasks like formatting and modification of the disk label will not be available.

USB redirection of storage devices can be disabled in an individual connection's settings. If desired, you can disable mass storage redirection altogether. To do this, turn off USB redirection, and then change the registry keys as described in the following table.

42 Chapter 7 RDP connections

Table 7-9 Disabling USB redirection

Registry entry

root/USB/root/holdProtocolStatic

Value to set

1 root/USB/root/protocol local

Description

Makes sure that the USBR type will not be automatically changed when a connection is set or unset

Makes sure that the RDP connection does not attempt to redirect any devices to the remote session

To completely disable local mounting of USB mass storage devices or to disable the redirection of USB mass storage devices but still allow other devices to redirect, in the thin client file system, delete the udev rule /etc/udev/rules.d/010_usbdrive.rules.

Using printer redirection with RDP

By default, RDP has two methods of printer redirection enabled:

●

USB redirection—Any USB printer plugged into the device will show up as a local printer in the remote session. The standard printer installation process must happen in the remote session if the printer is not already installed on that remote host. There are no settings to manage locally.

●

High-level redirection—If either USB redirection is unavailable on the remote host or the printer is a parallel or serial printer, use high-level redirection. Configure the printer to use a local printer spooler, and the RDP client automatically sets up a remote printer that sends print spooling commands through a virtual channel from the remote host to the thin client.

This method requires both that the printer be configured on the thin client and a Windows driver be specified on the thin client because the RDP client needs to specify to the remote host which driver to use for the remote printer. This Windows driver must match the driver that the printer would use when locally attached to a Windows operating system. This information is usually found under the Model in the printer properties.

NOTE:

See Configuring a serial or parallel printer on page 65

for more information.

Using audio redirection with RDP

By default, high-level audio redirection will redirect audio from the remote host to the thin client. Basic voice control might need to be set up, and RDP 7.1 contains a number of advanced audio redirection features that might require additional configuration.

See the following notes about using audio redirection with RDP:

●

RDP delivers the highest quality audio as the network bandwidth allows. RDP reduces audio quality to play on low-bandwidth connections.

●

No native audio or video syncing mechanisms are available in standard RDP. Longer videos might not sync with audio. MMR or RemoteFX can resolve this issue.

●

HP recommends high-level audio redirection, but USB redirection of audio devices is possible if additional functionality is present, such as a digital volume control. Only high-level redirection is available for analog devices.

●

Microphone redirection is enabled by default. The default microphone volume might need to be adjusted on the thin client. Older Windows RDP servers must have their settings modified to enable audio input.

●

Both the local and remote volume settings will affect the final volume. HP recommends setting the local volume to a maximum and adjusting the volume within the remote host.

Using device redirection with RDP 43

Using smart card redirection with RDP

By default, smart cards will be redirected using high-level redirection, allowing them to be used to log in to the session and other remote applications.

To enable smart card login for an RDP connection:

▲

Select Allow Smartcard Login in the RDP Connection Manager.

This will allow the user to connect without first specifying credentials. The RDP client will start the RDP session, and the user will be prompted to authenticate by smart card.

This technology requires drivers for the smart card reader driver to be installed on the thin client. By default, the CCID and Gemalto drivers are installed, which adds support for the majority of smart card readers available. Additional drivers can be installed by adding them to /usr/lib/pkcs11/.

NOTE:

When smart card login is enabled, Network Level Authentication is not supported and is automatically disabled.

44 Chapter 7 RDP connections

8 VMware Horizon View connections

●

VMware Horizon View settings

●

Using multi-monitor sessions with VMware Horizon View

●

Using keyboard shortcuts with VMware Horizon View

●

Using Multimedia Redirection with VMware Horizon View

●

Using device redirection with VMware Horizon View

●

Changing the VMware Horizon View protocol type

●

VMware Horizon View HTTPS and certificate management requirements

VMware Horizon View settings

The following tables describe the settings available in the VMware Horizon View Connection Manager. These settings are connection-specific and apply to only the VMware Horizon View connection you are currently configuring.

NOTE:

For information about how to locate these settings, see Using the Connection Manager controls on page 6

.

Table 8-1 VMware Horizon View Connection Manager > Network

Option Description

Name

Server

Username

Password

Domain

Desktop

Enter a name for this connection.

Enter the hostname or IP address of a VMware Horizon View server.

Enter the username to use for the connection.

Enter the password to use for the connection.

Enter the domain to use for the connection.

Specify the optional desktop pool to automatically connect to.

Table 8-2 VMware Horizon View Connection Manager > General

Option Description

Automatic login

Allow Smartcard login

Don’t start application maximized

Application Size

When enabled, the user is automatically logged in when the connection is established.

NOTE:

HP recommends enabling this option.

Enables smart card login.

NOTE:

For more information on smart cards, see Using smart card redirection with

VMware Horizon View on page 49

.

If enabled, applications do not start in maximized windows.

Sets the application window size. You can select All Monitors, Full Screen, Large

Window, or Small Window.

VMware Horizon View settings 45

Table 8-2 VMware Horizon View Connection Manager > General (continued)

Option Description

Desktop Size

Command Line Arguments

Sets the desktop window size. You can select All Monitors, Full Screen, Large Window, or Small Window.

Enter any desired command line arguments to be used for the connection.

For more help on using advanced command line arguments, do one of the following:

● On the command line, enter vmware-view--help.

●

See the documentation for the VMware Horizon View client for Linux provided by

VMware at http://www.vmware.com

.

Table 8-3 VMware Horizon View Connection Manager > Security

Option Description

Close After Disconnect

Hide top Menu bar

Makes the VMware Horizon View client close automatically after users log out of their desktops or the session terminates with an error.

This option is a security feature designed so that a user does not need to take an additional step to fully log out after they are finished with their desktop session.

This option is enabled by default for security purposes but can be disabled if users find that they are often switching to a new desktop pool after logging out of a session and do not want to fully log in again.

Makes the top menu bar invisible for users.

This option enabled by default. Disable it if users prefer to access options for window size or desktop pool selection in a VMware Horizon View session.

If enabled, standard users cannot change the server address.

Prevent users from changing server address

Connection Security Level Use the Connection Security Level to adjust the security level that the VMware Horizon

View client uses when connecting to the server.

NOTE:

For more information, see

VMware Horizon View HTTPS and certificate management requirements on page 50 for details on how connection security levels

behave.

Table 8-4 VMware Horizon View Connection Manager > RDP Options

Option Description

Enable motion events

Enable data compression

Enable deprecated RDP encryption

Enable offscreen cache

Attach to admin console

Enable buffering of RDP6 primitives

Certificate Verification Policy

Enables motion events for this connection.

Uses data compression for this connection.

Enables encryption for this connection.

If enabled, off-screen memory is used to cache bitmaps.

Attaches the connection to the administrator console port.

If enabled, non-RemoteFX graphics performance is increased at the cost of less frequent screen updates.

Select one of the following:

●

Accept all RDP server certificates

46 Chapter 8 VMware Horizon View connections

Table 8-4 VMware Horizon View Connection Manager > RDP Options (continued)

Option

Hostname to send

Load Balance Info

Remote computer sound

Enable port mapping

Enable printer mapping

Shared folders

Description

●

Use remembered hosts; warn if unknown or invalid certificate

●

Skip remembered hosts; warn if unknown or invalid certificate

●

Connect only to pre-approved RDP servers

Normally, the thin client's hostname is used for Client Access Licenses. This field allows a different value to be sent.

TIP:

Click the ? icon next to this option for more information.

Use this option with a brokered RDP connection.

TIP:

Click the ? icon next to this option for more information.

Specifies where the remote computer’s sound should be played (remotely or locally) or if it should not be played at all.

Maps the thin client's serial and parallel ports to the remote session.

Maps the local print queue to the remote session. Use this option if either USB redirection is unavailable on the remote host or the printer is a parallel or serial printer.

Configure the printer to use a local printer spooler, and the VMware Horizon View client automatically sets up a remote printer that sends print spooling commands through a virtual channel from the remote host to the thin client.

This method requires both that the printer be configured on the thin client and a

Windows driver be specified on the thin client because the VMware Horizon View client needs to specify to the remote host which driver to use for the remote printer. This

Windows driver must match the driver that the printer would use when locally attached to a Windows operating system. This information is usually found under the Model in the printer properties.

Add, Remove, or Edit shared folders.

Table 8-5 VMware Horizon View Connection Manager > RDP Experience

Option Description

Enable MMR

Choose your connection speed to optimize performance

Enables multimedia redirection.

Selecting a connection speed (LAN, Broadband, or Modem) will enable or disable the following options to optimize performance:

●

Desktop background

●

Font smoothing

●

Desktop composition

●

Show contents of window while dragging

●

Menu and window animation

●

Themes

Selecting Client Preferred Settings will allow the VMware Horizon View client to choose which options to use.

You can also select your own custom combination of options.

VMware Horizon View settings 47

NOTE:

See

Common connection settings on page 26

for information about the settings available on the final page of the VMware Horizon View Connection Manager.

Using multi-monitor sessions with VMware Horizon View

VMware Horizon View supports multi-monitor sessions. To enhance the virtualization experience, the default

VMware Horizon View sessions use full-screen and span all monitors. To choose a different window size, select Full Screen – All Monitors under the protocol type of the desktop pool for the connection and then choose another option from the window size list. The next time you connect to a session the window will open in the selected size.

Using keyboard shortcuts with VMware Horizon View

Windows keyboard shortcuts

To help administer Windows systems, VMware Horizon View supports Windows keyboard shortcuts. For example, when Ctrl + Alt + Del is used, VMware Horizon View displays a message that provides the following options:

●

Send a Ctrl+Alt+Del command.

●

Disconnect the session—Use this when you have no other way of ending the session.

Windows keyboard shortcuts will be forwarded to the remote desktop session. The result is that local keyboard shortcuts, such as Ctrl + Alt + Tab and Ctrl + Alt + F4 , will not function while inside the remote session.

TIP:

To be able to switch sessions, disable the Hide top Menu bar option in the VMware Horizon View

Connection Manager or via the registry key root/ConnectionType/view/connections/<UUID>/ hideMenuBar.

Media keys

VMware Horizon View uses media keys to control options such as volume, play/pause, and mute during a remote desktop session. This supports multimedia programs such as Windows Media Player.

Using Multimedia Redirection with VMware Horizon View

VMware Horizon View connections support MMR functionality when used with the Microsoft RDP protocol.

For more information, see

Using multimedia redirection with RDP on page 41 .

Using device redirection with VMware Horizon View

Using USB redirection with VMware Horizon View

To enable USBR for VMware Horizon View connections, select VMware Horizon View as the remote protocol in the USB Manager.

For more information on USBR, including device- and class-specific redirection, see

Using USB redirection with

RDP on page 42 .

Using mass storage redirection with VMware Horizon View

You must use the RDP connection protocol to use mass storage redirection with a VMware Horizon View connection.

48 Chapter 8 VMware Horizon View connections

To perform drive redirection of a USB drive or internal SATA drive:

▲

Add - xfreerdpoptions=’/drive:$foldname,shared folder path, share device’ in the command-line arguments option.

For example, –xfreerdpoptions=’/drive:myfolder,/home/user,/dev/sda2' shares the / home/user on the /dev/sda2 drive as myfolder in a VMware Horizon View connection.

For more details, see

Using mass storage redirection with RDP on page 42

.

Using printer redirection with VMware Horizon View

For connections made with the PCoIP protocol on x86 units, printers can be shared using VMware Horizon

View’s high-level printer redirection or USBR. PCoIP connections on ARM units support only USBR printer redirection. For connections made with the RDP protocol, see

Using printer redirection with RDP on page 43

for more information.

Using audio redirection with VMware Horizon View

If you do not need the audio recording capability, use high-level audio redirection. Audio will play out of the

3.5 mm jack or, by default, a USB headset if it is plugged in. Use the local audio manager to adjust the input/ output level, select playback, and capture devices.

The VMware Horizon View client supports high-level audio-record redirection only via the PCoIP connection type on x86 units when connecting to a server running VMware Horizon View 5.2 Feature Pack 2 or higher. If you need audio-recording support and are using a different configuration, use one of the following methods:

●

If your system uses VMware Horizon View Client 1.7 or higher, use the RDP protocol to allow for highlevel audio redirection through either the 3.5 mm jack or a USB headset.

NOTE:

To use high-level audio-record redirection through the RDP protocol, the server must support it and be configured to allow audio recording over a remote session. The server must be running Windows

7 or greater. You also must make sure the HKLM\SYSTEM\CurrentControlSet\Control

\Terminal Server\WinStations\RDP-Tcp\fDisableAudioCapture registry key is set to

0.

●

If you have a USB headset with a microphone, you can use USBR. Set the USB headset to be redirected into the session. The headset will show up as an audio device. By default, USB audio devices are not redirected and the VMware Horizon View client uses high-level audio redirection. To redirect the USB headset, use the thin client’s USB Manager and select the USB headset to be redirected. Make sure that

VMware Horizon View is selected as the USBR protocol and make sure that the headset is checked under the Devices to be redirected.

NOTE:

VMware and HP do not recommend using USBR for headsets. A large amount network bandwidth is required to stream audio data over the USBR protocol. Also, you might experience poor audio quality with this method.

Using smart card redirection with VMware Horizon View

To use a smart card to log in to the VMware Horizon View server:

1.

Be sure smart card login is enabled in the VMware Horizon View Connection Manager.

After starting the connection, the VMware Horizon View client will display a list of server credentials.

2.

To unlock the credentials and access the VMware Horizon View Manager server, type the appropriate PIN for the server.

Using device redirection with VMware Horizon View 49

NOTE:

After you supply the correct PIN, the user’s credentials will be used to log in to the VMware Horizon

View Manager server. Please see the VMware Horizon View documentation for details on configuring the server to support smart card login. As long as the server is configured to allow smart card login, the user’s credentials will pass through and they will be logged in to the desktop without having to enter their PIN again.

NOTE:

To log in to the VMware Horizon View Manager administrator server with a smart card, the local smart card driver must be installed on the thin client. See

Using smart card redirection with RDP on page 44

for more information on smart card driver installation. Once logged in to the remote host, the smart card will be passed to the remote host using a virtual channel, not USBR. This virtual channel redirection makes sure that the smart card can be used for tasks such as email signing, screen locking, and so on, but might cause the smart card to not show as a smart card device in the Windows Device Manager.

NOTE:

The remote host must have the proper smart card drivers installed.

Using webcam redirection with VMware Horizon View

The VMware Horizon View client supports high-level webcam redirection only through RTAV using x86 units connected to a back-end server running VMware Horizon View 5.2 Feature Pack 2 or higher. Other connection methods do not support high-level webcam redirection and can redirect webcams only using USBR. Based on internal testing and validation, HP has found that the performance of a webcam connected through basic

USBR performs poorly. HP does not recommend the use of this configuration and suggests that customers who require this function test using x86 units with RTAV technology to ensure satisfactory levels of performance. With USBR, the webcam might perform poorly or not at all. See

Using USB redirection with RDP on page 42 for more information.

Changing the VMware Horizon View protocol type

The VMware Horizon View client connects to desktops using one of the following protocol types:

●

PCoIP protocol

●

RDP protocol

To change the connection type:

1.

In the VMware Horizon View client, select a pool that supports one of the following protocols:

●

PCoIP

●

RDP

2.

Under the Connection menu, select Settings.

3.

Change the protocol by using the drop-down box next to Connect Via.

NOTE:

Use the VMware Horizon View Manager to configure which connection protocol should be used for each desktop pool.

TIP:

HP recommends using the PCoIP protocol to enhance the desktop experience. However, the RDP protocol provides more options for customization and might work better on slower connections.

VMware Horizon View HTTPS and certificate management requirements

VMware Horizon View Client 1.5 and VMware Horizon View Server 5.0 and later require HTTPS. By default, the

VMware Horizon View client warns about untrusted server certificates, such as self-signed (like the VMware

Horizon View Manager default certificate) or expired certificates. If a certificate is signed by a Certificate

50 Chapter 8 VMware Horizon View connections

Authority (CA) and the CA is untrusted, the connection will return an error and the user will not be allowed to connect.

HP recommends that a signed certificate verified by a standard trusted root CA be used on the VMware

Horizon View Manager server. This makes sure that users will be able to connect to the server without being prompted or required to do any configuration. If using an internal CA, the VMware Horizon View client connection returns an error until you complete one of the following tasks:

●

Use the Certificate Manager to import the certificate from a file or URL.

●

Use a remote profile update to import a certificate.

●

In the VMware Horizon View Connection Manager, set Connection Security Level to Allow all

connections.

Table 8-6 VMware Horizon View certificate security levels

Security level

Certificate trust

Trusted

Self-signed

Expired

Untrusted

Refuse insecure connections

Trusted

Error

Error

Error

Warn

Trusted

Warning

Warning

Error

Allow all connections

Trusted

Untrusted

Untrusted

Untrusted

Table 8-7 Certificate security level definitions

Level Description

Trusted

Untrusted

Warning

Error

Connects without a certificate warning dialog and displays a green lock icon

Connects without a certificate warning dialog and displays a red unlock icon

Connects with a certificate warning dialog and displays a red unlock icon

Does not allow the connection

VMware Horizon View HTTPS and certificate management requirements 51

9 Web Browser connections

●

Web Browser general settings

●

Web Browser connection-specific settings

Web Browser general settings

The following table describes the settings available in the Web Browser Connection General Settings Manager.

These settings are universal and apply to all Web Browser connections.

NOTE:

For information about how to locate these settings, see

Using the Connection Manager controls on page 6 .

Table 9-1 Web Browser Connection General Settings Manager

Option Description

Web Browser preferences

Allow connections to manage their own settings

Opens the Firefox Preferences dialog.

When enabled, Firefox settings are saved for each Web Browser connection. Otherwise, the settings are reset each time the connection is launched.

Web Browser connection-specific settings

The following table describes the settings available in the Web Browser Connection Manager. These settings are connection-specific and apply to only the Web Browser connection you are currently configuring.

NOTE:

For information about how to locate these settings, see

Using the Connection Manager controls on page 6 .

Table 9-2 Web Browser Connection Manager > Configuration

Option

Name

URL

Intended Use

Enable kiosk mode

Enable full screen

Enable print dialog

Description

The connection name.

The URL for the connection.

Lets you set the intended use of the connection to either Citrix, RDP, or Internet.

Enables kiosk mode.

Uses full screen mode for the connection.

Enables the print dialog box.

NOTE:

See

Common connection settings on page 26

for information about the settings available on the final page of the Web Browser Connection Manager.

52 Chapter 9 Web Browser connections

10 Additional connection types (ThinPro configuration only)

The connection types listed in this chapter are available only when the thin client is set to the ThinPro configuration. For more information, see

Comparison of ThinPro and Smart Zero on page 1 .

●

TeemTalk connection settings

●

XDMCP connection settings

●

SSH connection settings

●

Telnet connection settings

●

Custom connection settings

TeemTalk connection settings

TIP:

For more information on HP TeemTalk, see the HP TeemTalk Terminal Emulator User Guide.

The following table describes the settings available in the TeemTalk Connection Manager. These settings are connection-specific and apply to only the TeemTalk connection you are currently configuring.

NOTE:

For information about how to locate these settings, see Using the Connection Manager controls on page 6

.

Table 10-1 TeemTalk Connection Manager > Configuration

Option Description

Name

TeemTalk creation wizard

System beep

The connection name.

Opens the TeemTalk Session Wizard. See the other tables in this section for more information.

Enables the system beep sound.

NOTE:

See Common connection settings on page 26 for information about the settings available on the final

page of the TeemTalk Connection Manager.

The following tables describe the settings available in the TeemTalk Session Wizard, which is a component of the TeemTalk Connection Manager. These settings are connection-specific and apply to only the TeemTalk connection you are currently configuring.

NOTE:

For information about how to locate these settings, see Table 10-1 TeemTalk Connection Manager >

Configuration on page 53

.

Table 10-2 TeemTalk Session Wizard > Page 1

Option Description

Session Name The name of the session.

TeemTalk connection settings 53

Table 10-2 TeemTalk Session Wizard > Page 1 (continued)

Option Description

Transport

Connection

Emulation

The network transport to use for the connection. Valid transports are: TCP/IP, Serial,

SSH2, and SSL.

The connection method to be used. Advanced connection options can be configured via the button.

Emulation types are: hp70092, IBM 3151, IBM3270 Display, IBM3270 Printer, IBM5250

Display, IBM5250 Printer, MD Prism, TA6530, VT Series, and Wyse.

Table 10-3 TeemTalk Session Wizard > Page 2

Option Description

Emulation Printer

Auto Logon

Key Macros

Mouse Actions

Soft Buttons

Attributes

Auxiliary Ports

Hotspots

The HP TeemTalk emulation printer settings.

The HP TeemTalk auto login settings.

The HP TeemTalk key macros settings.

The HP TeemTalk mouse actions settings.

The HP TeemTalk soft buttons settings.

The HP TeemTalk attributes settings.

The HP TeemTalk auxiliary ports settings.

The HP TeemTalk hotspots settings.

Table 10-4 TeemTalk Session Wizard > Page 3

Option Description

Preferences

Start session connected

Show Status Bar

Displays the preferences shown in Table 10-5 TeemTalk Session Wizard > Page 3 >

Preferences on page 54

.

Starts the session connected.

Displays the status bar for this connection.

Table 10-5 TeemTalk Session Wizard > Page 3 > Preferences

Option Description

Show Configuration Bar

Save Current Window Position

Run in Full Screen Mode

Displays the Configuration Bar.

Saves current window's size and position when you click Save Preferences. It will be restored on the next system launch.

NOTE:

Click Save Preferences each time you change the window size or position to save the new values.

Select to make the window full screen and remove the frame, soft buttons, menu, and configuration bars.

NOTE:

This option does not become effective until the next system launch and overrides the Show Configuration Bar and Save Current Window Position options.

54 Chapter 10 Additional connection types (ThinPro configuration only)

Table 10-5 TeemTalk Session Wizard > Page 3 > Preferences (continued)

Option Description

Browser Command

Command Line Start Up Options

In the box, type the command that runs your web browser, such as:

/ display html links Firefox

Use to specify an alternate location for the startup options.

NOTE:

For specific information on HP TeemTalk Command Line Startup Options, see the HP TeemTalk Terminal Emulator User Guide.

Table 10-6 TeemTalk Session Wizard > Page 4

Component Description

Summary Session Information Displays a summary of the session that is to be created.

XDMCP connection settings

XDMCP is a way to connect directly to remote X servers. X servers are used to display graphics on most UNIXlike operating systems, such as Linux, Berkeley Software Distribution (BSD), and Hewlett Packard UniX (HP-

UX).

The following table describes the settings available in the XDMCP Connection Manager. These settings are connection-specific and apply to only the XDMCP connection you are currently configuring.

NOTE:

For information about how to locate these settings, see Using the Connection Manager controls on page 6

.

Table 10-7 XDMCP Connection Manager > Configuration

Option Description

Name

Type

Address

Use font server

Font server

Configure display

The connection name.

The XDMCP connection type. Valid options are: chooser, query, and broadcast.

This value is required if the Type value is set to query.

Use a remote X font server instead of locally installed fonts.

Font server is not enabled unless the Use font server option is checked.

Click to set the display configuration for the connection. If you do not set this configuration, the default configuration will be used.

NOTE:

See Common connection settings on page 26 for information about the settings available on the final

page of the XDMCP Connection Manager.

SSH connection settings

Secure Shell (SSH) is the most common way to gain remote command line access to UNIX-like operating systems, such as Linux, BSD, and HP-UX. SSH is also encrypted.

XDMCP connection settings 55

The following table describes the settings available in the Secure Shell Connection Manager. These settings are connection-specific and apply to only the SSH connection you are currently configuring.

NOTE:

For information about how to locate these settings, see

Using the Connection Manager controls on page 6 .

Table 10-8 Secure Shell Connection Manager > Configuration

Option Description

Name

Address

Port

User name

Run application

Compression

X11 connection forwarding

Force TTY allocation

Foreground color

Background color

Font

The connection name.

The IP address of the remote system.

The remote port to use for the connection.

The username to use for the connection.

The application to run to make the connection.

Select this option if you want to compress the data sent between the server and thin client.

If the server has an X server on it, select this option to allow the user to open user interfaces from the SSH session and display them locally on the thin client.

Select this option and specify a command to initiate a temporary session to run the command. Once the command has completed, the session will terminate. If no command is specified, then the session will run normally as if the option were not selected.

The default color of the text in the SSH session.

The default color of the background in the SSH session.

Valid options are: 7X14, 5X7, 5X8, 6X9, 6X12, 7X13, 8X13, 8X16, 9X15, 10X20, and

12X24.

NOTE:

See

Common connection settings on page 26

for information about the settings available on the final page of the SSH Connection Manager.

56 Chapter 10 Additional connection types (ThinPro configuration only)

Telnet connection settings

Telnet is an older method of gaining remote command line access. It is not encrypted.

The following table describes the settings available in the Telnet Connection Manager. These settings are connection-specific and apply to only the Telnet connection you are currently configuring.

NOTE:

For information about how to locate these settings, see Using the Connection Manager controls on page 6

.

Table 10-9 Telnet Connection Manager > Configuration

Option Description

Name

Address

Port

Foreground color

Background color

Font

The name of the connection.

The IP address of the remote system.

The port to use on the remote system.

The foreground color.

The background color.

Valid options are: 7X14, 5X7, 5X8, 6X9, 6X12, 6X13, 7X13, 8X13, 8X16, 9X15, 10X20, and 12X24.

NOTE:

See Common connection settings on page 26 for information about the settings available on the final

page of the Telnet Connection Manager.

Custom connection settings

If you would like to install a custom Linux application, you can use the Custom connection to allow you to open this application through the connection manager.

The following table describes the settings available in the Custom Connection Manager. These settings are connection-specific and apply to only the Custom connection you are currently configuring.

NOTE:

For information about how to locate these settings, see Using the Connection Manager controls on page 6

.

Table 10-10 Custom Connection Manager > Configuration

Option

Name

Enter command to run

Description

The connection name.

The command to run to make the remote connection.

NOTE:

See Common connection settings on page 26 for information about the settings available on the final

page of the Custom Connection Manager.

Telnet connection settings 57

11 HP Smart Client Services

HP Smart Client Services is a set of server-side tools that enable you to configure ThinPro profiles that can be distributed to large numbers of thin clients. This function is called Automatic Update.

HP ThinPro detects an Automatic Update server upon startup and configures settings accordingly. This simplifies device installation and maintenance.

●

Supported operating systems

●

Prerequisites for HP Smart Client Services

●

Obtaining HP Smart Client Services

●

Viewing the Automatic Update website

●

Creating an Automatic Update profile

●

Updating thin clients

Supported operating systems

HP Smart Client Services supports the following operating systems:

●

Windows 7

●

Windows Server 2008

●

Windows Server 2008 R2

●

Windows Server 2003

●

Windows Vista

●

Windows XP

NOTE:

The installer is 32-bit only, although it is supported on both the 32-bit and 64-bit versions of the

Windows operating system.

Prerequisites for HP Smart Client Services

Before installing HP Smart Client Services, verify the configuration and installation status of the following components:

●

Internet Information Services (IIS)

●

.NET Framework 3.5

For information about installing or enabling these components on the operating system that you are using for the server, go to http://www.microsoft.com

.

Obtaining HP Smart Client Services

To obtain HP Smart Client Services:

58 Chapter 11 HP Smart Client Services

1.

Go to http://www.hp.com/support .

2.

Search for the thin client model. HP Smart Client Services can be found under the Software - System

Management category of the Drivers, Software & Firmware page.

Viewing the Automatic Update website

1.

On the server desktop, select Start > Control Panel, and then click Administrative Tools.

2.

Double-click Internet Information Services (IIS) Manager.

3.

In the left pane of the IIS Manager, expand the following items:

“Server name” > Sites > HP Automatic Update > auto-update

NOTE:

The physical location where the Automatic Update files are stored is as follows:

C:\Program Files (x86)\Hewlett-Packard\HP Smart Client Service\auto-update

Creating an Automatic Update profile

This section describes how to create an Automatic Update profile for a single MAC address.

1.

Obtain the MAC address of the thin client using the system info. For example, the following steps use the

MAC address 00fcab8522ac.

2.

Use the Profile Editor to create or modify a ThinPro profile (see Using the Profile Editor on page 62 )

until you are ready to save the ThinPro profile.

3.

In the Profile Editor, click the Finish link in the left-hand pane to access the Current profile pane.

4.

Click Save profile as to save the ThinPro profile as the following:

C:\Program Files (x86) Hewlett-Packard\HP Smart Client Service\autoupdate\PersistentProfile\MAC\00fcab8522ac.xml

5.

Click the Finish button in the Current profile pane to exit the Profile Editor.

6.

Restart the thin client that uses the specified MAC address to initiate the Automatic Update process.

Updating thin clients

●

Using the broadcast update method

●

Using the DHCP tag update method

●

Using the DNS alias update method

●

Using the manual update method

Using the broadcast update method

To do a broadcast update, plug the thin client into the same network as the update server. A broadcast update relies on HP Smart Client Services, which works with IIS to automatically push updates to the thin client.

NOTE:

Broadcast updates work only if the thin client is on the same subnet as the server.

TIP:

To verify that the broadcast updates are working, run the Profile Editor and make some changes.

Connect the thin client and verify that it has downloaded the new profile. If it has not, see Troubleshooting on page 67

.

Viewing the Automatic Update website 59

Using the DHCP tag update method

On the Windows Server 2003 and Windows Server 2008 systems, DHCP tagging enables a thin client to update. Use this method to update specific thin clients; however, if you have only one or two clients to update, consider using the manual update method instead. Otherwise, HP recommends the broadcast update method.

Example of performing DHCP tagging

The example in this section shows how to perform DHCP tagging on a Windows 2008 R2 Server.

NOTE:

To use DHCP tagging, see your DHCP server documentation.

1.

On the server desktop, select Start > Administrative Tools > DHCP.

2.

In the left pane of the DHCP screen, click the domain where the thin clients are connected.

3.

In the right pane of the DHCP screen, expand and right-click IPv4, and then click Set Predefined

Options.

4.

In the Predefined Options and Values dialog, click Add.

5.

In the Option Type box, configure the options as described in the following table.

Table 11-1 Example DHCP tagging options

Field Entry

Name

Data Type

Code

Description

Type auto-update.

Select String.

Type 137.

Type HP Automatic Update.

6.

Click OK.

7.

In the Predefined Options and Values dialog, under Value > String, type the update server address in the format of the following example: http://auto-update.dominio.com:18287/auto-update

8.

To complete the setup, click OK. DHCP tagging is now ready to update specific thin clients.

Using the DNS alias update method

During system startup, Automatic Update attempts to resolve the DNS alias auto-update. If that host name resolves, it attempts to check for updates at http://auto-update:18287. This update method enables thin clients to access a single update server across the entire domain, thus simplifying management for deployments with many subnets and DHCP servers.

To configure the DNS alias update method:

▲

Change the hostname of the server hosting HP Smart Client Services to auto-update or create a DNS alias of auto-update for that server.

Using the manual update method

Use the manual update method to connect a thin client to a specific server for an update. Also, use this method if you want to test an update on a single thin client before pushing the update to many thin clients, or if you have specific updates to be installed on only one or two thin clients.

60 Chapter 11 HP Smart Client Services

NOTE:

Be sure you specify the hostname of the manual server in the profile that you are updating to.

Otherwise the settings reset to automatic when downloading the profile. Use the Profile Editor to modify these settings at root/auto-update.

NOTE:

If multiple thin clients require specific updates, use the DHCP tagging method.

If no update segregation is required, use the broadcast update method.

Performing a manual update

1.

Select Management > Automatic Update in the Control Panel.

2.

Select Enable manual configuration.

3.

Set the Protocol as http.

4.

In the Server field, type the update server hostname and port in this format: <hostname>:18287

5.

In the Path field, type the following: auto-update

6.

Select Preserve thin client configuration if you want to preserve all previously configured settings.

7.

Click OK, and then the thin client will pull the updates.

Updating thin clients 61

12 Using the Profile Editor

HP Smart Client Services contains the Profile Editor, which allows administrators to create ThinPro profiles and upload them to the Automatic Update server.

TIP:

In addition to creating a new ThinPro profile, you can edit an existing profile that was exported using

HP ThinState.

A ThinPro profile contains the connections, settings, and customizations that were configured using the

Connection Manager and various Control Panel utilities. A ThinPro profile is saved in a configuration file that is specific to the version of HP ThinPro in which it was created.

This section includes the following topics:

●

Accessing the Profile Editor

●

Loading a ThinPro profile

●

Modifying a ThinPro profile

●

Configuring a serial or parallel printer

NOTE:

See

Registry keys on page 81

for a comprehensive list and description of registry keys.

Accessing the Profile Editor

▲

Click Start > All Programs > Hewlett-Packard > HP Automatic Update Server > Profile Editor.

Loading a ThinPro profile

The Profile Editor will automatically load the default ThinPro profile that was created during the HP Smart

Client Services installation process. This is indicated by the Profile.xml link in the Profile Editor pane.

To load a ThinPro profile:

1.

In the Profile Editor pane, click Profile.xml.

2.

Select the desired profile, and then click Open.

Modifying a ThinPro profile

Use the various screens in the Profile Editor to modify a ThinPro profile as discussed in the following topics:

●

Selecting the platform for a ThinPro profile

●

Configuring a default connection for a ThinPro profile

●

Modifying the registry settings of a ThinPro profile

●

Adding files to a ThinPro profile

●

Saving the ThinPro profile

62 Chapter 12 Using the Profile Editor

Selecting the platform for a ThinPro profile

Use the Platform screen in the Profile Editor to do the following:

●

Select the desired HP ThinPro image version that is compatible with your hardware

●

Choose between the ThinPro and Smart Zero configuration

●

View installed client kits that provide additional registry settings

NOTE:

Client kits should be placed in the following directory:

C:\Program Files (x86)\Hewlett-Packard\HP Smart Client Service\autoupdate\Packages

To configure a ThinPro profile’s platform settings:

1.

On the Platform screen in the Profile Editor, select an OS Build ID that corresponds to the desired image version.

IMPORTANT:

Be sure to create a different ThinPro profile for each hardware type.

NOTE:

If a client kit is installed, it is displayed automatically in the Client Kits box, and additional registry settings will be available on the Registry screen.

2.

Set the configuration to either standard (ThinPro) or zero (Smart Zero).

NOTE:

For older image versions, this setting is greyed out and set to zero automatically.

Configuring a default connection for a ThinPro profile

To configure a default connection for a ThinPro profile:

1.

On the Connection screen in the Profile Editor, choose the desired connection type from the Type dropdown list.

NOTE:

The available connection types differ depending on whether you chose the ThinPro or Smart

Zero configuration on the Platform screen.

2.

In the Server field, type the name or IP address of the server.

Modifying the registry settings of a ThinPro profile

To change default registry settings for a ThinPro profile:

1.

On the Registry screen in the Profile Editor, expand the folders in the Registry settings tree to locate the registry setting you want to change.

2.

Select the registry key, and then enter the desired value in the Value field.

Adding files to a ThinPro profile

Use the Files screen in the Profile Editor to add configuration files that will be installed on the thin client automatically when the ThinPro profile is installed. This is typically used for the following reasons:

●

To add certificates

●

To modify device settings when a registry setting for the change is unavailable

●

To modify the behavior of the system by inserting custom scripts or modifying existing scripts

Modifying a ThinPro profile 63

You can also specify a symbolic link that points to a file already installed on the thin client. Use this when the file needs to be accessed from more than one directory.

Adding a configuration file to a ThinPro profile

1.

On the Files screen in the Profile Editor, select Add a file.

2.

Select Import File, locate the file to be imported, and then select Open.

NOTE:

Files can also be exported using the Export File button, if further details about the file are required.

3.

In the Path field, enter the path where the file will be installed on the thin client.

4.

In the File details section, set the Owner, Group, and Permissions fields to the appropriate values.

NOTE:

Typically, setting the owner and group as root and the permissions as 644 is satisfactory. If a special owner, group, or permissions are required, refer to standard Unix file permissions for guidelines on changing the file details.

5.

Select Save to finish adding the configuration file to the ThinPro profile.

NOTE:

A file installed as part of a profile will automatically overwrite any existing file on the file system at the destination path. Additionally, a second profile without the file attached will not revert previously attached files. All files that have been installed through profile attachment are permanent and must be reverted manually or through a factory reset.

Adding certificates to a ThinPro profile

ThinPro profiles automatically include certificates that are imported to a standard client certificate store for the following applications:

●

VMware Horizon View, Citrix, RDP

●

Automatic Update

●

HP Smart Client Services

●

Web browser stores

To import other certificates to a ThinPro profile:

1.

On the Files screen in the Profile Editor, select Add a file.

2.

Select Import File, locate the certificate, and then select Open.

NOTE:

The certificate should be formatted as a .pem or .crt file.

3.

In the Path field, set the path to the following:

/usr/local/share/ca-certificates

4.

Select Save to finish adding the certificate to the ThinPro profile.

5.

After installing the ThinPro profile, use the Certificate Manager to confirm that the certificate was imported properly.

Adding a symbolic link to a ThinPro profile

1.

On the Files screen in the Profile Editor, select Add a file.

2.

In the Type drop-down list, select Link.

64 Chapter 12 Using the Profile Editor

3.

In the Symbolic link details section, set the Link field to the path of the desired file already installed on the thin client.

4.

Select Save to finish adding the symbolic link.

Saving the ThinPro profile

1.

In the Profile Editor, select Finish in the left-hand pane to access the Current profile screen.

2.

Select Save Profile to save to the current ThinPro profile, or select Save Profile As to save as a new

ThinPro profile.

NOTE:

If Save Profile is disabled, your ThinPro profile has not changed since the last time it was saved.

3.

Select the Finish button in the Current profile screen to exit the Profile Editor.

Configuring a serial or parallel printer

Use the Profile Editor to set up the serial or parallel printer ports. A USB printer automatically maps when plugged in.

This section includes the following topics:

●

Obtaining the printer settings

●

Setting up printer ports

●

Installing printers on the server

Obtaining the printer settings

Before configuring printer ports, obtain the printer's settings. If available, check the printer's documentation before going further. If it is not available, follow these steps:

1.

For most printers, press and hold the Feed button while turning the device on.

2.

After a few seconds, release the Feed button. This allows the printer to enter a test mode and print the required information.

TIP:

You might need to turn the printer off to cancel the Test mode or press Feed again to print a diagnostic page.

Setting up printer ports

1.

In the Profile Editor, select Registry, and then enable the Show all settings checkbox.

2.

Enable printer port mapping for your connection type:

●

Citrix—No action is required.

●

RDP—Navigate to root > ConnectionType > freerdp. Right-click on the connections folder, select

New connection, and then click OK. Set the portMapping registry key to 1 to enable printer port mapping.

●

VMware Horizon View—Navigate to root > ConnectionType > view. Right-click on the connections folder, select New connection, and then click OK. Under the xfreerdpOptions folder, set the

portMapping registry key to 1 to enable printer port mapping.

Configuring a serial or parallel printer 65

3.

Navigate to root > Serial. Right-click the Serial folder, select New UUID, and then click OK.

4.

Under the new directory, set the baud, dataBits, flow, and parity values to the ones obtained in

Obtaining the printer settings on page 65 .

Set the device value to the port the printer will be plugged into. For example, the first serial port would be /dev/ttyS0, the second serial port would be /dev/ttyS1, and so on. For USB serial printers, use the format /dev/ttyUSB#, where # is the number of the port, starting with 0.

Installing printers on the server

1.

On the Windows desktop, select Start > Printers and Faxes.

2.

Select Add Printer, and then click Next.

3.

Select Local Printer attached to this Computer and, if required, deselect Automatically detect and

install my Plug and Play printer.

4.

When completed, click Next.

5.

In the menu, select a port.

NOTE:

The port you need is in the section of ports labeled TS###, where ### is a number between

000–009, 033–044. The appropriate port depends on your hostname and the printer you want to install.

For example, with a hostname of ZTAHENAKOS and a serial printer, select the port with

(ZTAHENAKOS:COM1). For a parallel printer, select (ZTAHENAKOS:LPT1). The TS### is assigned by the server, so it will not be the same every time.

6.

Select the manufacturer and driver for your printer.

TIP:

If desired, use the driver disc Windows Update to install the driver.

NOTE:

For basic or test printing, the Generic Manufacturer or Generic/Text Only printer usually works.

7.

If prompted to keep the existing driver and it is known to work, keep it, and then click Next.

8.

Assign a name to the printer. To use it as the default printer, select Yes, and then click Next.

9.

To share the printer, select Share name and assign it a share name. Otherwise, click Next.

10.

On the next page, you may request a test print. HP recommends this because it will verify the printer setup is correct. If it is not set up properly, review the settings and try again.

NOTE:

If the thin client disconnects from the server, the printer will need to be set up again the next time the thin client connects.

66 Chapter 12 Using the Profile Editor

13 Troubleshooting

This chapter discusses the following topics:

●

Troubleshooting network connectivity

●

Troubleshooting firmware corruption

●

Troubleshooting Citrix password expiration

●

Using system diagnostics to troubleshoot

Troubleshooting network connectivity

1.

Ping the desired server by doing the following:

a.

Click the System Information button on the taskbar, and then click on the Net Tools tab.

b.

Under Select Tool, select Ping.

c.

In the Target Host box, type the server address, and then click Start Process.

If the ping is successful, the system will display the following output:

PING 10.30.8.52 (10.30.8.52) 56(84) bytes of data.

64 bytes from 10.30.8.52: icmp_seq-1 ttl=64 time=0.81 5 ms 64 bytes from 10.30.8.52: icmp_seq=2 ttl=64 time=0.735 ms

If the ping is unsuccessful, the thin client might be disconnected from the network and experience a long delay with no system output.

2.

If the thin client does not respond to the ping, do the following:

a.

Check the network cable and check the network settings in the Control Panel.

b.

Try pinging other servers or thin clients.

c.

If you can reach other thin clients, verify that you typed the correct server address.

d.

Ping the server using the IP address instead of the domain name or vice-versa.

3.

Check the system logs by doing the following:

a.

Click the System Information button on the taskbar, and then click on the System Logs tab.

b.

Check for any errors in the logs.

c.

If there is an error, then the Server is not set up notification appears. Verify that the server is set up properly and that HP Smart Client Services is running.

Troubleshooting firmware corruption

If the thin client beeps two times after it is powered on or does not appear to boot, then the device firmware may be corrupt. It is possible to resolve this by downloading the thin client image from http://www.hp.com

, copying the image to a removable USB flash drive, and then booting the thin client from that flash drive.

Troubleshooting network connectivity 67

Reimaging thin client firmware

1.

Download the image from http://www.hp.com

.

2.

Unpack the image to the path C:\USBBoot.

3.

Format a USB flash drive.

4.

Copy all the files from C:\USBBoot to the root of the USB flash drive.

5.

Shut down the thin client.

6.

Insert the USB flash drive into the thin client.

7.

Turn on the thin client, and it will boot to the USB flash drive.

8.

Follow the on-screen instructions to reimage the thin client.

9.

When the reimage process completes, remove the USB flash drive and press Enter .

Troubleshooting Citrix password expiration

If users are not being prompted to change expired Citrix passwords, then make sure the XenApp Services site

(PNAgent site) has the Prompt authentication method set to allow users to change expired passwords. If you allow users to change their passwords by connecting directly to the domain controller, then make sure the time of the thin client is in sync with the domain controller and use the full domain name (for example, domain_name.com) when entering the Citrix login credentials. For more information, see Citrix documentation.

Using system diagnostics to troubleshoot

System diagnostics take a snapshot of the thin client that can be used to help solve issues without physical access to the thin client. This snapshot contains log files from the BIOS information and the processes active at the time the system diagnostics were run.

TIP:

You can change the Debug level setting in the System Logs tab of the System Information window to specify the amount of information to be included in the diagnostic report. This information may be requested by HP for troubleshooting. Because the system resets log files when it reboots, be sure to capture logs before a reboot.

Saving system diagnostic data

1.

Insert a USB flash drive into the thin client.

2.

Click the System Information button on the taskbar, and then click the System Logs tab.

3.

Click Diagnostic, and then save the compressed diagnostic file Diagnostic.tgz to the USB flash drive.

Uncompressing the system diagnostic files

The system diagnostic file Diagnostic.tgz is compressed and will need to be uncompressed before you can view the diagnostic files.

Uncompressing the system diagnostic files on Windows-based systems

1.

Download and install a copy of the Windows version of 7-Zip.

68 Chapter 13 Troubleshooting

NOTE:

You may obtain a free copy of 7-Zip for Windows at http://www.7-zip.org/download.html

.

2.

Insert the USB flash drive that contains the saved system diagnostic file, and then copy Diagnostic.tgz to the desktop.

3.

Right-click Diagnostic.tgz and select 7-zip > Extract files.

4.

Open the newly created folder named Diagnostic and repeat step 3 on Diagnostic.tar.

Uncompressing the system diagnostic files in Linux- or Unix-based systems

1.

Insert the USB flash drive that contains the saved system diagnostic file, and then copy Diagnostic.tgz to the home directory.

2.

Open a terminal and browse to the home directory.

3.

On the command line, enter tar xvfz Diagnostic.tgz.

Viewing the system diagnostic files

The system diagnostic files are divided into the Commands, /var/log, and /etc folders.

Viewing files in the Commands folder

This table describes the files to look for in the Commands folder.

Table 13-1 Commands folder files

File Description

demidecode.txt

dpkg_--list.txt

ps_-ef.txt

This file contains information on the system BIOS and graphics.

This file lists the packages installed at the time system diagnostics were run.

This file lists the active processes at the time system diagnostics were run.

Viewing files in the /var/log folder

The useful file in the /var/log folder is Xorg.0.log.

Viewing files in the /etc folder

The /etc folder contains the file system at the time the system diagnostics were run.

Using system diagnostics to troubleshoot 69

A USB updates

When USB updates are enabled (see Customization Center on page 19 ), you can use a USB flash drive to

simultaneously install multiple add-ons and certificates, as well as deploy a profile.

To perform USB updates:

1.

Place the desired files onto a USB flash drive.

NOTE:

The files can be placed in the root directory or in subfolders.

2.

Connect the USB flash drive to the thin client.

Updates are detected automatically and displayed in the USB Update dialog, in which you can search and view details about the detected updates.

3.

Select the checkboxes next to the updates you want to install, and then click Install.

4.

After installation, restart the thin client if prompted.

70 Appendix A USB updates

B BIOS tools

There are two kinds of BIOS tools for HP ThinPro:

●

BIOS settings tool—Used to retrieve or modify BIOS settings

●

BIOS flashing tool—Used to update the BIOS

BIOS settings tool

The following table describes the syntax for the BIOS settings tool.

Syntax

hptc-bios-cfg –G [options] [filename] hptc-bios-cfg –S [options] [filename] hptc-bios-cfg –h

Description

Retrieves the current BIOS settings and saves them to the specified file so they can be viewed or modified (CPQSETUP.TXT by default).

Writes the BIOS settings from the specified file (CPQSETUP.TXT by default) to the BIOS.

Displays a list of options.

BIOS flashing tool

The following table describes the syntax for the BIOS flashing tool.

Syntax

hptc-bios-flash [options] <ImageName> hptc-bios-flash –h

Description

Flashes the BIOS with the specified BIOS image.

Displays a list of options.

BIOS settings tool 71

C Resizing the flash drive partition

IMPORTANT:

HP thin clients that ship from the factory with HP ThinPro 5.2 or newer use the entire flash drive. The image capture methods have been updated to capture the smallest possible image, allowing images from larger flash drives to be deployed onto smaller flash drives that have enough space for the captured image. Resizing the flash drive partition should no longer be necessary for HP thin clients that ship from the factory with HP ThinPro 5.2 or newer. For thin clients with HP ThinPro that are not using the entire flash drive for any reason, see the following information.

To use the entire space of the flash drive, you have to modify the partition size and expand the file system to take up that additional space. This can be accomplished using the resize-image script.

NOTE:

When an image is deployed via HPDM, HP ThinState, or Automatic Update, the file system is automatically resized to use all available space on the flash drive.

The following table describes the syntax for the resize-image script.

Syntax

resize-image

Description

When called with no parameters, the script displays the current size of the partition and the amount of available space on the flash drive. The script prompts you to enter the target partition size and then confirm the change. The change takes effect after the next thin client restart.

NOTE:

It is not possible to decrease the partition size. The entered value must be larger than the current partition size.

Using this syntax, you can specify the target partition size in megabytes (MB) as a parameter and then confirm the change.

resize-image --size <SizeInMB>

Example: resize-image --size 1024 resize-image --no-prompt

—or— resize-image --no-prompt --size <SizeInMB>

Example: resize-image --no-prompt --size 1024

Using this syntax, the script runs automatically with no user interaction required.

If no specific size is given as a parameter simultaneously, the partition size is increased to the maximum size.

TIP:

This non-interactive mode is useful for scripting and performing this operation from a remote administration tool like

HP Device Manager.

72 Appendix C Resizing the flash drive partition

D Customizing the Smart Zero login screen

Customizing the screen background

This section describes the common attributes and elements used in customizing the Smart Zero login screen.

There is one directory per connection type—plus a default style—that specifies the style elements of the connection’s background image and login window style.

In a style directory, the file bgConfig.rtf specifies the elements in the desktop's background window. The syntax of the bgConfig.rtf file is in a stylesheet-like format with some or all of the elements described below.

Each element begins with an element type and then a set of attributes surrounded by braces, such as in the following example: global { color: 666666; # Dark gray padding: 20; # 20 pixels }

Any number of image or text elements can be specified. If any gradients are specified, only the last of them is used to color the desktop's background; otherwise, the color specified in the global section is used. Any line that begins with a number sign “#” is considered a comment and is ignored, as are blank lines. Text following a semicolon that begins with a “#” is also treated as a comment, such as the previous example.

Each element is assigned a set of attributes such as size, color, and position. Each attribute is specified by the attribute name, followed by a colon, followed by its values, followed by a semicolon, all on a single line. Some of these attributes are common to many element types.

The elements include:

●

Common attributes

●

Elements

●

Image

●

Text

Common attributes

Table D-1 Login Screen > Common Attributes > Name

Type

Parameter

Example

Default

Use

Description

A string name: ItemName;

Specifies a string to associate with the element. It is used only in debugging output, such as when a syntax or value error is found in attribute parsing.

Customizing the screen background 73

Table D-2 Login Screen > Common Attributes > padding

Type

Parameter

Example

Default

Use

Description

An absolute (pixel) or percentage value padding: 20;

An object will be positioned on the screen as if the screen were smaller on all sides by the padding value. For example, if an element would normally be placed at 0,0 with a padding of 20, it would be placed at 20,20 instead. If specified in the global element, it will apply to all subsequent elements, leaving an empty gutter around the screen edge, unless those elements override the padding with their own padding value.

Table D-3 Login Screen > Common Attributes > color

Type

Parameter

Example

Default

Use

Description

RRGGBB 6-digit hex value or rrr,ggg,bbb 0–255,0–255,0–255 form color: ff8800;

255,255,255 (white)

Specifies the color of the element

Table D-4 Login Screen > Common Attributes > alpha

Type

Parameter

Example

Default

Use

Description

0–255 integer alpha: 127;

255 (fully opaque)

Specifies the opacity of the element. 255 is fully opaque; 0 is fully transparent. Elements are layered over the background in the order they are defined.

Table D-5 Login Screen > Common Attributes > size

Type

Parameter

Example

Default

Use

Description

WWxHH, where WW is the width in absolute pixels or in a percentage of screen width and HH is the height in absolute pixels or in a percentage of the screen height.

size: 256x128;

The natural size of the element; for example, the pixel size of an image.

Specifies the size of the element. Elements will be scaled to match the specified size.

74 Appendix D Customizing the Smart Zero login screen

Table D-6 Login Screen > Common Attributes > position

Type

Parameter

Example

Default

Use

Description

XX,YY where XX and YY are positions in absolute pixels or in percentages of the screen width and height.

position: 50%, 90%;

0,0 (the upper left)

Specifies the position of the element. See the alignment table as well.

Table D-7 Login Screen > Common Attributes > alignment

Type

Parameter

Example

Default

Use

Description

[left I hcenter I right] [top I vcenterIbottom] alignment: left bottom; hcenter vcenter—the element is centered at the given position.

The combination of position and alignment specify both an anchor point for the element and how the element is aligned relative to that anchor point. For example, with a position of 90%,

70% and an alignment of right bottom, the element is positioned so that its right edge is at 90% of the width of the screen and its bottom edge is at 70% of the height of the screen.

Table D-8 Login Screen > Common Attributes > context

Type

Parameter

Example

Default

Use

Description

[login I desktop I all] context: login; all

Specifies whether the element should be shown only on the login screen for the protocol, on the desktop screen for the protocol (if any), or on both. Only some protocols (for example, Citrix

XenDesktop) have a desktop screen.

Elements

Table D-9 Login Screen > Elements > Custom > Global

Type

Use

Common attributes recognized

Description

Specifies the global background or padding values.

name, color, padding

●

color—specifies the solid background color of the screen, if no gradients are specified

●

padding—specifies the default padding for all subsequent elements

Customizing the screen background 75

Table D-10 Login Screen > Elements > Custom > Gradient

Type

Use

Common attributes recognized

Description

Specifies a full-screen gradient for use in the background.

name, context

Table D-11 Login Screen > Elements > Custom > Type

Type

Parameter

Example

Default

Use

Description

Specifies a full-screen gradient for use in the background.

Type: linear; linear

Linear gradients can be either horizontally oriented or vertically oriented; coordinates given in colors are a fraction of the width or height. Radial gradients are centered on the screen center; coordinates are a fraction of the distance to the screen edge (top and bottom or left and right).

Table D-12 Login Screen > Elements > Custom > Axis

Type

Parameter

Example

Default

Use

Description

[height I width] axis: width; height

For linear gradients, the axis specifies the direction of the gradient (top-to-bottom or left-to-right). For radial gradients, the axis specifies whether the radius of the gradient is half-screen height or half-screen width.

Table D-13 Login Screen > Elements > Custom > Metric

Type

Parameter

Example

Default

Use

Description

[linear I squared] metric: linear; squared

For radial gradients, the metric specifies whether the color interpolation between points is done with a dx2+dy2 distance calculation (squared) or the square root of number (linear).

Squared interpolation is somewhat quicker to draw.

76 Appendix D Customizing the Smart Zero login screen

Table D-14 Login Screen > Elements > Custom > colors

Type

Parameter

Example

Default

Use

Description

A space-separated list of [value,color] pairs, where the value is a

0.0–1.0 floating point fraction of the axis of measurement (for example, the width of the screen in a linear width-axis gradient) and the color is the color of the gradient at that point. The value runs top-to-bottom for vertical linear gradients; left-to-right for horizontal linear gradients; and center-to-edge for radial gradients. Colors are specified as either six-digit hex or three 0–

255 comma-separated values.

colors: 0.0,000000 0.5,996600 0.9,255,255,255;

Not applicable

Colors are interpolated along the linear or radial axis between the points and colors specified. If no values are given, the colors are assumed to be evenly spaced on the axis between 0.0 and 1.0. If the first fractional value is greater than 0.0, the first color will be used in the space between the screen edge and the first value.

Likewise, if the last value is less than 1.0, the last color will be used between the last value and the screen edge. Values must be in increasing sorted values, though a value can be repeated for a sharp transition. For example, “0.0, CCCCCC 0.5,EEEEEE

0.5,660000 1.0,330000” in a vertical linear gradient would specify a gradient between light grays on the upper half and dark reds on the lower half.

Table D-15 Login Screen > Elements > Custom > dithered

Type

Parameter

Example

Default

Use

Description

[true | false] dithered: true; false

If a gradient shows signs of color banding, dithering will eliminate this visual artifact. Dithering is not supported for radial gradients with the squared metric.

Image

Table D-16 Login screen > Image

Type

Use

Common attributes recognized

Common attributes

Description

Specifies an image to overlay a portion of the background.

name, size, alpha, position, alignment, context

See the tables following.

Customizing the screen background 77

Table D-17 Login screen > Custom Attributes > Source

Type

Parameter

Example

Default

Use

Description

File path source: /writable/misc/Company_logo.png;

Not applicable

Specifies the absolute pathname to the image file. Many formats are supported; for example, png, jpg,and gif. The image may have transparent regions.

Table D-18 Login screen > Custom Attributes > Proportional

Type

Parameter

Example

Default

Use

Description

[true | false] proportional: false; true

When true, if the image needs to be scaled, its aspect ratio will be maintained to fit within the rectangle specified. When false, nonproportional scaling is done to make the image exactly fit the specified size.

Text

Table D-19 Login screen > Text

Type

Use

Common attributes recognized

Common attributes

Description

Specifies a string of text to lay over the background name, size, color, alpha, position, alignment, context

See the tables below.

Table D-20 Login screen > Text > text-locale

Type

Parameter

Example

Default

Use

Description

Localized text text-de_DE: Dieser Text is in Deutsch.;

Not applicable

When in the matching locale, this text will be used for the string.

The supported text strings are as follows:

● de_DE (German)

● en_US (English)

● es_ES (Spanish)

● fr_FR (French)

78 Appendix D Customizing the Smart Zero login screen

Table D-20 Login screen > Text > text-locale (continued)

Type Description

● ja_JP (Japanese)

● zh_CN (Simplified Chinese)

NOTE:

The file encoding is UTF-8.

Table D-21 Login screen > Text > text

Type

Parameter

Example

Default

Use

Description

Default text text:

This will be shown on the screen.;

Not Applicable

If no matching localized text is specified, this text string will be used instead.

NOTE:

The text rendering engine does not support HTML-style markup.

Table D-22 Login screen > Text > font-locale

Type

Parameter

Example

Default

Use

Description

locale-specific fontName font-ja_JP: kochi-gothic;

Not applicable

When in the matching locale, this font will be used when the string is rendered. See the description for text-locale previous.

The name must match one of the fonts under /usr/share/fonts/

truetype. For Japanese text, it might be necessary to select kochi-gothic; for Simplified Chinese text, u mi ng.

Table D-23 Login screen > Text > font

Type

Parameter

Example

Default

Use

Description

fontName font: DejaVuSerif-Bold

; DejaVuSerif

If no matching localized font is specified, this font will be used instead. The name must match one of the fonts under /usr/share/

fonts/truetype.

Customizing the screen background 79

Table D-24 Login screen > Text > font-size

Type

Parameter

Example

Default

Use

Table D-25 Login screen > Text > max-width

Type

Parameter

Example

Default

Use

Table D-26 Login screen > Text > max-height

Type

Parameter

Example

Default

Use

Description

Pixels (for example, 20) or percentage of the screen height (for example, 5%) or points (for example, 12pt) font-size: 12pt;

Not applicable

Specifies the default size of the font. The text may be further scaled if size, max-width, and/or max-height are specified.

Description

Size in pixels or in a percentage of the screen width max-width: 90%;

Not applicable

If the string would otherwise turn out to be wider than the size given, it is scaled down to fit within the width specified.

Description

Size in pixels or in a percentage of screen height.

max-height: 64;

Not applicable

If the text would otherwise turn out to be taller than the size given, it is scaled down to fit the height specified.

80 Appendix D Customizing the Smart Zero login screen

E Registry keys

The tables in this appendix describe the paths, functions, and options for the registry keys of HP ThinPro.

The values of these registry keys can be modified in several different ways:

●

Using a _File and Registry task in HPDM

●

Using the Registry Editor component of the Profile Editor and then deploying the new profile

●

Using the Registry Editor in the HP ThinPro user interface, which is available by typing regeditor in the X Terminal.

NOTE:

Some registry keys might apply to the ThinPro or Smart Zero configuration only.

Registry keys are organized into the following high-level folders:

●

root > Audio

●

root > CertMgr

●

root > ComponentMgr

●

root > ConnectionManager

●

root > ConnectionType

●

root > CpuMgr

●

root > DHCP

●

root > Dashboard

●

root > Display

●

root > Network

●

root > SCIM

●

root > ScepMgr

●

root > Search

●

root > Serial

●

root > SystemInfo

●

root > TaskMgr

●

root > USB

●

root > auto-update

●

root > background

●

root > config-wizard

●

root > desktop

●

root > entries

●

root > keyboard

81

●

root > logging

●

root > mouse

●

root > restore-points

●

root > screensaver

●

root > security

●

root > sshd

●

root > time

●

root > touchscreen

●

root > translation

●

root > usb-update

●

root > users

●

root > vncserver

root > Audio

Table E-1 root > Audio

Registry key

root/Audio/AdjustSoundPath root/Audio/OutputMute root/Audio/OutputScale root/Audio/OutputScaleAuto root/Audio/OutputVolume root/Audio/PlaybackDevice root/Audio/RecordDevice root/Audio/RecordMute root/Audio/RecordScale root/Audio/RecordScaleAuto root/Audio/RecordVolume root/Audio/VisibleInSystray

Description

Sets the full path to the sound played when the playback volume is changed via the volume controls.

If set to 1, the internal speaker and headphone jack are muted.

Sets the volume scale for the internal speaker and headphone jack, ranging from 1 to 400.

If set to 1, the OutputScale value will be set automatically based on the thin client model.

Sets the volume for the internal speaker and headphone jack, ranging from 1 to 100.

Sets the device to use for playback.

Sets the device to use for capture.

If set to 1, the microphone jack is muted.

Sets the volume scale for the microphone jack, ranging from 1 to

400.

If set to 1, the RecordScale value will be set automatically based on the thin client model.

Sets the volume for the microphone jack, ranging from 1 to 100.

If set to 1, a speaker icon is visible in the system tray.

root > CertMgr

This registry category is used internally and does not have any user-defined entries.

82 Appendix E Registry keys

root > ComponentMgr

Table E-2 root > ComponentMgr

Registry key

root/ComponentMgr/General/

NotShowDeleteSnapshotWarning

root > ConnectionManager

Table E-3 root > ConnectionManager

Registry key

root/ConnectionManager/customLogoPath root/ConnectionManager/defaultConnection

Description

If set to 1, warning information will not be shown while deleting a snapshot.

root/ConnectionManager/minHeight root/ConnectionManager/minWidth root/ConnectionManager/splashLogoPath root/ConnectionManager/useKioskMode root/ConnectionManager/ useSplashOnConnectionStartup

Description

To properly launch a connection on startup, this must be set to a valid connection using the format <type>:<label> like in the following example: xen:Default Connection

Sets the full path to the image displayed while a connection is loading.

If set to 1, the image set by splashLogoPath is enabled. By default, this is enabled for ThinPro and disabled for Smart Zero.

root > ConnectionType root > ConnectionType > custom

Table E-4 root > ConnectionType > custom

Registry key

root/ConnectionType/custom/authorizations/ user/add root/ConnectionType/custom/authorizations/ user/general root/ConnectionType/custom/connections/

<UUID>/afterStartedCommand root/ConnectionType/custom/connections/

<UUID>/afterStoppedCommand root/ConnectionType/custom/connections/

<UUID>/authorizations/user/edit root/ConnectionType/custom/connections/

<UUID>/authorizations/user/execution

Description

If set to 1, a standard user has permission to add a new connection of this type using the Connection Manager. This key has no effect on Smart Zero.

If set to 1, a standard user has permission to modify the general settings for this connection type using the Connection Manager.

This key has no effect on Smart Zero.

Sets the command to execute after the connection has been started.

Sets the command to execute after the connection has been stopped.

If set to 1, a standard user has permission to modify the connection settings for this connection.

If set to 1, a standard user has permission to execute this connection.

root > ComponentMgr 83

Table E-4 root > ConnectionType > custom (continued)

Registry key

root/ConnectionType/custom/connections/

<UUID>/autoReconnect root/ConnectionType/custom/connections/

<UUID>/autoReconnectDelay root/ConnectionType/custom/connections/

<UUID>/autostart root/ConnectionType/custom/connections/

<UUID>/autostartDelay root/ConnectionType/custom/connections/

<UUID>/beforeStartingCommand root/ConnectionType/custom/connections/

<UUID>/command root/ConnectionType/custom/connections/

<UUID>/connectionEndAction root/ConnectionType/custom/connections/

<UUID>/coord root/ConnectionType/custom/connections/

<UUID>/dependConnectionId root/ConnectionType/custom/connections/

<UUID>/extraEnvValues/<UUID>/key root/ConnectionType/custom/connections/

<UUID>/extraEnvValues/<UUID>/value root/ConnectionType/custom/connections/

<UUID>/fallBackConnection root/ConnectionType/custom/connections/

<UUID>/hasDesktopIcon root/ConnectionType/custom/connections/

<UUID>/label root/ConnectionType/custom/connections/

<UUID>/startMode root/ConnectionType/custom/connections/

<UUID>/waitForNetwork root/ConnectionType/custom/coreSettings/

USBrelevant root/ConnectionType/custom/coreSettings/ appName

Description

If set to 1, the connection will be restarted when it is closed or disconnected.

Sets the amount of time in seconds to wait before reconnecting the session. The default of 0 will cause the connection to reconnect immediately. This setting only takes effect when autoReconnect is set to 1.

If set to a value of 1–5, the connection will be started automatically after the system boots, with the value of 1 having the highest priority.

Sets the amount of time in seconds to wait before starting the connection after the system boots. The default of 0 will cause the connection to start immediately. This setting only takes effect when autostart is set to 1.

Sets the command to execute before the connection starts.

Sets the main command for the custom connection to execute.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the name of an extra environment variable for use with the connection.

Sets the value of an extra environment variable for use with the connection.

Sets the fallback connection via its UUID.

If set to 1, the desktop icon for this connection is enabled. This key has no effect on Smart Zero.

Sets the connection name that is displayed in the UI. On Smart

Zero, this will typically be set to Default Connection and does not display in the UI.

If set to the default focus and the connection is already started, the connection will be given focus. Otherwise, an error will be returned stating that the connection is already started.

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

Specifies if this connection type is USB-relevant. If it is, it might have a USB plugin for redirecting USB devices.

Sets the internal application name to use for this connection type.

This key should not need to be modified.

84 Appendix E Registry keys

Table E-4 root > ConnectionType > custom (continued)

Registry key Description

root/ConnectionType/custom/coreSettings/ className root/ConnectionType/custom/coreSettings/ editor

Sets the internal application class name to use for this connection type. This key should not need to be modified.

Sets the internal application name to use when the Connection

Manager is launched for this connection type. This key should not need to be modified.

root/ConnectionType/custom/coreSettings/ generalSettingsEditor root/ConnectionType/custom/coreSettings/ serverRequired

Sets the internal application name to use when the General

Settings Manager is launched for this connection type. This key should not need to be modified.

Sets the path to the 16x16 pixel icon for this application.

root/ConnectionType/custom/coreSettings/ icon16Path root/ConnectionType/custom/coreSettings/ icon32Path

Sets the path to the 32x32 pixel icon for this application.

root/ConnectionType/custom/coreSettings/ icon48Path

Sets the path to the 48x48 pixel icon for this application.

root/ConnectionType/custom/coreSettings/label Sets the name to display for this connection type in the UI.

root/ConnectionType/custom/coreSettings/ priorityInConnectionLists

Sets the priority of this connection type when it is displayed in the

Connection Manager and the Configuration Wizard that displays during initial setup. A higher value will move the connection type towards the top of the list. If set to 0, the connection type is hidden from Configuration Wizard and is shown last in Connection

Manager. Connections types with the same priority are listed in alphabetical order.

Sets whether a server name or address is unused, optional, or required for this connection type.

root/ConnectionType/custom/coreSettings/ stopProcess root/ConnectionType/custom/coreSettings/ watchPid root/ConnectionType/custom/coreSettings/ wrapperScript

Sets the behavior that should occur when connection-mgr stop is called on this connection. By default this is close, which will send a standard kill signal to the process. When set to kill, the process specified by appName will be forcefully killed. When set to custom, a custom execution script specified by wrapperScript will be executed with the argument stop to terminate the process gracefully.

If set to 1, the connection is monitored under the name specified by appName. This key should not need to be modified.

Sets the script or binary to execute when launching this connection type. This is the primary script handling all connection settings and command line arguments for the connection. This key should not need to be modified.

root/ConnectionType/custom/gui/CustomManager/ name

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/custom/gui/CustomManager/ status

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/custom/gui/CustomManager/ title

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/custom/gui/CustomManager/ widgets/autoReconnect

Controls the state of the Auto reconnect widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root > ConnectionType 85

Table E-4 root > ConnectionType > custom (continued)

Registry key Description

root/ConnectionType/custom/gui/CustomManager/ widgets/autostart

Controls the state of the Auto start priority widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/custom/gui/CustomManager/ widgets/command

Controls the state of the Enter command to run widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/custom/gui/CustomManager/ widgets/fallBackConnection

Controls the state of the Fallback Connection widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/custom/gui/CustomManager/ widgets/hasDesktopIcon

Controls the state of the Show icon on desktop widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/custom/gui/CustomManager/ widgets/label

Controls the state of the Name widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/custom/gui/CustomManager/ widgets/waitForNetwork

Controls the state of the Wait for network before connecting widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root > ConnectionType > firefox

Table E-5 root > ConnectionType > firefox

Registry key

root/ConnectionType/firefox/authorizations/ user/add root/ConnectionType/firefox/authorizations/ user/general root/ConnectionType/firefox/connections/

<UUID>/address root/ConnectionType/firefox/connections/

<UUID>/afterStartedCommand root/ConnectionType/firefox/connections/

<UUID>/afterStoppedCommand

Description

If set to 1, a standard user has permission to add a new connection of this type using the Connection Manager. This key has no effect on Smart Zero.

If set to 1, a standard user has permission to modify the general settings for this connection type using the Connection Manager.

This key has no effect on Smart Zero.

Sets the URL or IP address to connect to.

Sets the command to execute after the connection has been started.

Sets the command to execute after the connection has been stopped.

86 Appendix E Registry keys

Table E-5 root > ConnectionType > firefox (continued)

Registry key

root/ConnectionType/firefox/connections/

<UUID>/authorizations/user/edit root/ConnectionType/firefox/connections/

<UUID>/authorizations/user/execution root/ConnectionType/firefox/connections/

<UUID>/autoReconnect root/ConnectionType/firefox/connections/

<UUID>/autoReconnectDelay root/ConnectionType/firefox/connections/

<UUID>/autostart root/ConnectionType/firefox/connections/

<UUID>/autostartDelay root/ConnectionType/firefox/connections/

<UUID>/beforeStartingCommand root/ConnectionType/firefox/connections/

<UUID>/connectionEndAction root/ConnectionType/firefox/connections/

<UUID>/coord root/ConnectionType/firefox/connections/

<UUID>/dependConnectionId root/ConnectionType/firefox/connections/

<UUID>/enablePrintDialog root/ConnectionType/firefox/connections/

<UUID>/extraEnvValues/<UUID>/key root/ConnectionType/firefox/connections/

<UUID>/extraEnvValues/<UUID>/value root/ConnectionType/firefox/connections/

<UUID>/fallBackConnection root/ConnectionType/firefox/connections/

<UUID>/forbiddenFiles root/ConnectionType/firefox/connections/

<UUID>/fullscreen root/ConnectionType/firefox/connections/

<UUID>/hasDesktopIcon root/ConnectionType/firefox/connections/

<UUID>/intendedUse

Description

If set to 1, a standard user has permission to modify the connection settings for this connection.

If set to 1, a standard user has permission to execute this connection.

If set to 1, the connection will be restarted when it is closed or disconnected.

Sets the amount of time in seconds to wait before reconnecting the session. The default of 0 will cause the connection to reconnect immediately. This setting only takes effect when autoReconnect is set to 1.

If set to a value of 1–5, the connection will be started automatically after the system boots, with the value of 1 having the highest priority.

Sets the amount of time in seconds to wait before starting the connection after the system boots. The default of 0 will cause the connection to start immediately. This setting only takes effect when autostart is set to 1.

Sets the command to execute before the connection starts.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

If set to 1, the Print dialog in the web browser can be used.

Sets the name of an extra environment variable for use with the connection.

Sets the value of an extra environment variable for use with the connection.

Sets the fallback connection via its UUID.

This registry key only works when Allow connections to manage

their own settings is checked in the Web Browser Connection

General Settings Manager. The files listed in this registry key's value will be removed after a Web Browser connection is ended.

The file names should be separated by a comma, and a wildcard is supported. For example: *.rdf,cookies.sqlite

If set to 1, the web browser will start in full screen. If kioskMode is disabled, the browser UI is accessible in full screen mode.

If set to 1, the desktop icon for this connection is enabled. This key has no effect on Smart Zero.

Sets the intended usage of this Web Browser connection to

Citrix, RDP, or Internet.

root > ConnectionType 87

Table E-5 root > ConnectionType > firefox (continued)

Registry key

root/ConnectionType/firefox/connections/

<UUID>/kioskMode root/ConnectionType/firefox/connections/

<UUID>/label root/ConnectionType/firefox/connections/

<UUID>/startMode root/ConnectionType/firefox/connections/

<UUID>/waitForNetwork root/ConnectionType/firefox/coreSettings/

USBrelevant root/ConnectionType/firefox/coreSettings/ appName root/ConnectionType/firefox/coreSettings/ className root/ConnectionType/firefox/coreSettings/ editor root/ConnectionType/firefox/coreSettings/ generalSettingsEditor root/ConnectionType/firefox/coreSettings/ icon16Path root/ConnectionType/firefox/coreSettings/ icon32Path root/ConnectionType/firefox/coreSettings/ icon48Path root/ConnectionType/firefox/coreSettings/ label root/ConnectionType/firefox/coreSettings/ priorityInConnectionLists root/ConnectionType/firefox/coreSettings/ restartIdleTime root/ConnectionType/firefox/coreSettings/ serverRequired root/ConnectionType/firefox/coreSettings/ stopProcess

Description

If set to 1, the web browser will launch in kiosk mode, meaning that the web browser will start in full screen (even if fullscreen is set to 0) and the browser UI is inaccessible.

Sets the connection name that is displayed in the UI. On Smart

Zero, this will typically be set to Default Connection and does not display in the UI.

If set to the default focus and the connection is already started, the connection will be given focus. Otherwise, an error will be returned stating that the connection is already started.

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

Specifies if this connection type is USB-relevant. If it is, it might have a USB plugin for redirecting USB devices.

Sets the internal application name to use for this connection type.

This key should not need to be modified.

Sets the internal application class name to use for this connection type. This key should not need to be modified.

Sets the internal application name to use when the Connection

Manager is launched for this connection type. This key should not need to be modified.

Sets the internal application name to use when the General

Settings Manager is launched for this connection type. This key should not need to be modified.

Sets the path to the 16x16 pixel icon for this application.

Sets the path to the 32x32 pixel icon for this application.

Sets the path to the 48x48 pixel icon for this application.

Sets the name to display for this connection type in the UI.

Sets the priority of this connection type when it is displayed in the

Connection Manager and the Configuration Wizard that displays during initial setup. A higher value will move the connection type towards the top of the list. If set to 0, the connection type is hidden from Configuration Wizard and is shown last in Connection

Manager. Connections types with the same priority are listed in alphabetical order.

Sets the time in minutes before the web browser restarts when the system is not receiving user input. If set to 0, restart is disabled.

Sets whether a server name or address is unused, optional, or required for this connection type.

Sets the behavior that should occur when connection-mgr stop is called on this connection. By default this is close, which

88 Appendix E Registry keys

Table E-5 root > ConnectionType > firefox (continued)

Registry key

root/ConnectionType/firefox/coreSettings/ wrapperScript root/ConnectionType/firefox/general/ enableUserChanges root/ConnectionType/firefox/gui/

FirefoxManager/name root/ConnectionType/firefox/gui/

FirefoxManager/status root/ConnectionType/firefox/gui/

FirefoxManager/title root/ConnectionType/firefox/gui/

FirefoxManager/widgets/address root/ConnectionType/firefox/gui/

FirefoxManager/widgets/autoReconnect root/ConnectionType/firefox/gui/

FirefoxManager/widgets/autostart root/ConnectionType/firefox/gui/

FirefoxManager/widgets/enablePrintDialog root/ConnectionType/firefox/gui/

FirefoxManager/widgets/fallBackConnection root/ConnectionType/firefox/gui/

FirefoxManager/widgets/hasDesktopIcon root/ConnectionType/firefox/gui/

FirefoxManager/widgets/kioskMode

Description

will send a standard kill signal to the process. When set to kill, the process specified by appName will be forcefully killed. When set to custom, a custom execution script specified by wrapperScript will be executed with the argument stop to terminate the process gracefully.

Sets the script or binary to execute when launching this connection type. This is the primary script handling all connection settings and command line arguments for the connection. This key should not need to be modified.

If set to 1, the settings configured in the Firefox Preferences dialog will be saved after each session.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the URL widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Auto reconnect widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Auto start priority widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Enable print dialog widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Fallback Connection widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Show icon on desktop widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Enable kiosk mode widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If root > ConnectionType 89

Table E-5 root > ConnectionType > firefox (continued)

Registry key

root/ConnectionType/firefox/gui/

FirefoxManager/widgets/label root/ConnectionType/firefox/gui/

FirefoxManager/widgets/startMode root/ConnectionType/firefox/gui/

FirefoxManager/widgets/waitForNetwork

Description

set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Name widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Enable full screen widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Wait for network before connecting widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root > ConnectionType > freerdp

Table E-6 root > ConnectionType > freerdp

Registry key

root/ConnectionType/freerdp/authorizations/ user/add root/ConnectionType/freerdp/authorizations/ user/general root/ConnectionType/freerdp/connections/

<UUID>/ExtraArgs root/ConnectionType/freerdp/connections/

<UUID>/SingleSignOn root/ConnectionType/freerdp/connections/

<UUID>/address root/ConnectionType/freerdp/connections/

<UUID>/afterStoppedCommand root/ConnectionType/freerdp/connections/

<UUID>/application root/ConnectionType/freerdp/connections/

<UUID>/attachToConsole root/ConnectionType/freerdp/connections/

<UUID>/audioLatency root/ConnectionType/freerdp/connections/

<UUID>/authorizations/user/edit

Description

If set to 1, a standard user has permission to add a new connection of this type using the Connection Manager. This key has no effect on Smart Zero.

If set to 1, a standard user has permission to modify the general settings for this connection type using the Connection Manager.

This key has no effect on Smart Zero.

Specifies extra arguments for the xfreerdp client. Run xfreerdp --help from an X terminal to see all available arguments.

Sets the hostname or IP address to connect to. The port number can be appended on the end after a colon character. For example: servername:3389

Sets the command to execute after the connection has been stopped.

Specifies an alternate shell or application to run.

Sets the average milliseconds of offset between the audio stream and the display of corresponding video frames after decoding.

If set to 1, a standard user has permission to modify the connection settings for this connection.

90 Appendix E Registry keys

Table E-6 root > ConnectionType > freerdp (continued)

Registry key

root/ConnectionType/freerdp/connections/

<UUID>/authorizations/user/execution root/ConnectionType/freerdp/connections/

<UUID>/autoReconnect root/ConnectionType/freerdp/connections/

<UUID>/autoReconnectDelay root/ConnectionType/freerdp/connections/

<UUID>/autostart root/ConnectionType/freerdp/connections/

<UUID>/autostartDelay

Description

If set to 1, a standard user has permission to execute this connection.

If set to 1, the connection will be restarted when it is closed or disconnected.

Sets the amount of time in seconds to wait before reconnecting the session. The default of 0 will cause the connection to reconnect immediately. This setting only takes effect when autoReconnect is set to 1.

If set to a value of 1–5, the connection will be started automatically after the system boots, with the value of 1 having the highest priority.

Sets the amount of time in seconds to wait before starting the connection after the system boots. The default of 0 will cause the connection to start immediately. This setting only takes effect when autostart is set to 1.

Sets the command to execute before the connection starts.

root/ConnectionType/freerdp/connections/

<UUID>/beforeStartingCommand root/ConnectionType/freerdp/connections/

<UUID>/clipboardExtension root/ConnectionType/freerdp/connections/

<UUID>/compression root/ConnectionType/freerdp/connections/

<UUID>/dependConnectionId root/ConnectionType/freerdp/connections/

<UUID>/directory root/ConnectionType/freerdp/connections/

<UUID>/disableMMRwithRFX root/ConnectionType/freerdp/connections/

<UUID>/domain root/ConnectionType/freerdp/connections/

<UUID>/extraEnvValues/<UUID>/key root/ConnectionType/freerdp/connections/

<UUID>/extraEnvValues/<UUID>/value root/ConnectionType/freerdp/connections/

<UUID>/fallBackConnection root/ConnectionType/freerdp/connections/

<UUID>/frameAcknowledgeCount root/ConnectionType/freerdp/connections/

<UUID>/gatewayAddress root/ConnectionType/freerdp/connections/

<UUID>/gatewayDomain

If set to 1, clipboard functionality is enabled between different

RDP sessions and between RDP sessions and the local system.

If set to 1, compression of RDP data sent between the client and the server is enabled.

This registry key is either used internally or reserved for future use. The value should not be changed.

Specifies the startup directory where an alternate shell application is executed.

If set to 1, multimedia redirection is disabled if a valid RemoteFX session is established.

Sets the default domain to supply to the remote host during login.

If a domain is not specified, the default domain for the remote host will be used.

Sets the name of an extra environment variable for use with the connection.

Sets the value of an extra environment variable for use with the connection.

Sets the fallback connection via its UUID.

Sets the number of video frames the server can push without waiting for acknowledgement from the client. Lower numbers result in a more responsive desktop but lower frame rate. If set to

0, frame acknowledgement is not used in the client-server interactions.

Sets the RD Gateway server name or address.

Sets the default domain to supply to the RD Gateway during login.

Usually, this setting is used with kiosk-style applications where a generic user name is used to login. If root > ConnectionType 91

Table E-6 root > ConnectionType > freerdp (continued)

Registry key

root/ConnectionType/freerdp/connections/

<UUID>/gatewayEnabled root/ConnectionType/freerdp/connections/

<UUID>/gatewayPassword root/ConnectionType/freerdp/connections/

<UUID>/gatewayPort root/ConnectionType/freerdp/connections/

<UUID>/gatewayUser root/ConnectionType/freerdp/connections/

<UUID>/gatewayUsesSameCredentials root/ConnectionType/freerdp/connections/

<UUID>/hasDesktopIcon root/ConnectionType/freerdp/connections/

<UUID>/label root/ConnectionType/freerdp/connections/

<UUID>/loadBalanceInfo root/ConnectionType/freerdp/connections/

<UUID>/localPartitionRedirection root/ConnectionType/freerdp/connections/

<UUID>/loginfields/domain root/ConnectionType/freerdp/connections/

<UUID>/loginfields/password root/ConnectionType/freerdp/connections/

<UUID>/loginfields/rememberme root/ConnectionType/freerdp/connections/

<UUID>/loginfields/showpassword root/ConnectionType/freerdp/connections/

<UUID>/loginfields/smartcard

Description

gatewayUsesSameCredentials is to 1, this value is disabled.

If set to 1, RD Gateway is expected to be used.

Sets the default password to supply to the RD Gateway during login. This value is usually encrypted. Usually, this setting is used with kiosk-style applications where a generic user name is used to login. If gatewayUsesSameCredentials is to 1, this value is disabled.

Sets the port number to use when contacting the RDP server. This value can be left empty. The most common value is 443.

Sets the default user name to supply to the RD Gateway during login. Usually, this setting is used with kiosk-style applications where a generic user name is used to login. If gatewayUsesSameCredentials is to 1, this value is disabled.

If set to 1, the same credentials that are used to connect to the final server are used to connect to the RD Gateway.

If set to 1, the desktop icon for this connection is enabled. This key has no effect on Smart Zero.

Sets the connection name that is displayed in the UI. On Smart

Zero, this will typically be set to Default Connection and does not display in the UI.

This value is the load balancing cookie sent for brokering purposes to the server upon connection and corresponds to the loadbalanceinfo field in the .rdp file. By default, the value is empty.

If set to 1, the local non-USB storage partitions are redirected to the remote host via the Storage extension. If set to 0, the extension is disabled for non-USB storage partitions that are not used by HP ThinPro.

If set to 1, the Domain field is shown in the login dialog for the connection. If set to 2, the field is shown but disabled. If set to 0, the field is hidden.

If set to 1, the Password field is shown in the login dialog for the connection. If set to 2, the field is shown but disabled. If set to 0, the field is hidden.

If set to 1, the Remember me checkbox is shown in the login dialog for the connection. If set to 2, the checkbox is shown but disabled. If set to 0, the checkbox is hidden.

If set to 1, the Show password button is shown in the login dialog for the connection. If set to 2, the button is shown but disabled. If set to 0, the button is hidden.

If set to 1, the Smart card login checkbox is shown in the login dialog for the connection. If set to 2, the checkbox is shown but disabled. If set to 0, the checkbox is hidden. This checkbox might not appear if no smart card is detected, even if this option is enabled.

92 Appendix E Registry keys

Table E-6 root > ConnectionType > freerdp (continued)

Registry key

root/ConnectionType/freerdp/connections/

<UUID>/loginfields/username root/ConnectionType/freerdp/connections/

<UUID>/mouseMotionEvents root/ConnectionType/freerdp/connections/

<UUID>/offScreenBitmaps root/ConnectionType/freerdp/connections/

<UUID>/password root/ConnectionType/freerdp/connections/

<UUID>/perfFlagDesktopComposition root/ConnectionType/freerdp/connections/

<UUID>/perfFlagFontSmoothing root/ConnectionType/freerdp/connections/

<UUID>/perfFlagNoCursorSettings root/ConnectionType/freerdp/connections/

<UUID>/perfFlagNoCursorShadow root/ConnectionType/freerdp/connections/

<UUID>/perfFlagNoMenuAnimations root/ConnectionType/freerdp/connections/

<UUID>/perfFlagNoTheming root/ConnectionType/freerdp/connections/

<UUID>/perfFlagNoWallpaper root/ConnectionType/freerdp/connections/

<UUID>/perfFlagNoWindowDrag root/ConnectionType/freerdp/connections/

<UUID>/portMapping root/ConnectionType/freerdp/connections/

<UUID>/printerMapping

Description

If set to 1, the User Name field is shown in the login dialog for the connection. If set to 2, the field is shown but disabled. If set to 0, the field is hidden.

If set to 0, mouse motion events are not sent to the server. This can prevent some user feedback such as tooltips from functioning properly.

If set to 0, off-screen bitmaps are disabled. This can increase performance slightly but will cause blocks of the screen to update asynchronously, causing screen transitions to update nonuniformly.

Sets the default password to supply to the remote host during login. This value will be encrypted. Generally, this setting is used for kiosk-style applications where a generic password is used for login.

If set to 1, desktop composition (such as translucent borders) is allowed if supported by the server. Turning off desktop composition can improve performance for low-bandwidth connections. Generally, this only affects RemoteFX. If set to 2, the value is selected based on the thin client performance.

If set to 1, font smoothing is allowed if supported by the server and enabled. Turning off font smoothing can improve performance on low-bandwidth connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, cursor blinking is disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, mouse cursor shadows are disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, menu animations are disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, user interface themes are disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, the desktop wallpaper is disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, full-content window dragging is disabled, which can improve performance on low-bandwidth RDP connections. The window outline is used instead. If set to 2, the value is selected based on the thin client performance.

If set to 1, all serial and parallel ports are redirected to the remote host via the Ports extension. If set to 0, the extension is disabled.

If set to 1, all printers defined locally via CUPS are redirected to the remote host via the Printers extension. If set to 0, the extension is disabled. If set to 2, the USB printers are redirected as configured in the USB Manager.

root > ConnectionType 93

Table E-6 root > ConnectionType > freerdp (continued)

Registry key

root/ConnectionType/freerdp/connections/

<UUID>/rdWebFeed/autoStartSingleResource root/ConnectionType/freerdp/connections/

<UUID>/rdWebFeed/filter/<UUID>/alias root/ConnectionType/freerdp/connections/

<UUID>/rdWebFeed/filter/<UUID>/name root/ConnectionType/freerdp/connections/

<UUID>/rdWebFeed/keepResourcesWindowOpened root/ConnectionType/freerdp/connections/

<UUID>/rdp6Buffering root/ConnectionType/freerdp/connections/

<UUID>/rdp8Codecs root/ConnectionType/freerdp/connections/

<UUID>/rdpEncryption root/ConnectionType/freerdp/connections/

<UUID>/rdpH264Codec root/ConnectionType/freerdp/connections/

<UUID>/rdpProgressiveCodec root/ConnectionType/freerdp/connections/

<UUID>/remoteApp root/ConnectionType/freerdp/connections/

<UUID>/remoteDesktopService root/ConnectionType/freerdp/connections/

<UUID>/remoteFx root/ConnectionType/freerdp/connections/

<UUID>/seamlessWindow root/ConnectionType/freerdp/connections/

<UUID>/securityLevel

Description

If set to 1, and if only a single published resource (RemoteApp program or virtual desktop) is returned by the server, that resource will be started automatically.

Specifies the alias of a resource for the resource filter. RemoteApp and Desktop resources with a matching alias will be available to users.

Specifies the name of a resource for the resource filter.

RemoteApp and Desktop resources with a matching name will be available to users.

If set to 0, the resource selection window is closed automatically after a resource has started. If set to 1, the resource selection window is kept open after resources have started. This allows a user to start several resources before closing the resource selection window.

If set to 1, non-RemoteFX graphics performance is increased at the cost of less frequent screen updates.

If set to 1, RDP 8 codecs are used if available. This setting should be disabled only in the case of a defect specific to RDP 8 codecs.

Disabling this setting might also disable more advanced codecs.

If set to 1, standard RDP encryption is used to encrypt all data between the client and the server.

If set to 1, RDP 8 H.264 codecs are used if available. This setting has known visual errors, particularly in multi-monitor configurations, and should be considered experimental and unsupported. Enabling this setting simply advises the server that the thin client supports H.264 for desktop display. The server must also support H.264, and the server makes the final decision on what codecs are used. This setting affects only the desktop codecs. It does not affect multimedia redirection codecs.

If set to 1, RDP 8 progressive codecs are used if available. This setting should be disabled only in the case of a defect specific to

RDP 8 progressive codecs. Disabling this setting might also disable more advanced codecs.

Specifies the name of an available application to run in Remote

Application Integrated Locally (RAIL) mode.

If set to Remote Computer, a direct RDP connection to a remote computer is done. If set to RD Web Access, a connection to an RD Web Access service is done first to retrieve a feed of the published RemoteApp resources.

If set to 1, RemoteFX in the style of RDP 7.1 is used if available.

This setting is deprecated and might disappear in a future release of HP ThinPro. This setting should be disabled only in the case of a defect specific to RemoteFX protocol. Disabling this setting might also disable more advanced codecs.

If set to 1, window decorations are disabled. This can be desirable in a multi-monitor configuration to allow the connection to be set to the size of the primary monitor.

Sets the certificate security level. If set to 0, all connections are allowed. If set to 1, remembered hosts are checked and a warning dialog is shown if verification is not passed. If set to 2,

94 Appendix E Registry keys

Table E-6 root > ConnectionType > freerdp (continued)

Registry key

root/ConnectionType/freerdp/connections/

<UUID>/sendHostname root/ConnectionType/freerdp/connections/

<UUID>/showConnectionGraph root/ConnectionType/freerdp/connections/

<UUID>/smartcard root/ConnectionType/freerdp/connections/

<UUID>/sound root/ConnectionType/freerdp/connections/

<UUID>/startMode root/ConnectionType/freerdp/connections/

<UUID>/timeoutError root/ConnectionType/freerdp/connections/

<UUID>/timeoutRecovery root/ConnectionType/freerdp/connections/

<UUID>/timeoutWarning root/ConnectionType/freerdp/connections/

<UUID>/timeoutWarningDialog

Description

remembered hosts are not checked and a warning dialog is shown if verification is not passed. If set to 3, all insecure connections are refused.

Sets the thin client hostname that is sent to the remote host. If left blank, the system hostname is sent. The registry key root/

ConnectionType/freerdp/general/sendHostname must be set to hostname for this key to be used.

This is a diagnostic function. If set to 1, when the session starts, a separate program will be started to graph the connection's health.

If set to 1, local smartcard authentication to the remote host is allowed. Currently, this will disable Network Level Authentication

(NLA).

If set to 1, the playback and recording devices are redirected to the remote host via the Audio extension. If set to 0, the extension is disabled. If set to 2, the USB audio devices are redirected as configured in the USB Manager. Generally, HP recommends setting this value to 1 so that high-level audio redirection is used. This will improve audio quality and ensure that client audio redirected via other extensions (such as

Multimedia Redirection) matches local audio settings.

If set to the default focus and the connection is already started, the connection will be given focus. Otherwise, an error will be returned stating that the connection is already started.

Sets the number of milliseconds to wait after losing the connection before giving up on reconnecting with the server. If set to 0, reconnection is attempted forever.

Sets the number of milliseconds to wait after losing the connection for networking to recover without trying a forced reconnect.

Sets the number of milliseconds to wait after losing the connection before warning the user that the connection has been lost.

If set to 1, when an end-to-end connection drop is detected, a dialog is displayed and the screen will turn grayscale. Otherwise, messages are written to the connection log and the session freezes.

If set to 1, end-to-end connection health checks are done.

root/ConnectionType/freerdp/connections/

<UUID>/timeoutsEnabled root/ConnectionType/freerdp/connections/

<UUID>/usbMiscRedirection root/ConnectionType/freerdp/connections/

<UUID>/usbStorageRedirection

If set to 0, redirection is disabled for all other USB devices except those handled by sound, printerMapping, portMapping, usbStorageRedirection, and localPartitionRedirection. If set to 2, all other USB devices are redirected to the remote host as configured in the USB

Manager.

If set to 1, USB storage devices are redirected to the remote host via the Storage extension. If set to 0, the extension is disabled.

If set to 2, USB storage devices are redirected as configured in the

USB Manager.

root > ConnectionType 95

Table E-6 root > ConnectionType > freerdp (continued)

Registry key

root/ConnectionType/freerdp/connections/

<UUID>/username root/ConnectionType/freerdp/connections/

<UUID>/waitForNetwork root/ConnectionType/freerdp/connections/

<UUID>/windowMode root/ConnectionType/freerdp/connections/

<UUID>/windowSizeHeight root/ConnectionType/freerdp/connections/

<UUID>/windowSizePercentage root/ConnectionType/freerdp/connections/

<UUID>/windowSizeWidth root/ConnectionType/freerdp/connections/

<UUID>/windowType root/ConnectionType/freerdp/connections/

<UUID>/xkbLayoutId root/ConnectionType/freerdp/coreSettings/

USBrelevant root/ConnectionType/freerdp/coreSettings/ appName root/ConnectionType/freerdp/coreSettings/ className root/ConnectionType/freerdp/coreSettings/ disableLinkDropWarning root/ConnectionType/freerdp/coreSettings/ editor root/ConnectionType/freerdp/coreSettings/ generalSettingsEditor root/ConnectionType/freerdp/coreSettings/ icon16Path root/ConnectionType/freerdp/coreSettings/ icon32Path

Description

Sets the default user name to supply to the remote host during login. Generally, this setting is used for kiosk-style applications where a generic user name is used for login.

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

If set to Remote Application, RDP will run in Remote

Application Integrated Locally (RAIL) mode. This requires that the

RemoteApp server allows the desired application to run as a remote application. The application will be displayed in a separate window within the desktop environment, making it look like the application is part of the local system. Also see the remoteApp registry key. If set to Alternate Shell, a non-standard shell is invoked. Also see the application and directory registry keys.

Sets an XKB layout ID for bypassing the system keyboard. To see the list of available IDs, enter the following command in an X terminal: xfreerdp --kbd-list.

Specifies if this connection type is USB-relevant. If it is, it might have a USB plugin for redirecting USB devices.

Sets the internal application name to use for this connection type.

This key should not need to be modified.

Sets the internal application class name to use for this connection type. This key should not need to be modified.

If set to 1, the operating system does not generate a dialog indicating that networking is down because the connection protocol handles such situations.

Sets the internal application name to use when the Connection

Manager is launched for this connection type. This key should not need to be modified.

Sets the internal application name to use when the General

Settings Manager is launched for this connection type. This key should not need to be modified.

Sets the path to the 16x16 pixel icon for this application.

Sets the path to the 32x32 pixel icon for this application.

96 Appendix E Registry keys

Table E-6 root > ConnectionType > freerdp (continued)

Registry key Description

root/ConnectionType/freerdp/coreSettings/ icon48Path root/ConnectionType/freerdp/coreSettings/ initialConnectionTimeout root/ConnectionType/freerdp/coreSettings/ label root/ConnectionType/freerdp/coreSettings/ priorityInConnectionLists

Sets the path to the 48x48 pixel icon for this application.

Sets the number of seconds to wait for an initial response from the RDP server before giving up.

Sets the name to display for this connection type in the UI.

root/ConnectionType/freerdp/coreSettings/ stopProcess root/ConnectionType/freerdp/coreSettings/ watchPid

Sets the priority of this connection type when it is displayed in the

Connection Manager and the Configuration Wizard that displays during initial setup. A higher value will move the connection type towards the top of the list. If set to 0, the connection type is hidden from Configuration Wizard and is shown last in Connection

Manager. Connections types with the same priority are listed in alphabetical order.

Sets the behavior that should occur when connection-mgr stop is called on this connection. By default this is close, which will send a standard kill signal to the process. When set to kill, the process specified by appName will be forcefully killed. When set to custom, a custom execution script specified by wrapperScript will be executed with the argument stop to terminate the process gracefully.

If set to 1, the connection is monitored under the name specified by appName. This key should not need to be modified.

root/ConnectionType/freerdp/coreSettings/ wrapperScript root/ConnectionType/freerdp/general/ autoReconnectDialogTimeout root/ConnectionType/freerdp/general/ disablePasswordChange

Sets the script or binary to execute when launching this connection type. This is the primary script handling all connection settings and command line arguments for the connection. This key should not need to be modified.

If autoReconnect is enabled, this key sets the number of seconds before timing out any error dialogs for the connection. If set to 0, the dialogs wait indefinitely for user interaction.

When a remote login fails due to bad credentials, the user is presented with a button that brings up a dialog for updating their password. If this key is set is 1, that button and dialog are not displayed.

root/ConnectionType/freerdp/general/enableMMR If set to 1, the Multimedia Redirection plugin is enabled, causing supported codecs played through Windows Media Player to be redirected to the client. This will greatly improve full screen and high definition video playback for codecs such as WMV9, VC1, and MPEG4.

root/ConnectionType/freerdp/general/ preferredAudio root/ConnectionType/freerdp/general/ rdWebFeedUrlPattern

Sets the default audio backend for high-level audio redirection

(both in and out).

Sets the pattern used to build the RD Web Access URL. The host of the URL is replaced by the value of the connection's Address field.

This pattern is not used when the address is already a URL.

root/ConnectionType/freerdp/general/ sendHostname

If set to hostname, the system hostname is sent to the remote host. This is typically used to identify the thin client associated with a particular RDP session. The sent hostname can be overridden using sendHostname in the connection-specific settings. If set to mac, the MAC address of the first available network adapter is sent instead of the hostname.

root > ConnectionType 97

Table E-6 root > ConnectionType > freerdp (continued)

Registry key

root/ConnectionType/freerdp/general/ serialPortsDriver root/ConnectionType/freerdp/general/ serialPortsPermissive

Description

This setting ensures a better compatibility with the expected underlying Windows driver SerCx2.sys, SerCx.sys, or Serial.sys.

If set to 1, errors for unsupported features will be ignored.

root > ConnectionType > ssh

Table E-7 root > ConnectionType > ssh

Registry key

root/ConnectionType/ssh/authorizations/ user/add root/ConnectionType/ssh/authorizations/user/ general root/ConnectionType/ssh/connections/<UUID>/ address root/ConnectionType/ssh/connections/<UUID>/ afterStartedCommand root/ConnectionType/ssh/connections/<UUID>/ afterStoppedCommand root/ConnectionType/ssh/connections/<UUID>/ application root/ConnectionType/ssh/connections/<UUID>/ authorizations/user/edit root/ConnectionType/ssh/connections/<UUID>/ authorizations/user/execution root/ConnectionType/ssh/connections/<UUID>/ autoReconnect root/ConnectionType/ssh/connections/<UUID>/ autoReconnectDelay root/ConnectionType/ssh/connections/<UUID>/ autostart root/ConnectionType/ssh/connections/<UUID>/ autostartDelay root/ConnectionType/ssh/connections/<UUID>/ backgroundColor root/ConnectionType/ssh/connections/<UUID>/ beforeStartingCommand

Description

If set to 1, a standard user has permission to add a new connection of this type using the Connection Manager. This key has no effect on Smart Zero.

If set to 1, a standard user has permission to modify the general settings for this connection type using the Connection Manager.

This key has no effect on Smart Zero.

Sets the hostname or IP address to connect to.

Sets the command to execute after the connection has been started.

Sets the command to execute after the connection has been stopped.

Specifies the application to run.

If set to 1, a standard user has permission to modify the connection settings for this connection.

If set to 1, a standard user has permission to execute this connection.

If set to 1, the connection will be restarted when it is closed or disconnected.

Sets the amount of time in seconds to wait before reconnecting the session. The default of 0 will cause the connection to reconnect immediately. This setting only takes effect when autoReconnect is set to 1.

If set to a value of 1–5, the connection will be started automatically after the system boots, with the value of 1 having the highest priority.

Sets the amount of time in seconds to wait before starting the connection after the system boots. The default of 0 will cause the connection to start immediately. This setting only takes effect when autostart is set to 1.

Sets the background color for the connection.

Sets the command to execute before the connection starts.

98 Appendix E Registry keys

Table E-7 root > ConnectionType > ssh (continued)

Registry key

root/ConnectionType/ssh/connections/<UUID>/ compression root/ConnectionType/ssh/connections/<UUID>/ connectionEndAction root/ConnectionType/ssh/connections/<UUID>/ coord root/ConnectionType/ssh/connections/<UUID>/ dependConnectionId root/ConnectionType/ssh/connections/<UUID>/ extraEnvValues/<UUID>/key root/ConnectionType/ssh/connections/<UUID>/ extraEnvValues/<UUID>/value root/ConnectionType/ssh/connections/<UUID>/ fallBackConnection root/ConnectionType/ssh/connections/<UUID>/ font root/ConnectionType/ssh/connections/<UUID>/ foregroundColor root/ConnectionType/ssh/connections/<UUID>/ fork root/ConnectionType/ssh/connections/<UUID>/ hasDesktopIcon root/ConnectionType/ssh/connections/<UUID>/ isInMenu root/ConnectionType/ssh/connections/<UUID>/ label

Description

Enables compression for an SSH connection.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the name of an extra environment variable for use with the connection.

Sets the value of an extra environment variable for use with the connection.

Sets the fallback connection via its UUID.

Sets the font size for the connection.

Sets the foreground color for the connection.

root/ConnectionType/ssh/connections/<UUID>/ port root/ConnectionType/ssh/connections/<UUID>/ startMode root/ConnectionType/ssh/connections/

<UUID>/tty root/ConnectionType/ssh/connections/<UUID>/ username root/ConnectionType/ssh/connections/<UUID>/ waitForNetwork root/ConnectionType/ssh/connections/

<UUID>/x11 root/ConnectionType/ssh/coreSettings/

USBrelevant

If set to 1, the Fork into background option is enabled for the connection.

If set to 1, the desktop icon for this connection is enabled. This key has no effect on Smart Zero.

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the connection name that is displayed in the UI. On Smart

Zero, this will typically be set to Default Connection and does not display in the UI.

Sets the port number to use when contacting the SSH server. The default is 22.

If set to the default focus and the connection is already started, the connection will be given focus. Otherwise, an error will be returned stating that the connection is already started.

If set to 1, the Force TTY allocation option is enabled for the connection.

Sets the default user name to supply to the remote host during login. Generally, this setting is used for kiosk-style applications where a generic user name is used for login.

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

If set to 1, the X11 connection forwarding option is enabled for the connection.

Specifies if this connection type is USB-relevant. If it is, it might have a USB plugin for redirecting USB devices.

root > ConnectionType 99

Table E-7 root > ConnectionType > ssh (continued)

Registry key Description

root/ConnectionType/ssh/coreSettings/appName Sets the internal application name to use for this connection type.

This key should not need to be modified.

root/ConnectionType/ssh/coreSettings/ className root/ConnectionType/ssh/coreSettings/editor

Sets the internal application class name to use for this connection type. This key should not need to be modified.

Sets the internal application name to use when the Connection

Manager is launched for this connection type. This key should not need to be modified.

Sets the path to the 16x16 pixel icon for this application.

root/ConnectionType/ssh/coreSettings/ icon16Path root/ConnectionType/ssh/coreSettings/ icon32Path

Sets the path to the 32x32 pixel icon for this application.

Sets the path to the 48x48 pixel icon for this application.

root/ConnectionType/ssh/coreSettings/ icon48Path root/ConnectionType/ssh/coreSettings/label root/ConnectionType/ssh/coreSettings/ priorityInConnectionLists root/ConnectionType/ssh/coreSettings/ serverRequired

Sets the name to display for this connection type in the UI.

Sets the priority of this connection type when it is displayed in the

Connection Manager and the Configuration Wizard that displays during initial setup. A higher value will move the connection type towards the top of the list. If set to 0, the connection type is hidden from Configuration Wizard and is shown last in Connection

Manager. Connections types with the same priority are listed in alphabetical order.

Sets whether a server name or address is unused, optional, or required for this connection type.

root/ConnectionType/ssh/coreSettings/ stopProcess

Sets the behavior that should occur when connection-mgr stop is called on this connection. By default this is close, which will send a standard kill signal to the process. When set to kill, the process specified by appName will be forcefully killed. When set to custom, a custom execution script specified by wrapperScript will be executed with the argument stop to terminate the process gracefully.

root/ConnectionType/ssh/coreSettings/watchPid If set to 1, the connection is monitored under the name specified by appName. This key should not need to be modified.

root/ConnectionType/ssh/coreSettings/ wrapperScript

Sets the script or binary to execute when launching this connection type. This is the primary script handling all connection settings and command line arguments for the connection. This key should not need to be modified.

root/ConnectionType/ssh/gui/SshManager/name This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/ssh/gui/SshManager/status This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/ssh/gui/SshManager/title This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/ssh/gui/SshManager/ widgets/address

Controls the state of the Address widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

100 Appendix E Registry keys

Table E-7 root > ConnectionType > ssh (continued)

Registry key

root/ConnectionType/ssh/gui/SshManager/ widgets/application root/ConnectionType/ssh/gui/SshManager/ widgets/autoReconnect root/ConnectionType/ssh/gui/SshManager/ widgets/autostart root/ConnectionType/ssh/gui/SshManager/ widgets/backgroundColor root/ConnectionType/ssh/gui/SshManager/ widgets/compression root/ConnectionType/ssh/gui/SshManager/ widgets/fallBackConnection root/ConnectionType/ssh/gui/SshManager/ widgets/font root/ConnectionType/ssh/gui/SshManager/ widgets/foregroundColor root/ConnectionType/ssh/gui/SshManager/ widgets/fork root/ConnectionType/ssh/gui/SshManager/ widgets/hasDesktopIcon

Description

Controls the state of the Run application widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Auto reconnect widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Auto start priority widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Background color widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Compression widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Fallback Connection widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Font widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Foreground color widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Fork into background widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Show icon on desktop widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root > ConnectionType 101

Table E-7 root > ConnectionType > ssh (continued)

Registry key

root/ConnectionType/ssh/gui/SshManager/ widgets/isInMenu root/ConnectionType/ssh/gui/SshManager/ widgets/label root/ConnectionType/ssh/gui/SshManager/ widgets/port root/ConnectionType/ssh/gui/SshManager/ widgets/tty root/ConnectionType/ssh/gui/SshManager/ widgets/username root/ConnectionType/ssh/gui/SshManager/ widgets/waitForNetwork root/ConnectionType/ssh/gui/SshManager/ widgets/x11

Description

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Name widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Port widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Force TTY allocation widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the User name widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Wait for network before connecting widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the X11 connection forwarding widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to readonly, the widget is visible in the read-only state.

root > ConnectionType > teemtalk

Table E-8 root > ConnectionType > teemtalk

Registry key

root/ConnectionType/teemtalk/authorizations/ user/add root/ConnectionType/teemtalk/authorizations/ user/general root/ConnectionType/teemtalk/connections/

<UUID>/afterStartedCommand root/ConnectionType/teemtalk/connections/

<UUID>/afterStoppedCommand

Description

If set to 1, a standard user has permission to add a new connection of this type using the Connection Manager. This key has no effect on Smart Zero.

If set to 1, a standard user has permission to modify the general settings for this connection type using the Connection Manager.

This key has no effect on Smart Zero.

Sets the command to execute after the connection has been started.

Sets the command to execute after the connection has been stopped.

102 Appendix E Registry keys

Table E-8 root > ConnectionType > teemtalk (continued)

Registry key

root/ConnectionType/teemtalk/connections/

<UUID>/authorizations/user/edit root/ConnectionType/teemtalk/connections/

<UUID>/authorizations/user/execution root/ConnectionType/teemtalk/connections/

<UUID>/autoReconnect root/ConnectionType/teemtalk/connections/

<UUID>/autostart

Description

If set to 1, a standard user has permission to modify the connection settings for this connection.

If set to 1, a standard user has permission to execute this connection.

If set to 1, the connection will be restarted when it is closed or disconnected.

If set to a value of 1–5, the connection will be started automatically after the system boots, with the value of 1 having the highest priority.

Sets the command to execute before the connection starts.

root/ConnectionType/teemtalk/connections/

<UUID>/beforeStartingCommand root/ConnectionType/teemtalk/connections/

<UUID>/connectionEndAction root/ConnectionType/teemtalk/connections/

<UUID>/coord root/ConnectionType/teemtalk/connections/

<UUID>/dependConnectionId root/ConnectionType/teemtalk/connections/

<UUID>/extraEnvValues/<UUID>/key root/ConnectionType/teemtalk/connections/

<UUID>/extraEnvValues/<UUID>/value root/ConnectionType/teemtalk/connections/

<UUID>/fallBackConnection root/ConnectionType/teemtalk/connections/

<UUID>/hasDesktopIcon root/ConnectionType/teemtalk/connections/

<UUID>/isInMenu root/ConnectionType/teemtalk/connections/

<UUID>/label root/ConnectionType/teemtalk/connections/

<UUID>/startMode root/ConnectionType/teemtalk/connections/

<UUID>/systembeep root/ConnectionType/teemtalk/connections/

<UUID>/ttsName root/ConnectionType/teemtalk/connections/

<UUID>/waitForNetwork

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the name of an extra environment variable for use with the connection.

Sets the value of an extra environment variable for use with the connection.

Sets the fallback connection via its UUID.

If set to 1, the desktop icon for this connection is enabled. This key has no effect on Smart Zero.

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the connection name that is displayed in the UI. On Smart

Zero, this will typically be set to Default Connection and does not display in the UI.

If set to the default focus and the connection is already started, the connection will be given focus. Otherwise, an error will be returned stating that the connection is already started.

If set to 1, system beep is enabled for the connection.

Sets the TeemTalk profile name.

root/ConnectionType/teemtalk/coreSettings/

USBrelevant root/ConnectionType/teemtalk/coreSettings/ appName

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

Specifies if this connection type is USB-relevant. If it is, it might have a USB plugin for redirecting USB devices.

Sets the internal application name to use for this connection type.

This key should not need to be modified.

root > ConnectionType 103

Table E-8 root > ConnectionType > teemtalk (continued)

Registry key

root/ConnectionType/teemtalk/coreSettings/ className root/ConnectionType/teemtalk/coreSettings/ editor root/ConnectionType/teemtalk/coreSettings/ generalSettingsEditor

Description

Sets the internal application class name to use for this connection type. This key should not need to be modified.

Sets the internal application name to use when the Connection

Manager is launched for this connection type. This key should not need to be modified.

Sets the internal application name to use when the General

Settings Manager is launched for this connection type. This key should not need to be modified.

Sets the path to the 16x16 pixel icon for this application.

root/ConnectionType/teemtalk/coreSettings/ icon16Path root/ConnectionType/teemtalk/coreSettings/ icon32Path root/ConnectionType/teemtalk/coreSettings/ icon48Path root/ConnectionType/teemtalk/coreSettings/ label root/ConnectionType/teemtalk/coreSettings/ priorityInConnectionLists

Sets the path to the 32x32 pixel icon for this application.

Sets the path to the 48x48 pixel icon for this application.

Sets the name to display for this connection type in the UI.

root/ConnectionType/teemtalk/coreSettings/ serverRequired root/ConnectionType/teemtalk/coreSettings/ stopProcess root/ConnectionType/teemtalk/coreSettings/ wrapperScript root/ConnectionType/teemtalk/gui/

TeemtalkManager/name root/ConnectionType/teemtalk/gui/

TeemtalkManager/status root/ConnectionType/teemtalk/gui/

TeemtalkManager/title root/ConnectionType/teemtalk/gui/

TeemtalkManager/widgets/autoReconnect

Sets the priority of this connection type when it is displayed in the

Connection Manager and the Configuration Wizard that displays during initial setup. A higher value will move the connection type towards the top of the list. If set to 0, the connection type is hidden from Configuration Wizard and is shown last in Connection

Manager. Connections types with the same priority are listed in alphabetical order.

Sets whether a server name or address is unused, optional, or required for this connection type.

Sets the behavior that should occur when connection-mgr stop is called on this connection. By default this is close, which will send a standard kill signal to the process. When set to kill, the process specified by appName will be forcefully killed. When set to custom, a custom execution script specified by wrapperScript will be executed with the argument stop to terminate the process gracefully.

Sets the script or binary to execute when launching this connection type. This is the primary script handling all connection settings and command line arguments for the connection. This key should not need to be modified.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Auto reconnect widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

104 Appendix E Registry keys

Table E-8 root > ConnectionType > teemtalk (continued)

Registry key

root/ConnectionType/teemtalk/gui/

TeemtalkManager/widgets/autostart root/ConnectionType/teemtalk/gui/

TeemtalkManager/widgets/hasDesktopIcon root/ConnectionType/teemtalk/gui/

TeemtalkManager/widgets/isInMenu root/ConnectionType/teemtalk/gui/

TeemtalkManager/widgets/label root/ConnectionType/teemtalk/gui/

TeemtalkManager/widgets/waitForNetwork

Description

Controls the state of the Auto start priority widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Show icon on desktop widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Name widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Wait for network before connecting widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root > ConnectionType > telnet

Table E-9 root > ConnectionType > telnet

Registry key

root/ConnectionType/telnet/authorizations/ user/add root/ConnectionType/telnet/authorizations/ user/general root/ConnectionType/telnet/connections/

<UUID>/address root/ConnectionType/telnet/connections/

<UUID>/afterStartedCommand root/ConnectionType/telnet/connections/

<UUID>/afterStoppedCommand root/ConnectionType/telnet/connections/

<UUID>/authorizations/user/edit root/ConnectionType/telnet/connections/

<UUID>/authorizations/user/execution root/ConnectionType/telnet/connections/

<UUID>/autoReconnect

Description

If set to 1, a standard user has permission to add a new connection of this type using the Connection Manager. This key has no effect on Smart Zero.

If set to 1, a standard user has permission to modify the general settings for this connection type using the Connection Manager.

This key has no effect on Smart Zero.

Sets the hostname or IP address to connect to.

Sets the command to execute after the connection has been started.

Sets the command to execute after the connection has been stopped.

If set to 1, a standard user has permission to modify the connection settings for this connection.

If set to 1, a standard user has permission to execute this connection.

If set to 1, the connection will be restarted when it is closed or disconnected.

root > ConnectionType 105

Table E-9 root > ConnectionType > telnet (continued)

Registry key

root/ConnectionType/telnet/connections/

<UUID>/autostart root/ConnectionType/telnet/connections/

<UUID>/backgroundColor root/ConnectionType/telnet/connections/

<UUID>/beforeStartingCommand root/ConnectionType/telnet/connections/

<UUID>/connectionEndAction root/ConnectionType/telnet/connections/

<UUID>/coord root/ConnectionType/telnet/connections/

<UUID>/dependConnectionId root/ConnectionType/telnet/connections/

<UUID>/extraEnvValues/<UUID>/key root/ConnectionType/telnet/connections/

<UUID>/extraEnvValues/<UUID>/value root/ConnectionType/telnet/connections/

<UUID>/fallBackConnection root/ConnectionType/telnet/connections/

<UUID>/font root/ConnectionType/telnet/connections/

<UUID>/foregroundColor root/ConnectionType/telnet/connections/

<UUID>/hasDesktopIcon root/ConnectionType/telnet/connections/

<UUID>/label root/ConnectionType/telnet/connections/

<UUID>/locale root/ConnectionType/telnet/connections/

<UUID>/port root/ConnectionType/telnet/connections/

<UUID>/startMode root/ConnectionType/telnet/connections/

<UUID>/waitForNetwork root/ConnectionType/telnet/coreSettings/

USBrelevant root/ConnectionType/telnet/coreSettings/ appName root/ConnectionType/telnet/coreSettings/ className

Description

If set to a value of 1–5, the connection will be started automatically after the system boots, with the value of 1 having the highest priority.

Sets the background color for the connection.

Sets the command to execute before the connection starts.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the name of an extra environment variable for use with the connection.

Sets the value of an extra environment variable for use with the connection.

Sets the fallback connection via its UUID.

Sets the font size for the connection.

Sets the foreground color for the connection.

If set to 1, the desktop icon for this connection is enabled. This key has no effect on Smart Zero.

Sets the connection name that is displayed in the UI. On Smart

Zero, this will typically be set to Default Connection and does not display in the UI.

Sets the locale of the connection.

Sets the port number to use when contacting the server. The default is 23.

If set to the default focus and the connection is already started, the connection will be given focus. Otherwise, an error will be returned stating that the connection is already started.

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

Specifies if this connection type is USB-relevant. If it is, it might have a USB plugin for redirecting USB devices.

Sets the internal application name to use for this connection type.

This key should not need to be modified.

Sets the internal application class name to use for this connection type. This key should not need to be modified.

106 Appendix E Registry keys

Table E-9 root > ConnectionType > telnet (continued)

Registry key Description

root/ConnectionType/telnet/coreSettings/ editor root/ConnectionType/telnet/coreSettings/ generalSettingsEditor

Sets the internal application name to use when the Connection

Manager is launched for this connection type. This key should not need to be modified.

Sets the internal application name to use when the General

Settings Manager is launched for this connection type. This key should not need to be modified.

Sets the path to the 16x16 pixel icon for this application.

root/ConnectionType/telnet/coreSettings/ icon16Path root/ConnectionType/telnet/coreSettings/ icon32Path

Sets the path to the 32x32 pixel icon for this application.

root/ConnectionType/telnet/coreSettings/ icon48Path

Sets the path to the 48x48 pixel icon for this application.

root/ConnectionType/telnet/coreSettings/label

Sets the name to display for this connection type in the UI.

root/ConnectionType/telnet/coreSettings/ priorityInConnectionLists

Sets the priority of this connection type when it is displayed in the

Connection Manager and the Configuration Wizard that displays during initial setup. A higher value will move the connection type towards the top of the list. If set to 0, the connection type is hidden from Configuration Wizard and is shown last in Connection

Manager. Connections types with the same priority are listed in alphabetical order.

root/ConnectionType/telnet/coreSettings/ serverRequired root/ConnectionType/telnet/coreSettings/ stopProcess root/ConnectionType/telnet/coreSettings/ wrapperScript

Sets whether a server name or address is unused, optional, or required for this connection type.

Sets the behavior that should occur when connection-mgr stop is called on this connection. By default this is close, which will send a standard kill signal to the process. When set to kill, the process specified by appName will be forcefully killed. When set to custom, a custom execution script specified by wrapperScript will be executed with the argument stop to terminate the process gracefully.

Sets the script or binary to execute when launching this connection type. This is the primary script handling all connection settings and command line arguments for the connection. This key should not need to be modified.

root/ConnectionType/telnet/gui/TelnetManager/ name

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/telnet/gui/TelnetManager/ status

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/telnet/gui/TelnetManager/ title

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/address

Controls the state of the Address widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/autoReconnect

Controls the state of the Auto reconnect widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to root > ConnectionType 107

Table E-9 root > ConnectionType > telnet (continued)

Registry key Description

inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/autostart

Controls the state of the Auto start priority widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/backgroundColor

Controls the state of the Background color widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/fallBackConnection

Controls the state of the Fallback Connection widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/foregroundColor

Controls the state of the Foreground color widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/hasDesktopIcon

Controls the state of the Show icon on desktop widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/label

Controls the state of the Name widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/port

Controls the state of the Port widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/telnet/gui/TelnetManager/ widgets/waitForNetwork

Controls the state of the Wait for network before connecting widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

108 Appendix E Registry keys

root > ConnectionType > view

Table E-10 root > ConnectionType > view

Registry key Description

root/ConnectionType/view/authorizations/ user/add root/ConnectionType/view/authorizations/user/ general

If set to 1, a standard user has permission to add a new connection of this type using the Connection Manager. This key has no effect on Smart Zero.

If set to 1, a standard user has permission to modify the general settings for this connection type using the Connection Manager.

This key has no effect on Smart Zero.

root/ConnectionType/view/connections/<UUID>/

ExtraArgs

Specifies extra arguments for the VMware Horizon View client.

Run view_client --help or vmware-view --help from an X terminal to see all available arguments.

root/ConnectionType/view/connections/<UUID>/

SingleSignOn root/ConnectionType/view/connections/<UUID>/ afterStartedCommand root/ConnectionType/view/connections/<UUID>/ afterStoppedCommand root/ConnectionType/view/connections/<UUID>/ appInMenu root/ConnectionType/view/connections/<UUID>/ appOnDesktop root/ConnectionType/view/connections/<UUID>/ applicationSize

Sets the command to execute after the connection has been started.

Sets the command to execute after the connection has been stopped.

If set to 1, all applications for this connection will be displayed in the taskbar menu.

If set to 1, all applications for this connection will be displayed on the desktop.

Sets the size in which the VMware Horizon View client will launch applications.

root/ConnectionType/view/connections/<UUID>/ attachToConsole root/ConnectionType/view/connections/<UUID>/ authorizations/user/edit root/ConnectionType/view/connections/<UUID>/ authorizations/user/execution root/ConnectionType/view/connections/<UUID>/ autoReconnect

If set to 1, a standard user has permission to modify the connection settings for this connection.

If set to 1, a standard user has permission to execute this connection.

root/ConnectionType/view/connections/<UUID>/ autoReconnectDelay root/ConnectionType/view/connections/<UUID>/ automaticLogin

If set to 1, the connection will be restarted when it is closed or disconnected.

Sets the amount of time in seconds to wait before reconnecting the session. The default of 0 will cause the connection to reconnect immediately. This setting only takes effect when autoReconnect is set to 1.

If set to 1, the VMware Horizon View client will attempt to log in automatically if all fields are provided. If set to 0, users have to click Connect manually in the VMware Horizon View client, log in, and select a desktop.

root/ConnectionType/view/connections/<UUID>/ autostart root/ConnectionType/view/connections/<UUID>/ autostartDelay

If set to a value of 1–5, the connection will be started automatically after the system boots, with the value of 1 having the highest priority.

Sets the amount of time in seconds to wait before starting the connection after the system boots. The default of 0 will cause the connection to start immediately. This setting only takes effect when autostart is set to 1.

root > ConnectionType 109

Table E-10 root > ConnectionType > view (continued)

Registry key

root/ConnectionType/view/connections/<UUID>/ beforeStartingCommand root/ConnectionType/view/connections/<UUID>/ closeAfterDisconnect

Description

Sets the command to execute before the connection starts.

root/ConnectionType/view/connections/<UUID>/ coord root/ConnectionType/view/connections/<UUID>/ dependConnectionId root/ConnectionType/view/connections/<UUID>/ desktop

If set to 1, the connection is ended after the first desktop is closed. If set to 0, the VMware Horizon View client returns to the desktop selection screen. This is enabled by default to prevent users from accidentally leaving the connection at the desktop selection screen after logging off.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

If specified, the named desktop will launch automatically upon login. By default, if there is only one desktop available, it will launch automatically without needing to be specified.

Sets the size in which the VMware Horizon View client will launch the desktop.

root/ConnectionType/view/connections/<UUID>/ desktopSize root/ConnectionType/view/connections/<UUID>/ directory root/ConnectionType/view/connections/<UUID>/ disableMaximizedApp root/ConnectionType/view/connections/<UUID>/ domain root/ConnectionType/view/connections/<UUID>/ enableSingleMode root/ConnectionType/view/connections/<UUID>/ extraEnvValues/<UUID>/key root/ConnectionType/view/connections/<UUID>/ extraEnvValues/<UUID>/value root/ConnectionType/view/connections/<UUID>/ fallBackConnection root/ConnectionType/view/connections/<UUID>/ fullscreen root/ConnectionType/view/connections/<UUID>/ hasDesktopIcon root/ConnectionType/view/connections/<UUID>/ hideMenuBar root/ConnectionType/view/connections/<UUID>/ isInMenu root/ConnectionType/view/connections/<UUID>/ label root/ConnectionType/view/connections/<UUID>/ lockServer

If set to 1, window size settings for maximized applications are disabled.

Sets the domain to provide to View Connection Server. If no domain is specified, the default domain for the server is used.

Sets the name of an extra environment variable for use with the connection.

Sets the value of an extra environment variable for use with the connection.

Sets the fallback connection via its UUID.

If set to 1, the VMware Horizon View client launches in full screen mode when started.

If set to 1, the desktop icon for this connection is enabled. This key has no effect on Smart Zero.

If set to 1, the top menu bar within the desktop is hidden. This bar is used to manage remote devices and start other desktops.

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the connection name that is displayed in the UI. On Smart

Zero, this will typically be set to Default Connection and does not display in the UI.

If set to 1, standard users are prevented from changing the server address.

110 Appendix E Registry keys

Table E-10 root > ConnectionType > view (continued)

Registry key

root/ConnectionType/view/connections/<UUID>/ loginfields/domain root/ConnectionType/view/connections/<UUID>/ loginfields/password root/ConnectionType/view/connections/<UUID>/ loginfields/rememberme root/ConnectionType/view/connections/<UUID>/ loginfields/showpassword root/ConnectionType/view/connections/<UUID>/ loginfields/smartcard root/ConnectionType/view/connections/<UUID>/ loginfields/username root/ConnectionType/view/connections/<UUID>/ password

Description

If set to 1, the Domain field is shown in the login dialog for the connection. If set to 2, the field is shown but disabled. If set to 0, the field is hidden.

If set to 1, the Password field is shown in the login dialog for the connection. If set to 2, the field is shown but disabled. If set to 0, the field is hidden.

If set to 1, the Remember me checkbox is shown in the login dialog for the connection. If set to 2, the checkbox is shown but disabled. If set to 0, the checkbox is hidden.

If set to 1, the Show password button is shown in the login dialog for the connection. If set to 2, the button is shown but disabled. If set to 0, the button is hidden.

If set to 1, the Smart card login checkbox is shown in the login dialog for the connection. If set to 2, the checkbox is shown but disabled. If set to 0, the checkbox is hidden. This checkbox might not appear if no smart card is detected, even if this option is enabled.

If set to 1, the User Name field is shown in the login dialog for the connection. If set to 2, the field is shown but disabled. If set to 0, the field is hidden.

Sets the default password to supply to the remote host during login. This value will be encrypted. Generally, this setting is used for kiosk-style applications where a generic password is used for login.

root/ConnectionType/view/connections/<UUID>/ saveCredentials root/ConnectionType/view/connections/<UUID>/ server root/ConnectionType/view/connections/<UUID>/ sessionEndAction root/ConnectionType/view/connections/<UUID>/ singleDesktop root/ConnectionType/view/connections/<UUID>/ smartcard

Sets the address of the remote host to connect to. This is typically a URL such as http://server.domain.com.

root/ConnectionType/view/connections/<UUID>/ startMode root/ConnectionType/view/connections/<UUID>/ username root/ConnectionType/view/connections/<UUID>/ viewSecurityLevel

If set to 1, locally-attached smart cards are forwarded to the remote host, allowing them to be used by applications on the remote host. This only enables smart card login for the remote host, not for View Connection Server.

If set to the default focus and the connection is already started, the connection will be given focus. Otherwise, an error will be returned stating that the connection is already started.

Sets the default user name to supply to the remote host during login. Generally, this setting is used for kiosk-style applications where a generic user name is used for login.

If set to Refuse insecure connections, the VMware

Horizon View client will not allow a user to connect to View

Connection Server if the server's SSL certificate is invalid. If set to

Warn, the VMware Horizon View client will display a warning if the server's certificate is not able to be verified, and if the certificate is self-signed or expired, the user still will not be allowed to connect. If set to Allow all connections, the server root > ConnectionType 111

Table E-10 root > ConnectionType > view (continued)

Registry key

root/ConnectionType/view/connections/<UUID>/ waitForNetwork

Description

certificate will not be verified and connections to any server will be allowed.

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/attachToConsole root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/audioLatency root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/colorDepth root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/compression root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/disableMMRwithRFX root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/frameAcknowledgeCount root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/general/enableMMR root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/general/sendHostname root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/loadBalanceInfo root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/mouseMotionEvents root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/offScreenBitmaps root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/perfFlagDesktopComposition

Sets the average milliseconds of offset between the audio stream and the display of corresponding video frames after decoding.

This setting is deprecated. It is used to reduce the color depth of the connection below that of the native desktop resolution.

Frequently, this has been used to reduce network bandwidth.

Reducing color depth to a level not supported by the video driver can cause screen corruption or launch failures.

If set to 1, compression of RDP data sent between the client and the server is enabled.

If set to 1, multimedia redirection is disabled if a valid RemoteFX session is established.

Sets the number of video frames the server can push without waiting for acknowledgement from the client. Lower numbers result in a more responsive desktop but lower frame rate. If set to

0, frame acknowledgement is not used in the client-server interactions.

If set to 1, the Multimedia Redirection plugin is enabled, causing supported codecs played through Windows Media Player to be redirected to the client. This will greatly improve full screen and high definition video playback for codecs such as WMV9, VC1, and MPEG4.

If set to hostname, the system hostname is sent to the remote host. This is typically used to identify the thin client associated with a particular RDP session. The sent hostname can be overridden using sendHostname in the connection-specific settings. If set to mac, the MAC address of the first available network adapter is sent instead of the hostname.

This value is the load balancing cookie sent for brokering purposes to the server upon connection and corresponds to the loadbalanceinfo field in the .rdp file. By default, the value is empty.

If set to 0, mouse motion events are not sent to the server. This can prevent some user feedback such as tooltips from functioning properly.

If set to 0, off-screen bitmaps are disabled. This can increase performance slightly but will cause blocks of the screen to update asynchronously, causing screen transitions to update nonuniformly.

If set to 1, desktop composition (such as translucent borders) is allowed if supported by the server. Turning off desktop composition can improve performance for low-bandwidth

112 Appendix E Registry keys

Table E-10 root > ConnectionType > view (continued)

Registry key

root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/perfFlagFontSmoothing root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/perfFlagNoCursorSettings root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/perfFlagNoCursorShadow root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/perfFlagNoMenuAnimations root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/perfFlagNoTheming root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/perfFlagNoWallpaper root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/perfFlagNoWindowDrag root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/portMapping root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/printerMapping root/ConnectionType/freerdp/connections/

<UUID>/rdp6Buffering root/ConnectionType/freerdp/connections/

<UUID>/rdp8Codecs root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/rdpEncryption root/ConnectionType/freerdp/connections/

<UUID>/rdpH264Codec root/ConnectionType/freerdp/connections/

<UUID>/rdpProgressiveCodec

Description

connections. Generally, this only affects RemoteFX. If set to 2, the value is selected based on the thin client performance.

If set to 1, font smoothing is allowed if supported by the server and enabled. Turning off font smoothing can improve performance on low-bandwidth connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, cursor blinking is disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, mouse cursor shadows are disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, menu animations are disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, user interface themes are disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, the desktop wallpaper is disabled, which can improve performance on low-bandwidth RDP connections. If set to 2, the value is selected based on the thin client performance.

If set to 1, full-content window dragging is disabled, which can improve performance on low-bandwidth RDP connections. The window outline is used instead. If set to 2, the value is selected based on the thin client performance.

If set to 1, the following serial and parallel ports are redirected to the remote host: ttyS0, ttyS1, ttyS2, ttyS3, ttyUSB0, lp0.

If set to 1, all printers defined locally via CUPS are redirected to the remote host.

If set to 1, non-RemoteFX graphics performance is increased at the cost of less frequent screen updates.

If set to 1, RDP 8 codecs are used if available. This setting should be disabled only in the case of a defect specific to RDP 8 codecs.

Disabling this setting might also disable more advanced codecs.

If set to 1, standard RDP encryption is used to encrypt all data between the client and the server.

If set to 1, RDP 8 H.264 codecs are used if available. This setting has known visual errors, particularly in multi-monitor configurations, and should be considered experimental and unsupported. Enabling this setting simply advises the server that the thin client supports H.264 for desktop display. The server must also support H.264, and the server makes the final decision on what codecs are used. This setting affects only the desktop codecs. It does not affect multimedia redirection codecs.

If set to 1, RDP 8 progressive codecs are used if available. This setting should be disabled only in the case of a defect specific to

RDP 8 progressive codecs. Disabling this setting might also disable more advanced codecs.

root > ConnectionType 113

Table E-10 root > ConnectionType > view (continued)

Registry key Description

root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/remoteFx root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/securityLevel root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/sendHostname

If set to 1, RemoteFX is used if available.

Sets the certificate security level. If set to 0, all connections are allowed. If set to 1, remembered hosts are checked and a warning dialog is shown if verification is not passed. If set to 2, remembered hosts are not checked and a warning dialog is shown if verification is not passed. If set to 3, all insecure connections are refused.

Sets the thin client hostname that is sent to the remote host. If left blank, the system hostname is sent. The registry key root/

ConnectionType/view/connections/<UUID>/ xfreerdpOptions/general/sendHostname must be set to hostname for this key to be used.

root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/sound root/ConnectionType/view/connections/<UUID>/ xfreerdpOptions/xkbLayoutId

If set to Bring to this computer, sound is redirected from the remote host to the client using a standard virtual channel. If set to Leave at remote computer, sound is left at the remote host. This can be useful when using a redirected USB audio device. If set to any other value, audio is disabled.

Generally, HP recommends setting this value to Bring to this computer and not redirecting USB playback devices to the remote host. This will improve audio quality and ensure that client audio redirected via other virtual channels (such as

Multimedia Redirection) matches local audio settings.

Sets an XKB layout ID for bypassing the system keyboard. To see the list of available IDs, enter the following command in an X terminal: xfreerdp --kbd-list.

root/ConnectionType/view/coreSettings/

USBrelevant

Specifies if this connection type is USB-relevant. If it is, it might have a USB plugin for redirecting USB devices.

root/ConnectionType/view/coreSettings/appName Sets the internal application name to use for this connection type.

This key should not need to be modified.

root/ConnectionType/view/coreSettings/ className

Sets the internal application class name to use for this connection type. This key should not need to be modified.

root/ConnectionType/view/coreSettings/editor Sets the internal application name to use when the Connection

Manager is launched for this connection type. This key should not need to be modified.

root/ConnectionType/view/coreSettings/ icon16Path

Sets the path to the 16x16 pixel icon for this application.

Sets the path to the 32x32 pixel icon for this application.

root/ConnectionType/view/coreSettings/ icon32Path root/ConnectionType/view/coreSettings/ icon48Path

Sets the path to the 48x48 pixel icon for this application.

root/ConnectionType/view/coreSettings/label root/ConnectionType/view/coreSettings/ priorityInConnectionLists

Sets the name to display for this connection type in the UI.

Sets the priority of this connection type when it is displayed in the

Connection Manager and the Configuration Wizard that displays during initial setup. A higher value will move the connection type towards the top of the list. If set to 0, the connection type is hidden from Configuration Wizard and is shown last in Connection

Manager. Connections types with the same priority are listed in alphabetical order.

114 Appendix E Registry keys

Table E-10 root > ConnectionType > view (continued)

Registry key Description

root/ConnectionType/view/coreSettings/ serverRequired root/ConnectionType/view/coreSettings/ stopProcess root/ConnectionType/view/coreSettings/ watchPid root/ConnectionType/view/coreSettings/ wrapperScript

Sets whether a server name or address is unused, optional, or required for this connection type.

Sets the behavior that should occur when connection-mgr stop is called on this connection. By default this is close, which will send a standard kill signal to the process. When set to kill, the process specified by appName will be forcefully killed. When set to custom, a custom execution script specified by wrapperScript will be executed with the argument stop to terminate the process gracefully.

If set to 1, the connection is monitored under the name specified by appName. This key should not need to be modified.

Sets the script or binary to execute when launching this connection type. This is the primary script handling all connection settings and command line arguments for the connection. This key should not need to be modified.

root/ConnectionType/view/general/rdpOptions Options specified here will be forwarded directly to the RDP client if RDP is used as the display protocol for the VMware Horizon View connection. To see a full list of options, enter the following command in an X terminal: rdesktop --help root/ConnectionType/view/gui/viewManager/name This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/view/gui/viewManager/ status

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/view/gui/viewManager/ title root/ConnectionType/view/gui/viewManager/ widgets/autostart root/ConnectionType/view/gui/viewManager/ widgets/fallBackConnection root/ConnectionType/view/gui/viewManager/ widgets/label

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Auto start priority widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Fallback Connection widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Name widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root > ConnectionType 115

root > ConnectionType > xdmcp

Table E-11 root > ConnectionType > xdmcp

Registry key Description

root/ConnectionType/xdmcp/authorizations/ user/add root/ConnectionType/xdmcp/authorizations/ user/general

If set to 1, a standard user has permission to add a new connection of this type using the Connection Manager. This key has no effect on Smart Zero.

If set to 1, a standard user has permission to modify the general settings for this connection type using the Connection Manager.

This key has no effect on Smart Zero.

root/ConnectionType/xdmcp/connections/<UUID>/ address

Sets the hostname or IP address to connect to.

root/ConnectionType/xdmcp/connections/<UUID>/ afterStartedCommand

Sets the command to execute after the connection has been started.

root/ConnectionType/xdmcp/connections/<UUID>/ afterStoppedCommand

Sets the command to execute after the connection has been stopped.

root/ConnectionType/xdmcp/connections/<UUID>/ authorizations/user/edit

If set to 1, a standard user has permission to modify the connection settings for this connection.

root/ConnectionType/xdmcp/connections/<UUID>/ authorizations/user/execution

If set to 1, a standard user has permission to execute this connection.

root/ConnectionType/xdmcp/connections/<UUID>/ autoReconnect

If set to 1, the connection will be restarted when it is closed or disconnected.

root/ConnectionType/xdmcp/connections/<UUID>/ autostart

If set to a value of 1–5, the connection will be started automatically after the system boots, with the value of 1 having the highest priority.

root/ConnectionType/xdmcp/connections/<UUID>/ beforeStartingCommand

Sets the command to execute before the connection starts.

root/ConnectionType/xdmcp/connections/<UUID>/ color

Sets the color depth of the display for the connection.

root/ConnectionType/xdmcp/connections/<UUID>/ connectionEndAction

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xdmcp/connections/<UUID>/ coord

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xdmcp/connections/<UUID>/ dependConnectionId

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xdmcp/connections/<UUID>/ extraEnvValues/<UUID>/key

Sets the name of an extra environment variable for use with the connection.

root/ConnectionType/xdmcp/connections/<UUID>/ extraEnvValues/<UUID>/value

Sets the value of an extra environment variable for use with the connection.

root/ConnectionType/xdmcp/connections/<UUID>/ fallBackConnection

Sets the fallback connection via its UUID.

root/ConnectionType/xdmcp/connections/<UUID>/ fontServer

Sets the address of the font server to use. The registry key useFontServer must also be set to 1.

root/ConnectionType/xdmcp/connections/<UUID>/ hasDesktopIcon

If set to 1, the desktop icon for this connection is enabled. This key has no effect on Smart Zero.

116 Appendix E Registry keys

Table E-11 root > ConnectionType > xdmcp (continued)

Registry key Description

root/ConnectionType/xdmcp/connections/<UUID>/ isInMenu

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xdmcp/connections/<UUID>/ label

Sets the connection name that is displayed in the UI. On Smart

Zero, this will typically be set to Default Connection and does not display in the UI.

root/ConnectionType/xdmcp/connections/<UUID>/ refreshRate

Sets the refresh rate of the display for the connection.

root/ConnectionType/xdmcp/connections/<UUID>/ startMode

If set to the default focus and the connection is already started, the connection will be given focus. Otherwise, an error will be returned stating that the connection is already started.

root/ConnectionType/xdmcp/connections/<UUID>/ type

Sets the XDMCP connection type. If set to chooser, all available hosts are listed and the user can select which one to connect to. If set to query, an XDMCP request is sent to the specified host directly. If set to broadcast, all available hosts are listed and the first one is connected to automatically.

root/ConnectionType/xdmcp/connections/<UUID>/ useFontServer

If set to 1, the font server is enabled. If set to 0, the local font is used.

root/ConnectionType/xdmcp/connections/<UUID>/ waitForNetwork

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

root/ConnectionType/xdmcp/connections/<UUID>/ windowSize

Sets the window size of the connection.

root/ConnectionType/xdmcp/coreSettings/

USBrelevant

Specifies if this connection type is USB-relevant. If it is, it might have a USB plugin for redirecting USB devices.

root/ConnectionType/xdmcp/coreSettings/ appName

Sets the internal application name to use for this connection type.

This key should not need to be modified.

root/ConnectionType/xdmcp/coreSettings/audio This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xdmcp/coreSettings/ className root/ConnectionType/xdmcp/coreSettings/ desktopButton

Sets the internal application class name to use for this connection type. This key should not need to be modified.

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xdmcp/coreSettings/editor Sets the internal application name to use when the Connection

Manager is launched for this connection type. This key should not need to be modified.

root/ConnectionType/xdmcp/coreSettings/ generalSettingsEditor

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the path to the 16x16 pixel icon for this application.

root/ConnectionType/xdmcp/coreSettings/ icon16Path root/ConnectionType/xdmcp/coreSettings/ icon32Path

Sets the path to the 32x32 pixel icon for this application.

root/ConnectionType/xdmcp/coreSettings/ icon48Path

Sets the path to the 48x48 pixel icon for this application.

root/ConnectionType/xdmcp/coreSettings/label Sets the name to display for this connection type in the UI.

root > ConnectionType 117

Table E-11 root > ConnectionType > xdmcp (continued)

Registry key

root/ConnectionType/xdmcp/coreSettings/ priorityInConnectionLists root/ConnectionType/xdmcp/coreSettings/ serverRequired root/ConnectionType/xdmcp/coreSettings/ stopProcess root/ConnectionType/xdmcp/coreSettings/ watchPid root/ConnectionType/xdmcp/coreSettings/ wrapperScript root/ConnectionType/xdmcp/gui/XdmcpManager/ name root/ConnectionType/xdmcp/gui/XdmcpManager/ status root/ConnectionType/xdmcp/gui/XdmcpManager/ title root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/address root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/autoReconnect root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/autostart root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/color root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/fontServer

Description

Sets the priority of this connection type when it is displayed in the

Connection Manager and the Configuration Wizard that displays during initial setup. A higher value will move the connection type towards the top of the list. If set to 0, the connection type is hidden from Configuration Wizard and is shown last in Connection

Manager. Connections types with the same priority are listed in alphabetical order.

Sets whether a server name or address is unused, optional, or required for this connection type.

Sets the behavior that should occur when connection-mgr stop is called on this connection. By default this is close, which will send a standard kill signal to the process. When set to kill, the process specified by appName will be forcefully killed. When set to custom, a custom execution script specified by wrapperScript will be executed with the argument stop to terminate the process gracefully.

If set to 1, the connection is monitored under the name specified by appName. This key should not need to be modified.

Sets the script or binary to execute when launching this connection type. This is the primary script handling all connection settings and command line arguments for the connection. This key should not need to be modified.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Address widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Auto reconnect widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Auto start priority widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Font server widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

118 Appendix E Registry keys

Table E-11 root > ConnectionType > xdmcp (continued)

Registry key

root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/hasDesktopIcon root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/isInMenu root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/label root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/refreshRate root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/type root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/useFontServer root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/waitForNetwork root/ConnectionType/xdmcp/gui/XdmcpManager/ widgets/windowSize

Description

Controls the state of the Show icon on desktop widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Name widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Type widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Use font server widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Wait for network before connecting widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

This registry key is either used internally or reserved for future use. The value should not be changed.

root > ConnectionType > xen

Table E-12 root > ConnectionType > xen

Registry key

root/ConnectionType/xen/authorizations/ user/add root/ConnectionType/xen/authorizations/user/ general root/ConnectionType/xen/connections/<UUID>/

SingleSignOn root/ConnectionType/xen/connections/<UUID>/ address

Description

If set to 1, a standard user has permission to add a new connection of this type using the Connection Manager. This key has no effect on Smart Zero.

If set to 1, a standard user has permission to modify the general settings for this connection type using the Connection Manager.

This key has no effect on Smart Zero.

Sets the address of the remote host to connect to. This is typically a URL such as http://server.domain.com.

root > ConnectionType 119

Table E-12 root > ConnectionType > xen (continued)

Registry key

root/ConnectionType/xen/connections/<UUID>/ afterStartedCommand root/ConnectionType/xen/connections/<UUID>/ afterStoppedCommand root/ConnectionType/xen/connections/<UUID>/ anonymousLogin root/ConnectionType/xen/connections/<UUID>/ appInMenu root/ConnectionType/xen/connections/<UUID>/ appOnDashboard root/ConnectionType/xen/connections/<UUID>/ appOnDesktop root/ConnectionType/xen/connections/<UUID>/ authorizations/user/edit root/ConnectionType/xen/connections/<UUID>/ authorizations/user/execution root/ConnectionType/xen/connections/<UUID>/ autoLaunchSingleApp root/ConnectionType/xen/connections/<UUID>/ autoReconnect root/ConnectionType/xen/connections/<UUID>/ autoReconnectAppsOnLogin root/ConnectionType/xen/connections/<UUID>/ autoReconnectDelay root/ConnectionType/xen/connections/<UUID>/ autoRefreshInterval root/ConnectionType/xen/connections/<UUID>/ autoStartDesktop root/ConnectionType/xen/connections/<UUID>/ autoStartResource root/ConnectionType/xen/connections/<UUID>/ autostart root/ConnectionType/xen/connections/<UUID>/ autostartDelay

Description

Sets the command to execute after the connection has been started.

Sets the command to execute after the connection has been stopped.

If set to 1, anonymous login is allowed for PNAgent and direct connections.

If set to 1, all applications for the connection will be displayed in the taskbar menu.

If set to 1, all applications for the connection will be displayed on the taskbar.

If set to 1, all applications for the connection will be displayed on the desktop.

If set to 1, a standard user has permission to modify the connection settings for this connection.

If set to 1, a standard user has permission to execute this connection.

If set to 1, and if only a single published application or desktop is returned by the Citrix server, that resource will be launched automatically.

If set to 1, the connection will be restarted when it is closed or disconnected.

If set to 1, the system will attempt to reconnect any active or disconnected Citrix sessions upon initial login.

Sets the amount of time in seconds to wait before reconnecting the session. The default of 0 will cause the connection to reconnect immediately. This setting only takes effect when autoReconnect is set to 1.

Controls the amount of time in seconds before the resources are cleared and refreshed again from the server. Set to -1 to disable.

It is normally not required to frequently refresh the resources from the server.

If set to 1, the first desktop to become available when the connection is started will be launched automatically.

Sets the name of the desktop or application to start automatically when the connection is launched.

If set to a value of 1–5, the connection will be started automatically after the system boots, with the value of 1 having the highest priority.

Sets the amount of time in seconds to wait before starting the connection after the system boots. The default of 0 will cause the connection to start immediately. This setting only takes effect when autostart is set to 1.

Sets the command to execute before the connection starts.

root/ConnectionType/xen/connections/<UUID>/ beforeStartingCommand root/ConnectionType/xen/connections/<UUID>/ connectionEndAction

This registry key is either used internally or reserved for future use. The value should not be changed.

120 Appendix E Registry keys

Table E-12 root > ConnectionType > xen (continued)

Registry key

root/ConnectionType/xen/connections/<UUID>/ connectionMode root/ConnectionType/xen/connections/<UUID>/ coord root/ConnectionType/xen/connections/<UUID>/ dependConnectionId root/ConnectionType/xen/connections/<UUID>/ disableSaveCredentials root/ConnectionType/xen/connections/<UUID>/ domain root/ConnectionType/xen/connections/<UUID>/ enableRSAToken

Description

Sets the Citrix connection mode for the connection.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xen/connections/<UUID>/ extraEnvValues/<UUID>/key root/ConnectionType/xen/connections/<UUID>/ extraEnvValues/<UUID>/value root/ConnectionType/xen/connections/<UUID>/ fallBackConnection root/ConnectionType/xen/connections/<UUID>/ folder root/ConnectionType/xen/connections/<UUID>/ forceHttps root/ConnectionType/xen/connections/<UUID>/ fullscreen root/ConnectionType/xen/connections/<UUID>/ hasDesktopIcon root/ConnectionType/xen/connections/<UUID>/ ignoreCertCheck root/ConnectionType/xen/connections/<UUID>/ label root/ConnectionType/xen/connections/<UUID>/ loginfields/password root/ConnectionType/xen/connections/<UUID>/ loginfields/rememberme

Sets the domain to provide to the XenDesktop server. If no domain is specified, the default domain for the server is used.

CAUTION:

This functionality is unsupported.

If set to 1, the user will be prompted before connecting for a security token value to use when authenticating with NetScaler

Gateway.

Sets the name of an extra environment variable for use with the connection.

Sets the value of an extra environment variable for use with the connection.

Sets the fallback connection via its UUID.

If set to 1, only HTTPS connections are allowed.

If set to 1, the Citrix client launches in full screen mode when started.

If set to 1, the desktop icon for this connection is enabled. This key has no effect on Smart Zero.

If set to 1, certificate checks are ignored for the connection.

root/ConnectionType/xen/connections/<UUID>/ logOnMethod root/ConnectionType/xen/connections/<UUID>/ loginfields/domain

Sets the connection name that is displayed in the UI. On Smart

Zero, this will typically be set to Default Connection and does not display in the UI.

If set to 1, the Domain field is shown in the login dialog for the connection. If set to 2, the field is shown but disabled. If set to 0, the field is hidden.

If set to 1, the Password field is shown in the login dialog for the connection. If set to 2, the field is shown but disabled. If set to 0, the field is hidden.

If set to 1, the Remember me checkbox is shown in the login dialog for the connection. If set to 2, the checkbox is shown but disabled. If set to 0, the checkbox is hidden.

root > ConnectionType 121

Table E-12 root > ConnectionType > xen (continued)

Registry key Description

root/ConnectionType/xen/connections/<UUID>/ loginfields/showpassword root/ConnectionType/xen/connections/<UUID>/ loginfields/smartcard root/ConnectionType/xen/connections/<UUID>/ loginfields/username root/ConnectionType/xen/connections/<UUID>/ password root/ConnectionType/xen/connections/<UUID>/ requireCredentialsDirectConnect

If set to 1, the Show password button is shown in the login dialog for the connection. If set to 2, the button is shown but disabled. If set to 0, the button is hidden.

If set to 1, the Smart card login checkbox is shown in the login dialog for the connection. If set to 2, the checkbox is shown but disabled. If set to 0, the checkbox is hidden. This checkbox might not appear if no smart card is detected, even if this option is enabled.

If set to 1, the User Name field is shown in the login dialog for the connection. If set to 2, the field is shown but disabled. If set to 0, the field is hidden.

Sets the default password to supply to the remote host during login. This value will be encrypted. Generally, this setting is used for kiosk-style applications where a generic password is used for login.

If set to 0, credentials are not needed to initiate a direct connection. However, credentials are needed to launch an application.

root/ConnectionType/xen/connections/<UUID>/ savePassword root/ConnectionType/xen/connections/<UUID>/ smartCardModuleKey root/ConnectionType/xen/connections/<UUID>/ startMode

Specifies the security module to use for a smart card connection.

root/ConnectionType/xen/connections/<UUID>/ unplugSmartCardAction root/ConnectionType/xen/connections/<UUID>/ username root/ConnectionType/xen/connections/<UUID>/ waitForNetwork

If set to the default focus and the connection is already started, the connection will be given focus. Otherwise, an error will be returned stating that the connection is already started.

Sets the action to perform when a smart card is unplugged during a connection. logoffwill log off the current session. closewill close all the opened resources. noactionwill do nothing.

Sets the default user name to supply to the remote host during login. Generally, this setting is used for kiosk-style applications where a generic user name is used for login.

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

root/ConnectionType/xen/coreSettings/

USBrelevant

Specifies if this connection type is USB-relevant. If it is, it might have a USB plugin for redirecting USB devices.

root/ConnectionType/xen/coreSettings/appName Sets the internal application name to use for this connection type.

This key should not need to be modified.

root/ConnectionType/xen/coreSettings/ autoLogoutDelayAfterLaunch root/ConnectionType/xen/coreSettings/ autoLogoutDelayBeforeLaunch

This setting applies to Citrix servers with multiple published resources. If less than 0, no auto-logout is performed. Otherwise, this setting dictates the number of seconds between the closing of the last Xen published resource and when the user is logged out automatically and returned to the initial login screen. Citrix process delays might extend the auto-logout time.

This setting applies to Citrix servers with multiple published resources. If less than 0, no auto-logout is performed. Otherwise, this setting dictates the number of seconds allowed to pass while no applications are launched before the user is logged out

122 Appendix E Registry keys

Table E-12 root > ConnectionType > xen (continued)

Registry key Description

root/ConnectionType/xen/coreSettings/ className root/ConnectionType/xen/coreSettings/editor root/ConnectionType/xen/coreSettings/ generalSettingsEditor automatically and returned to the initial login screen. Citrix process delays might extend the auto-logout time.

Sets the internal application class name to use for this connection type. This key should not need to be modified.

Sets the internal application name to use when the Connection

Manager is launched for this connection type. This key should not need to be modified.

Sets the internal application name to use when the General

Settings Manager is launched for this connection type. This key should not need to be modified.

Sets the path to the 16x16 pixel icon for this application.

root/ConnectionType/xen/coreSettings/ icon16Path root/ConnectionType/xen/coreSettings/ icon32Path root/ConnectionType/xen/coreSettings/ icon48Path root/ConnectionType/xen/coreSettings/label root/ConnectionType/xen/coreSettings/ priorityInConnectionLists root/ConnectionType/xen/coreSettings/ serverRequired root/ConnectionType/xen/coreSettings/ stopProcess

Sets the path to the 32x32 pixel icon for this application.

Sets the path to the 48x48 pixel icon for this application.

Sets the name to display for this connection type in the UI.

Sets the priority of this connection type when it is displayed in the

Connection Manager and the Configuration Wizard that displays during initial setup. A higher value will move the connection type towards the top of the list. If set to 0, the connection type is hidden from Configuration Wizard and is shown last in Connection

Manager. Connections types with the same priority are listed in alphabetical order.

Sets whether a server name or address is unused, optional, or required for this connection type.

Sets the behavior that should occur when connection-mgr stop is called on this connection. By default this is close, which will send a standard kill signal to the process. When set to kill, the process specified by appName will be forcefully killed. When set to custom, a custom execution script specified by wrapperScript will be executed with the argument stop to terminate the process gracefully.

root/ConnectionType/xen/coreSettings/watchPid If set to 1, the connection is monitored under the name specified by appName. This key should not need to be modified.

root/ConnectionType/xen/coreSettings/ wrapperScript root/ConnectionType/xen/general/TWIMode

Sets the script or binary to execute when launching this connection type. This is the primary script handling all connection settings and command line arguments for the connection. This key should not need to be modified.

Controls seamless mode for published applications. This setting directly maps to the Citrix .ini file setting TWIMode.

root/ConnectionType/xen/general/

TWIModeResizeType

This setting directly maps to the Citrix .ini file setting

TWIMoveResizeType.

If set to 1, a user can read the mapped drive.

root/ConnectionType/xen/general/ allowReadOn<AthruZ> root/ConnectionType/xen/general/ allowWriteOn<AthruZ>

If set to 1, a user can write to the mapped drive.

root > ConnectionType 123

Table E-12 root > ConnectionType > xen (continued)

Registry key Description

root/ConnectionType/xen/general/async If set to 1, asynchronous polling is enabled. This setting directly maps to the Citrix .ini file setting CommPollSize.

root/ConnectionType/xen/general/autoReconnect If set to 1, automatic session reconnection is enabled. This is not the same as the connection-specific auto-reconnect. This occurs internally within the Citrix client without restarting the connection. This setting directly maps to the Citrix .ini file setting

TransportReconnectEnabled.

root/ConnectionType/xen/general/ bitmapCacheSize

Sets the minimum size for bitmap caching. This setting directly maps to the Citrix .ini file setting

PersistentCacheMinBitmap.

root/ConnectionType/xen/general/bottomMonitor Sets the screen area of the bottom monitor to show the virtual desktop. If set to 0, the monitor is not used to show the virtual desktop.

root/ConnectionType/xen/general/colorDepth Forces a specific color depth for all connections. This is usually done only in specialized environments where the automatic depth selection fails or in very slow networks to reduce congestion.

root/ConnectionType/xen/general/colorMapping If set to Shared - Approximate Colors, approximate colors from the default colormap are used. If set to Private -

Exact Colors, precise colors are used. This setting directly maps to the Citrix .ini file setting ApproximateColors.

root/ConnectionType/xen/general/ contentRedirection root/ConnectionType/xen/general/ defaultBrowserProtocol root/ConnectionType/xen/general/ drivePathMappedOn<AthruZ>

If set to 1, links from web content are sent from the server to the client so that the client can try to open them locally.

Controls the protocol used to locate the host for the connection. If not specified, the default value from the [WFClient] section of wfclient.ini is used. This setting directly maps to the Citrix .ini file setting BrowserProtocol.

Sets the local filesystem directory to map to the remote host.

Typically this is set to /media to allow all connected USB drives to be mapped to the remote host via a single drive letter.

root/ConnectionType/xen/general/ enableAlertSound

If set to 1, Windows alert sounds are enabled. This setting indirectly maps to the Citrix .ini file setting DisableSound.

If set to 1, clipboard redirection is enabled.

root/ConnectionType/xen/general/ enableClipboard root/ConnectionType/xen/general/ enableCursorColors root/ConnectionType/xen/general/ enableDataCompression root/ConnectionType/xen/general/ enableDriveMapAndRedirect root/ConnectionType/xen/general/ enableDriveMapping

If set to 1, colored cursors are enabled. Setting this to 0 might fix graphical cursor corruption in some cases.

If set to 1, data compression is enabled. This setting directly maps to the Citrix .ini file setting Compress.

If set to 1, mapping and redirection for USB storage devices is enabled.

If set to 1, directories on the local filesystem can be forwarded to the remote host via a virtual drive. Typically /media is mapped to Z to allow USB drives to be forwarded to the remote host. If

USB redirection is enabled, this setting should be disabled to prevent storage conflicts. To be properly mapped to the remote host in this fashion, the USB device must use one of the following filesystems: FAT32, NTFS, ext2, ext3.

124 Appendix E Registry keys

Table E-12 root > ConnectionType > xen (continued)

Registry key Description

root/ConnectionType/xen/general/ enableDynamicDriveMapping root/ConnectionType/xen/general/ enableForceDirectConnect root/ConnectionType/xen/general/ enableH264Compression root/ConnectionType/xen/general/ enableHDXFlashRedirection

If set to 1, H.264 compression is enabled. The H.264 codec provides better performance of rich and professional graphics applications on WAN networks than the JPEG codec.

Controls the behavior of HDX Flash Redirection. If set to Always,

HDX Flash Redirection is used if possible, and the user is not prompted. If set to Ask, the user is prompted. If set to Never, the feature is disabled.

Controls the behavior of HDX Flash Server-Side Content Fetching.

If disabled, the client will fetch for content.

root/ConnectionType/xen/general/ enableHDXFlashServerContentFetch root/ConnectionType/xen/general/ enableHDXMediaStream

If set to 1, HDX MediaStream is enabled. If set to 0, media files will still play via standard streaming, but the quality might not be as high.

root/ConnectionType/xen/general/enableHWH264 If set to 1, and if enableH264Compression is also set to 1, hardware compression for H.264 is enabled. If set to 0, H.264 compression will be handled by software.

root/ConnectionType/xen/general/ enableMapOn<AthruZ>

If set to 1, a local filesystem directory can be mapped to this drive on the remote host. The corresponding drivePathMappedOn registry key must be set to a valid local directory for drive mapping to work properly.

root/ConnectionType/xen/general/ enableMultiMedia

If set to 1, USB storage devices will be dynamically mapped on the

Citrix server. If set to 0, dynamic mapping of USB storage devices is disabled.

If set to 1, the connection is forced to bypass the Citrix Web

Interface and PNAgent services. Authentication will occur on the server after the initial connection has been made.

root/ConnectionType/xen/general/ enableOffScreenSurface

If set to 1, multimedia is enabled. HDX Lync might have a conflict if this setting is enabled. This setting directly maps to the

Citrix .ini file settings in the MultiMedia in Virtual

Channels section.

If set to 1, the server can use the X PixMap format for offscreen drawing. This reduces bandwidth in 15-bit and 24-bit color modes at the expense of X server memory and processor time.

This setting directly maps to the Citrix .ini file setting

EnableOSS.

root/ConnectionType/xen/general/ enableSessionReliability root/ConnectionType/xen/general/ enableSmallFrames

If set to 1, Citrix Session Reliability is enabled. Session Reliability changes the way sessions are resumed after losing a network connection. Please see Citrix documentation for more information on Session Reliability.

If set to 1, small non-H.264 rectangle updates are enabled for H.

264. enableTextTracking must also be enabled for this to have an effect.

If set to 1, smart card login is enabled.

root/ConnectionType/xen/general/ enableSmartCard root/ConnectionType/xen/general/ enableTextTracking root/ConnectionType/xen/general/ enableUSBRedirection

If set to 1, optimized lossless text overlays are enabled for H.264.

If set to 1, USB storage devices will be redirected.

root > ConnectionType 125

Table E-12 root > ConnectionType > xen (continued)

Registry key Description

root/ConnectionType/xen/general/ enableWindowsAlertSounds root/ConnectionType/xen/general/ encryptionLevel

Sets the level of encryption. Encryption protocols for all levels are defined in the [EncryptionLevelSession] section of module.ini. This setting directly maps to the Citrix .ini file setting

[EncryptionLevelSession].

Sets the font smoothing type.

root/ConnectionType/xen/general/ fontSmoothingType root/ConnectionType/xen/general/ hotKey<1thru15>Char root/ConnectionType/xen/general/ hotKey<1thru15>Shift

Sets the hot key to forward to the remote session when the key or key combination set in the corresponding hotKeyShift is pressed.

Sets the key or key combination used to activate the hot key set in the corresponding hotKeyChar.

root/ConnectionType/xen/general/ httpAddresses/<UUID>/address root/ConnectionType/xen/general/ keyPassthroughEscapeChar

Sets the keyboard key for disabling the transparent keyboard mode. This setting directly maps to the Citrix .ini file setting

KeyPassthroughEscapeChar.

root/ConnectionType/xen/general/ keyPassthroughEscapeShift root/ConnectionType/xen/general/ lastComPortNum

Sets the keyboard key combination for disabling the transparent keyboard mode. This setting directly maps to the Citrix .ini file setting KeyPassthroughEscapeShift.

Sets the number of mapped serial ports. If set to 0, serial port mapping is disabled.

root/ConnectionType/xen/general/leftMonitor Sets the screen area of the left monitor to show the virtual desktop. If set to 0, the monitor is not used to show the virtual desktop.

root/ConnectionType/xen/general/localTextEcho

Controls keyboard latency reduction. This setting indirectly maps to the Citrix .ini file setting ZLKeyboardMode.

root/ConnectionType/xen/general/ monitorNetwork

If set to Off, network connectivity is not monitored. If set to

Local network link status only, only the local network link status is monitored. If set to Server online status, both the local network link status and server connectivity are monitored.

root/ConnectionType/xen/general/ mouseClickFeedback root/ConnectionType/xen/general/ mouseMiddleButtonPaste

Controls mouse latency reduction. This setting indirectly maps to the Citrix .ini file setting ZLMouseMode.

If set to 1, middle mouse button paste emulation for Windows sessions is enabled. This setting directly maps to the Citrix .ini file setting MouseSendsControlV.

root/ConnectionType/xen/general/noInfoBox root/ConnectionType/xen/general/ printerAutoCreation

If set to 1, the client manager (wfcmgr) will not display when a client session terminates. This setting directly maps to the

Citrix .ini file setting PopupOnExit.

If set to 0, printer mapping is disabled. If set to 1, printers defined locally will be mapped to the connection. If set to 2, USB printers are redirected as configured in the USB Manager.

root/ConnectionType/xen/general/proxyAddress Sets the proxy address to use if a manual proxy setting is selected via proxyType.

126 Appendix E Registry keys

Table E-12 root > ConnectionType > xen (continued)

Registry key Description

root/ConnectionType/xen/general/proxyPassword Sets the proxy password to use if a manual proxy setting is selected via proxyType. This password will be encrypted using rc4 encryption.

root/ConnectionType/xen/general/proxyPort Sets the proxy port to use if a manual proxy setting is selected via proxyType.

root/ConnectionType/xen/general/proxyType root/ConnectionType/xen/general/proxyUser

Sets the type of proxy to use for XenDesktop connections. The value Use Browser settings is only supported if a local browser is installed.

Sets the proxy username to use if a manual proxy setting is selected via proxyType.

root/ConnectionType/xen/general/rightMonitor Sets the screen area of the right monitor to show the virtual desktop. If set to 0, the monitor is not used to show the virtual desktop.

root/ConnectionType/xen/general/saveLogs If set to 1, detailed log information is saved after the session ends. This log information will be saved to the following directory: /tmp/debug/citrix/<date>/ root/ConnectionType/xen/general/ serverCheckTimeout root/ConnectionType/xen/general/ sessionSharingClient

If set to 1, session-sharing requests are sent to other Citrix sessions on the same X display. This setting directly maps to the

Citrix .ini file setting EnableSessionSharingClient.

If set to 1, the virtual desktop will be shown on all monitors.

root/ConnectionType/xen/general/ showOnAllMonitors root/ConnectionType/xen/general/ smartCardModuleMap/CoolKeyPK11 root/ConnectionType/xen/general/ smartCardModuleMap/GemaltoDotNet

Specifies the path to the CoolKey PKCS #11 smart card security module.

Specifies the path to the Gemalto .NET smart card security module.

Specifies the path to the Open SC smart card security module.

root/ConnectionType/xen/general/ smartCardModuleMap/OpenSC root/ConnectionType/xen/general/sound Sets the sound quality. This setting indirectly maps to the

Citrix .ini file setting AudioBandwidthLimit.

root/ConnectionType/xen/general/speedScreen root/ConnectionType/xen/general/tcpAccel root/ConnectionType/xen/general/tcpAddresses/

<UUID>/address root/ConnectionType/xen/general/topMonitor root/ConnectionType/xen/general/ transparentKeyPassthrough

Sets the screen area of the top monitor to show the virtual desktop. If set to 0, the monitor is not used to show the virtual desktop.

Controls how certain Windows key combinations handled. If set to

Translated, the key combinations apply to the local desktop. If set to Direct in full screen desktops only, the key combinations apply to the remote session only when it is in full screen mode. If set to Direct, the key combinations always apply to the remote session as long as the window has focus. This setting indirectly maps to the Citrix .ini file setting

TransparentKeyPassthrough.

root > ConnectionType 127

Table E-12 root > ConnectionType > xen (continued)

Registry key Description

root/ConnectionType/xen/general/ twRedundantImageItems root/ConnectionType/xen/general/ useAlternateAddress root/ConnectionType/xen/general/ useBitmapCache root/ConnectionType/xen/general/useEUKS root/ConnectionType/xen/general/useLocalIM

Controls the number of screen areas that will be tracked in

ThinWire to prevent redundant drawing of bitmap images. An adequate value for 1024x768 sessions is 300.

If set to 1, an alternate address is used for firewall connections.

This setting directly maps to the Citrix .ini file setting

UseAlternateAddress.

If set to 1, the persistent disk cache is enabled. The persistent disk cache stores commonly-used graphical objects such as bitmaps on the hard disk of the thin client. Using the persistent disk cache increases performance across low-bandwidth connections but reduces the amount of available disk space on the thin client. For thin clients on high-speed LANs, usage of the persistent disk cache is not necessary. This setting directly maps to the Citrix .ini file setting PersistentCacheEnabled.

Controls the use of Extended Unicode Keyboard Support (EUKS) on Windows servers. If set to 0, EUKS is not used. If set to 1, EUKS is used as a fallback. If set to 2, EUKS is used whenever possible.

If this setting is enabled, the local X input method is used to interpret keyboard input. This is supported for European languages only. This setting directly maps to the Citrix .ini file setting useLocalIME.

root/ConnectionType/xen/general/userAgent root/ConnectionType/xen/general/ waitForNetwork root/ConnectionType/xen/general/ webcamFramesPerSec

The string from this key will be presented by the Citrix client and will be helpful for administrators to know where the connection request is from.

If set to 1, the connection will not be launched until networking is available. This ensures that, on a slow network, the connection does not launch before networking is available, which could cause a failure.

Controls the HDXWebCamFramesPerSec variable in the

All_Regions.ini file.

root/ConnectionType/xen/general/webcamSupport If set to 0, the webcam and webcam audio are disabled. If set to 1, the webcam and webcam audio are enabled, with compression. If set to 2, USB redirection of the webcam and webcam audio is enabled.

root/ConnectionType/xen/general/windowHeight Sets the height of the window in pixels if windowSize is set to

Fixed Size.

root/ConnectionType/xen/general/windowPercent

Sets the size of the window as a percentage if windowSize is set to Percentage of Screen Size.

root/ConnectionType/xen/general/windowSize If set to Default, the server-side settings are used. If set to

Full Screen, the window is maximized without borders on all available screens. If set to Fixed Size, the windowWidth and windowHeight registry keys can be used to specify the size of the window in pixels. If set to Percentage of Screen

Size, the windowPercent key can be used to specify the size of the window as a percentage. For Percentage of Screen

Size to take effect, enableForceDirectConnect must be set to 1 and TWIMode must be set to 0. This setting only works with XenApp and only if the server allows direct connections. This setting does not work with XenDesktop.

128 Appendix E Registry keys

Table E-12 root > ConnectionType > xen (continued)

Registry key Description

root/ConnectionType/xen/general/windowWidth root/ConnectionType/xen/gui/XenDesktopPanel/ disabled

Sets the width of the window in pixels if windowSize is set to

Fixed Size.

If set to 1, the Xen Desktop panel and its taskbar are disabled.

This is usually used when autoStartResource or autoStartDesktop is enabled.

root/ConnectionType/xen/gui/XenManager/name This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xen/gui/XenManager/status This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xen/gui/XenManager/title This registry key is either used internally or reserved for future use. The value should not be changed.

root/ConnectionType/xen/gui/XenManager/ widgets/address

Controls the state of the Service URL widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/xen/gui/XenManager/ widgets/appInMenu

Controls the state of the Show applications on taskbar widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to readonly, the widget is visible in the read-only state.

root/ConnectionType/xen/gui/XenManager/ widgets/appOnDesktop root/ConnectionType/xen/gui/XenManager/ widgets/autoReconnect root/ConnectionType/xen/gui/XenManager/ widgets/autoStartDesktop

Controls the state of the Show applications on desktop widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to readonly, the widget is visible in the read-only state.

Controls the state of the Auto reconnect widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Auto Start Desktop widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/xen/gui/XenManager/ widgets/autoStartResource root/ConnectionType/xen/gui/XenManager/ widgets/autostart root/ConnectionType/xen/gui/XenManager/ widgets/domain

Controls the state of the Auto Start Resource widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Auto start priority widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Domain widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to root > ConnectionType 129

Table E-12 root > ConnectionType > xen (continued)

Registry key Description

root/ConnectionType/xen/gui/XenManager/ widgets/fallBackConnection inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Fallback Connection widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/xen/gui/XenManager/ widgets/folder root/ConnectionType/xen/gui/XenManager/ widgets/hasDesktopIcon root/ConnectionType/xen/gui/XenManager/ widgets/isInMenu root/ConnectionType/xen/gui/XenManager/ widgets/label root/ConnectionType/xen/gui/XenManager/ widgets/password

Controls the state of the Show icon on desktop widget in the

Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Name widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Password widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/xen/gui/XenManager/ widgets/username root/ConnectionType/xen/gui/XenManager/ widgets/waitForNetwork

Controls the state of the Username widget in the Connection

Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Wait for network before connecting widget in the Connection Manager for this connection type. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/ConnectionType/xen/gui/fbpanel/autohide If set to true, the taskbar auto-hides.

root/ConnectionType/xen/gui/fbpanel/edge root/ConnectionType/xen/gui/fbpanel/hidden

Sets the default position of the taskbar when more than one published desktop or application is available.

If set to 1, the taskbar is completely hidden, but only if autoStartResource or autoStartDesktop is enabled.

130 Appendix E Registry keys

root > CpuMgr

Table E-13 root > CpuMgr

Registry key Description

root/CpuMgr/General/CpuNumber root/CpuMgr/General/EnableCpuMgr

Indicates the number of CPUs in the system. This value is readonly.

If set to 1, the CPU Manager will control system performance. If set to 0, the system will run at its default performance level.

root/CpuMgr/General/ScalingAvailableGovernors Indicates the available CPU scaling governors in the system. This value is read-only.

root/CpuMgr/General/ScalingGovernor

Sets the CPU scaling governor to use when the CPU Manager is enabled. The available governors are hardware-dependent. Some common governors are performance and ondemand. The performance governor uses the most power and configures the system to run at maximum performance, even if nothing is in use. The ondemand governor configures system resources based on the current demand and might yield the best performanceper-watt, but user performance might suffer if the system is constantly increasing or decreasing the performance. The default governor is performance. A change in governor takes effect immediately.

root > DHCP

This folder exists to support temporary registry keys that are added when the system acquires a DHCP lease.

No modification is necessary.

root > Dashboard

NOTE:

The dashboard is the same thing as the taskbar.

Table E-14 root > Dashboard

Registry key

root/Dashboard/GUI/Clock root/Dashboard/GUI/ConnectionManager root/Dashboard/GUI/ControlPanel root/Dashboard/GUI/PowerButton root/Dashboard/GUI/Search root/Dashboard/GUI/SystemInformation root/Dashboard/GUI/SystemTray root/Dashboard/GUI/TaskBar root/Dashboard/General/AlwaysOnTop root/Dashboard/General/AutoHide

Description

If set to 1, the clock is shown on the taskbar.

If set to 1, the Connection Manager button is shown on the taskbar.

If set to 1, the Control Panel button is shown on the taskbar.

If set to 1, the power button is shown on the taskbar.

If set to 1, the Search button is shown on the taskbar.

If set to 1, the System Information button is shown on the taskbar.

If set to 1, the system tray is shown on the taskbar.

If set to 1, the application area is shown on the taskbar.

If set to 1, the taskbar will always be on top.

If set to 1, the taskbar auto-hides.

root > CpuMgr 131

Table E-14 root > Dashboard (continued)

Registry key

root/Dashboard/General/EnterLeaveTimeout root/Dashboard/General/IconSize root/Dashboard/General/Length root/Dashboard/General/LengthToScreenSide root/Dashboard/General/PanelDockSide root/Dashboard/General/RemainPixel root/Dashboard/General/SlidingTimeout root/Dashboard/General/Width

Description

Sets the amount of time in milliseconds before the taskbar will hide or show when AutoHide is enabled.

Sets the size of the icons on the taskbar.

Sets the length of the taskbar.

If set to 1, the length of taskbar is fixed and equal to the length of the side of the screen to which it is anchored.

Sets the side of the screen to which the taskbar is docked.

Sets the number of pixels that are still visible when the taskbar hides.

Sets the amount of time in milliseconds that it takes for the taskbar to hide or show when AutoHide is enabled.

Sets the width of the taskbar.

root > Display

Table E-15 root > Display

Registry key Description

root/Display/Configuration/AMDOptions/

SWCursor root/Display/Configuration/displaymode root/Display/Configuration/hexlayout root/Display/Configuration/hexprofile root/Display/Configuration/primaryprofile root/Display/Configuration/quaternarymode

If set to 1, a software-rendered mouse cursor is used, which might fix issues such as cursor corruption but can introduce issues with multimedia playback and touch screens. If set to 0, a hardware-rendered mouse cursor is used, which fixes issues with multimedia playback and touch screens.

Sets the display mode. If set to 0, the standard mode (a 1–4 monitor configuration) is used. If set to 1, a 6-monitor configuration can be used, but only on supported platforms with the appropriate add-on card.

Sets the layout in 6-monitor mode.

Sets the profile used in 6-monitor mode.

Sets the profile to use for the primary monitor via the profile name. For Smart Zero, this must always be set to default.

Sets the position of the fourth monitor relative to the monitor indicated in quaternaryrelative. This is hardwaredependent and is not supported on all models. Values are defined as follows: 0=Same As; 1=Above; 2=Right Of; 3=Left Of; 4=Below.

root/Display/Configuration/quaternaryprofile Sets the profile to use for the fourth monitor via the profile name.

root/Display/Configuration/quaternaryrelative Sets which monitor is used as a reference to set the position of the fourth monitor.

root/Display/Configuration/secondaryConnector Sets the secondary connector.

root/Display/Configuration/secondarymode Sets the position of the secondary monitor relative to the primary monitor. This is hardware-dependent and is not supported on all models. Values are defined as follows: 0=Same As; 1=Above;

2=Right Of; 3=Left Of; 4=Below.

132 Appendix E Registry keys

Table E-15 root > Display (continued)

Registry key

root/Display/Configuration/ secondaryorientation root/Display/Configuration/secondaryprofile root/Display/Configuration/swapstate root/Display/Configuration/tertiarymode root/Display/Configuration/tertiaryprofile root/Display/Configuration/tertiaryrelative root/Display/Profiles/<UUID>/colorScaling root/Display/Profiles/<UUID>/depth root/Display/Profiles/<UUID>/height root/Display/Profiles/<UUID>/label root/Display/Profiles/<UUID>/orientation root/Display/Profiles/<UUID>/refresh root/Display/Profiles/<UUID>/width root/Display/userLock root/Display/userLockEngaged

Description

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the profile to use for the secondary monitor via the profile name.

Specifies which connector is connected to the primary monitor.

This is hardware-dependent and is not supported on all models.

Generally, 0 means the primary monitor is on the VGA connector and 1 means the other connector. For the t510, 0 means the primary monitor is on the DVI-I connector, and 1 means the primary monitor is on the DVI-D connector. For platforms with an add-on video card, 0 means the primary monitor is on the built-in video card, and 1 means the primary monitor is on the add-on video card.

Sets the position of the third monitor relative to the monitor indicated in tertiaryrelative. This is hardware-dependent and is not supported on all models. Values are defined as follows:

0=Same As; 1=Above; 2=Right Of; 3=Left Of; 4=Below.

Sets the profile to use for the third monitor via the profile name.

Sets which monitor is used as a reference to set the position of the third monitor.

Sets the color temperature or direct RGB scaling for thin clients with built-in monitors. The entry is a 6-digit hex value (RRGGBB), where ffffff would indicate full (100%) scaling on all three color channels.

Sets the display color depth in bits-per-pixel. A higher color depth means better quality but lower performance.

Sets the monitor resolution height. If set to 0, the resolution is auto-detected.<

Sets the display profile name. For Smart Zero, this must always be set to default.

Sets the monitor orientation as follows: 0=Normal; 1=Rotate Left;

2=Rotate Right; 3=Invert.

Sets the desired monitor refresh rate. Not all refresh rates are supported for all resolutions. If set to 0, the refresh rate is autodetected. The supported values are dependent on the monitor.

Setting a refresh rate that is not supported by the attached monitor will lead to a black screen. HP recommends leaving this set to 0.

Sets the monitor resolution width. If set to 0, the resolution is auto-detected.

If set to 1, and if the display settings have been modified by the user, the display settings are preserved when importing a ThinPro profile.

This registry key is set to 1 automatically after the display settings have been modified by the user. You normally do not need to modify this setting.

root > Display 133

root > Network

Table E-16 root > Network

Registry key Description

root/Network/ActiveDirectory/Domain root/Network/ActiveDirectory/DynamicDNS root/Network/ActiveDirectory/Enabled root/Network/ActiveDirectory/Method root/Network/ActiveDirectory/Password root/Network/ActiveDirectory/Username

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

root/Network/DNSServers root/Network/DefaultHostnamePattern root/Network/FtpProxy root/Network/Hostname root/Network/HttpProxy root/Network/HttpsProxy

Additional DNS servers for domain name resolution can be specified here. The specified servers will be used in addition to any servers retrieved via DHCP. Up to three IPv4 or IPv6 addresses can be specified, separated by commas.

Sets the default hostname pattern to use when generating a new hostname. This is used if the Hostname registry key and /etc/ hostname are both empty. The hostname pattern uses % as a delimiter. In the example HPTC%MAC:1-6%, HPTC would be the prefix, and the first six characters of the thin client MAC address would follow. So if the MAC address of the thin client is

11:22:33:44:55:66, the generated hostname would be

HPTC112233. If the pattern is TC%MAC%, the generated hostname would be TC112233445566. If the pattern is HP

%MAC:7%, the generated hostname would be HP1122334.

Sets the FTP proxy address. HP recommends using the following format for this value because the http prefix is better supported: http://ProxyServer:Port

Sets the hostname of the thin client.

Sets the HTTP proxy address. HP recommends using the following format: http://ProxyServer:Port

Sets the HTTPS proxy address. HP recommends using the following format for this value because the http prefix is better supported: http://ProxyServer:Port root/Network/IPSec/IPSecRules/<UUID>/DstAddr

Sets the destination address for the IPSec rule.

root/Network/IPSec/IPSecRules/<UUID>/

MMAuthMethod

Sets the authentication method for the IPSec rule. PSK is for using a pre-shared key, and Certificate is for using certificate files.

root/Network/IPSec/IPSecRules/<UUID>/

MMAuthMethodCACert root/Network/IPSec/IPSecRules/<UUID>/

MMAuthMethodClientCert

If the authentication method is Certificate, the CA certificate file path is saved in this registry key.

If the authentication method is Certificate, the client certificate file path is saved in this registry key.

134 Appendix E Registry keys

Table E-16 root > Network (continued)

Registry key Description

root/Network/IPSec/IPSecRules/<UUID>/

MMAuthMethodPresharedKey root/Network/IPSec/IPSecRules/<UUID>/

MMAuthMethodPrivateKey

If the authentication method is PSK, the pre-shared key value is saved in this registry key.

If the authentication method is Certificate, the private key file path that corresponds with the client certificate is saved in this registry key.

Sets the phase 1 Diffie-Hellman group.

root/Network/IPSec/IPSecRules/<UUID>/

MMDHGroup root/Network/IPSec/IPSecRules/<UUID>/

MMEncryptionAlg root/Network/IPSec/IPSecRules/<UUID>/

MMIntegrityAlg root/Network/IPSec/IPSecRules/<UUID>/

MMLifetimeMinutes root/Network/IPSec/IPSecRules/<UUID>/

QMAHEnable root/Network/IPSec/IPSecRules/<UUID>/

QMAHIntegrityAlg root/Network/IPSec/IPSecRules/<UUID>/

QMESPEnable root/Network/IPSec/IPSecRules/<UUID>/

QMESPEncryptionAlg root/Network/IPSec/IPSecRules/<UUID>/

QMESPIntegrityAlg root/Network/IPSec/IPSecRules/<UUID>/

QMLifetimeSeconds

Sets the phase 1 encryption algorithm.

Sets the phase 1 integrity algorithm.

Sets the phase 1 lifetime.

Enables phase 2 AH.

Sets the phase 2 AH integrity algorithm.

Enables phase 2 ESP.

Sets the phase 2 ESP encryption algorithm.

Sets the phase 2 ESP integrity algorithm.

Sets the phase 2 lifetime.

root/Network/IPSec/IPSecRules/<UUID>/

RuleDescription root/Network/IPSec/IPSecRules/<UUID>/

RuleEnable

Sets the description for the IPSec rule.

If set to 1, the rule is enabled.

root/Network/IPSec/IPSecRules/<UUID>/RuleName Sets the name for the IPSec rule.

root/Network/IPSec/IPSecRules/<UUID>/SrcAddr Sets the source address for the IPSec rule.

Sets the tunnel destination address for the IPSec rule.

root/Network/IPSec/IPSecRules/<UUID>/

TunnelDstAddr root/Network/IPSec/IPSecRules/<UUID>/

TunnelEnable

Enables tunnel mode for the IPSec rule.

root/Network/IPSec/IPSecRules/<UUID>/

TunnelSrcAddr root/Network/KeepPreviousDNS

Sets the tunnel source address for the IPSec rule.

root/Network/SearchDomains

If set to 1, previously-configured DNS servers and search domains not generated by the Network Manager will be kept in resolv.conf.

If set to 0, resolv.conf will be overwritten completely.

Additional search domains for FQDN resolution can be specified here. The specified domains will be appended to any incomplete server definitions in an attempt to generate an FQDN that can be resolved via DNS. For example, a search domain of root > Network 135

Table E-16 root > Network (continued)

Registry key

root/Network/VPN/AutoStart root/Network/VPN/PPTP/Domain root/Network/VPN/PPTP/Gateway root/Network/VPN/PPTP/Password root/Network/VPN/PPTP/Username root/Network/VPN/Type root/Network/VPN/VPNC/Domain root/Network/VPN/VPNC/Gateway root/Network/VPN/VPNC/Group root/Network/VPN/VPNC/GroupPassword root/Network/VPN/VPNC/IKEDHGroup root/Network/VPN/VPNC/LocalUDPPort root/Network/VPN/VPNC/NATTMode root/Network/VPN/VPNC/Password root/Network/VPN/VPNC/PerfectForwardSecrecy root/Network/VPN/VPNC/Security root/Network/VPN/VPNC/Username root/Network/Wired/DefaultGateway root/Network/Wired/EnableDefGatewayAsDNS root/Network/Wired/EthernetSpeed root/Network/Wired/IPAddress root/Network/Wired/IPv6Enable root/Network/Wired/Interface root/Network/Wired/MTU

Description

mydomain.com will allow the server definition myserver to resolve properly to myserver.mydomain.com, even if the

DNS server does not have myserver in its name resolution tables. Up to five additional search domains can be specified.

If set to 1, VPN starts automatically when the system starts up.

Sets the PPTP domain.

Sets the PPTP gateway.

Sets the PPTP user password.

Sets the PPTP username.

Sets the VPN type.

Sets the VPNC domain.

Sets the VPNC gateway.

Sets the VPNC group.

Sets the VPNC group password.

Sets the VPNC IKE Diffie-Hellman group.

Sets the local UDP port to use for VPNC. If set to 0, a random port will be used. This setting is valid only when the NAT traversal mode (NATTMode) is cisco-udp.

Sets the VPNC NAT traversal mode.

Sets the VPNC user password.

Sets the VPNC Diffie-Hellman group to use for Perfect Forward

Secrecy (PFS).

Sets the VPNC security level.

Sets the VPNC username.

Sets the default gateway the device will use to communicate with the Internet. Typically this is the IP address of the router. This setting will only take effect when Method is set to Static.

If set to 1, the default gateway will also be the name server.

Sets the link speed of the primary Ethernet network interface.

Automatic allows the fastest available link speed to be used, which is usually 1 Gbps or 100 Mbps/Full depending on the switch.

The link speed can also be forced to a single speed (100 Mbps or

10 Mbps) and duplex mode (Full or Half) to support switches and hubs that do not perform appropriate auto-negotiation.

Sets the IPv4 address of the thin client. This setting will only take effect when Method is set to Static.

If set to 1, IPv6 is enabled.

Sets the default Ethernet interface or NIC.

Sets the MTU. It does not matter if the IP address is static or

DHCP-acquired.

136 Appendix E Registry keys

Table E-16 root > Network (continued)

Registry key Description

root/Network/Wired/Method root/Network/Wired/Security/CACert

If set to Automatic, the thin client will use DHCP to attempt to retrieve network settings. If set to Static, the values of the

IPAddress, SubnetMask, and DefaultGateway registry keys are used. HP does not recommend using Static in a generic ThinPro profile because it will cause all thin clients to receive the same IP address.

Sets the path to CA certificate file.

root/Network/Wired/Security/EnableMachineAuth If set to 1, machine authentication for PEAP is enabled.

root/Network/Wired/Security/Identity root/Network/Wired/Security/InnerAuth root/Network/Wired/Security/InnerAuthTTLS

Sets the identity or anonymous identity.

Sets the PEAP inner authentication protocol.

Sets the TTLS inner authentication protocol.

root/Network/Wired/Security/PEAPVersion root/Network/Wired/Security/Password root/Network/Wired/Security/PrivateKey root/Network/Wired/Security/Type root/Network/Wired/Security/UserCert

Sets the PEAP version.

Sets the password.

Sets the path to a private key file. This is only used for TLS authentication.

Sets the 802.1x authentication type.

root/Network/Wired/Security/Username root/Network/Wired/SubnetMask root/Network/Wireless/DefaultGateway root/Network/Wireless/EnableDefGatewayAsDNS root/Network/Wireless/IPAddress

Sets the path to a user certificate file. This is only used for TLS authentication.

Sets the username.

Sets the subnet mask of the device, such as 255.255.255.0 (for a standard class C subnet). This setting will only take effect when

Method is set to Static.

Sets the default gateway the device will use to communicate with the Internet. Typically this is the IP address of the router. This setting will only take effect when Method is set to Static.

If set to 1, the default gateway will also be the name server.

Sets the IPv4 address of the thin client. This setting will only take effect when Method is set to Static.

root/Network/Wireless/IPv6Enable root/Network/Wireless/Interface root/Network/Wireless/Method root/Network/Wireless/PowerEnable root/Network/Wireless/SSID root/Network/Wireless/SSIDHidden root/Network/Wireless/SSIDWhiteList

If set to 1, IPv6 is enabled.

Sets the default wireless interface or wireless network adapter.

If set to Automatic, the thin client will use DHCP to attempt to retrieve network settings. If set to Static, the values of the

IPAddress, SubnetMask, and DefaultGateway registry keys are used. HP does not recommend using Static in a generic ThinPro profile because it will cause all thin clients to receive the same IP address.

If set to 1, power management of the wireless network card is enabled.

Sets the wireless access point to use via its SSID.

Specifies if the SSID of the wireless access point is hidden.

Specifies a whitelist for wireless access points. If this registry key's value is not empty, only the SSIDs specified in the value will root > Network 137

Table E-16 root > Network (continued)

Registry key Description

root/Network/Wireless/Security/CACert root/Network/Wireless/Security/EAPFASTPAC root/Network/Wireless/Security/

EAPFASTProvision root/Network/Wireless/Security/Identity root/Network/Wireless/Security/InnerAuth

Sets the identity or anonymous identity.

Sets the PEAP inner authentication protocol.

root/Network/Wireless/Security/InnerAuthTTLS Sets the TTLS inner authentication protocol.

root/Network/Wireless/Security/PEAPVersion root/Network/Wireless/Security/Password

Sets the PEAP version.

root/Network/Wireless/Security/PrivateKey

Sets the password.

Sets the path to a private key file. This is only used for TLS authentication.

root/Network/Wireless/Security/Type root/Network/Wireless/Security/UserCert root/Network/Wireless/Security/Username root/Network/Wireless/Security/WEPAuth root/Network/Wireless/Security/WEPIndex root/Network/Wireless/SubnetMask root/Network/disableLeftClickMenu be shown in the wireless access point scan results. Use a semicolon to separate the SSIDs.

Sets the path to CA certificate file.

Sets the path to the PAC file for EAP FAST authentication.

Sets the provisioning option for EAP FAST authentication.

Sets the wireless authentication type.

Sets the path to a user certificate file. This is only used for TLS authentication.

Sets the username.

Sets the WEP authentication type.

Sets the WEP password index.

Sets the subnet mask of the device, such as 255.255.255.0 (for a standard class C subnet). This setting will only take effect when

Method is set to Static.

If set to 1, the left-click menu for the network system tray icon is disabled.

root/Network/disableRightClickMenu root/Network/iPeak/ShowStatus root/Network/iPeak/Status root/Network/userLock root/Network/userLockEngaged

If set to 1, the right-click menu for the network system tray icon is disabled.

If set to 1, the HP Velocity status is displayed as part of the system tray icon. HP Velocity is not supported on the HP t420.

If set to 1, HP Velocity is enabled. If set to 2, HP Velocity is enabled in Monitor mode. If set to 0, HP Velocity is disabled. HP

Velocity is not supported on the HP t420.

If set to 1, and if the network settings have been modified by the user, the network settings are preserved when importing a

ThinPro profile.

This registry key is set to 1 automatically after the network settings have been modified by the user. You normally do not need to modify this setting.

138 Appendix E Registry keys

root > SCIM

Table E-17 root > SCIM

Registry key

root/SCIM/ScimEnabled

Description

If set to 1, SCIM is enabled for Chinese, Japanese, and Korean input.

root > ScepMgr

Table E-18 root > ScepMgr

Registry key Description

root/ScepMgr/General/AutoRenew/Enabled root/ScepMgr/General/AutoRenew/TimeFrame root/ScepMgr/IdentifyingInfo/CommonName

If set to 1, certificates will be renewed automatically before they expire.

Sets the number of days before a certificate's expiration date that the SCEP Manager will try to renew the certificate automatically.

Sets the common name to use for SCEP identifying information, such as your name or the Fully-Qualified Domain Name (FQDN) of the device. The FQDN is used by default if this value is left empty.

Sets the country or region to use for SCEP identifying information.

root/ScepMgr/IdentifyingInfo/CountryName root/ScepMgr/IdentifyingInfo/EmailAddress root/ScepMgr/IdentifyingInfo/LocalityName

Sets the email address to use for SCEP identifying information.

Sets the locality name to use for SCEP identifying information, such as a city name.

root/ScepMgr/IdentifyingInfo/OrganizationName Sets the organization name to use for SCEP identifying information, such as a company name or government organization name.

root/ScepMgr/IdentifyingInfo/

OrganizationUnitName

Sets the organizational unit name to use for SCEP identifying information, such as a department name or section name.

root/ScepMgr/IdentifyingInfo/StateName root/ScepMgr/ScepEnroll/ScepServers/<UUID>/

CertFileChanged root/ScepMgr/ScepEnroll/ScepServers/<UUID>/

KeySize root/ScepMgr/ScepEnroll/ScepServers/<UUID>/

ServerName

Sets the state or province to use for SCEP identifying information.

The registry key is used only to inform other applications that a certificate file has changed. This should not need to be modified.

Sets the key size to use for the generated key pair.

Sets the SCEP server name.

root/ScepMgr/ScepEnroll/ScepServers/<UUID>/

ServerUrl root/ScepMgr/ScepEnroll/ScepServers/<UUID>/

Status/Code root/ScepMgr/ScepEnroll/ScepServers/<UUID>/

Status/Detail

Sets the SCEP server URL, which is necessary for the SCEP client to enroll a certificate.

Contains the status code of the SCEP enrollment. This value is read-only.

Contains detailed information about the SCEP enrollment. This value is read-only.

root > SCIM 139

root > Search

Table E-19 root > Search

Registry key Description

root/Search/Category/Applications/

ConnectionManager/checked root/Search/Category/Applications/

ConnectionManager/enabled root/Search/Category/Applications/

Connections/checked root/Search/Category/Applications/

Connections/enabled root/Search/Category/Applications/

ControlPanel/checked root/Search/Category/Applications/

ControlPanel/enabled root/Search/Category/Applications/Desktop/ checked root/Search/Category/Applications/Desktop/ enabled root/Search/Category/Applications/icon root/Search/Category/Applications/name root/Search/Category/FileSystem/caseSensitive root/Search/Category/FileSystem/enabled root/Search/Category/FileSystem/folderFilter Specifies the folders in the filesystem that the user will be allowed to search. Use a semicolon to separate folders. For example: /home/user;/usr/bin root/Search/Category/FileSystem/location root/Search/Category/FileSystem/subFolder root/Search/Category/Miscellaneons/

CheckForUpdate root/Search/Category/Miscellaneons/Logout root/Search/Category/Miscellaneons/Reboot root/Search/Category/Miscellaneons/ShutDown root/Search/Category/Miscellaneons/Sleep root/Search/Category/Miscellaneons/

SwitchToAdmin root/Search/Category/Regeditor/byDir root/Search/Category/Regeditor/byKey root/Search/Category/Regeditor/byValue

140 Appendix E Registry keys

Table E-19 root > Search (continued)

Registry key

root/Search/Category/Regeditor/byWhole root/Search/GUI/showCategory

root > Serial

Table E-20 root > Serial

Registry key

root/Serial/<UUID>/baud root/Serial/<UUID>/dataBits root/Serial/<UUID>/device root/Serial/<UUID>/flow root/Serial/<UUID>/name root/Serial/<UUID>/parity

Description

Description

Sets the speed of the serial device.

Sets how many bits are in each character.

Specifies the serial device attached to the system.

Sets the flow control of the serial device, which is used to communicate stops and starts of the serial communication.

Specifies the Windows device port for communicating with the serial device.

Sets the parity bit of the serial device. The parity bit is used for error detection. If set to none, there is no parity detection.

root > SystemInfo

Table E-21 root > SystemInfo

Registry key Description

root/SystemInfo/Pages/General root/SystemInfo/Pages/NetTools

If set to 0, the General tab of the System Information window is hidden from standard users.

If set to 0, the Net Tools tab of the System Information window is hidden from standard users.

root/SystemInfo/Pages/Network If set to 0, the Network tab of the System Information window is hidden from standard users.

root/SystemInfo/Pages/SoftwareInformationTab/

ServicePacks

If set to 0, the Service Packs tab in the Software Information section of the System Information window is hidden from standard users.

root/SystemInfo/Pages/SoftwareInformationTab/

SoftwareInformation

If set to 0, the Software Information tab of the System

Information window is hidden from standard users.

root/SystemInfo/Pages/SoftwareInformationTab/

SoftwareInstalled

If set to 0, the Software Installed tab in the Software

Information section of the System Information window is hidden from standard users.

root/SystemInfo/Pages/SystemLogs root/SystemInfo/authorized

If set to 0, the System Logs tab of the System Information window is hidden from standard users.

If set to 0, the System Information button on the taskbar is disabled for standard users.

root > Serial 141

root > TaskMgr

Table E-22 root > TaskMgr

Registry key

root/TaskMgr/General/AlwaysOnTop

root > USB

Table E-23 root > USB

Registry key

root/USB/Classes/<ClassType>/ClassID root/USB/Classes/<ClassType>/DisplayName root/USB/Classes/<ClassType>/State root/USB/Classes/<ClassType>/Visible root/USB/Classes/ShowTab root/USB/Devices/<UUID>/DisplayName root/USB/Devices/<UUID>/ProductID root/USB/Devices/<UUID>/State root/USB/Devices/<UUID>/VendorID root/USB/root/autoSwitchProtocol root/USB/root/mass-storage/allowed root/USB/root/mass-storage/read-only root/USB/root/opendebug root/USB/root/protocol

Description

If set to 1, the Task Manager window is always on top.

Description

Sets the USB class ID number.

Sets the USB class name.

Sets whether the class is mapped to the remote host.

Sets whether the class is shown in the UI, not shown in the UI, or disabled.

If set to 1, the Classes section is shown in the USB Manager.

Sets the name to show in the USB Manager. If not supplied, the

USB Manager will attempt to generate an appropriate name using device information.

Sets the product ID of the device.

Sets whether this device is mapped to the remote host as follows:

0=Do Not Redirect; 1=Use Defaults; 2=Redirect.

Sets the vendor ID of the device.

If set to 1, the remote USB protocol will switch automatically based on which protocol is chosen.

If set to 1, mass storage devices will be mounted automatically when the protocol is local.

If set to 1, when mass storage devices are mounted automatically, they will be mounted as read-only.

If set to 1, a debug message will be written to /tmp/USB-mgrlog.

Sets which protocol owns remote USB. Valid values depend on which protocols are installed on the system but can include local, xen, freerdp, and view.

root > auto-update

Table E-24 root > auto-update

Registry key

root/auto-update/DNSAliasDir

Description

Sets the default root directory for DNS alias mode on the server hosting HP Smart Client Services.

142 Appendix E Registry keys

Table E-24 root > auto-update (continued)

Registry key Description

root/auto-update/ManualUpdate root/auto-update/ScheduledScan/Enabled root/auto-update/ScheduledScan/Interval root/auto-update/ScheduledScan/Period

If set to 1, the DHCP tag, DNS alias, and broadcast update methods for Automatic Update are disabled. When performing a manual update, the password, path, protocol, user, and

ServerURL registry keys must be set to ensure the update server is known.

If set to 1, the thin client performs periodic scans of the

Automatic Update server to check for updates. If set to 0, the thin client will only check for updates at system startup.

Sets the amount of time to wait between scheduled update scans.

This should be specified in the HH:MM format. Intervals longer than 24 hours can be specified. For example, to have the scans occur every 48 hours, set this to 48:00.

Thin clients will randomly activate their scheduled scan throughout the defined period. Using a long period avoids cases where all thin clients update at exactly the same, which could cause network congestion. The period should be specified in the

HH:MM format. For example, to spread thin client updates over a

2.5-hour period, set this to 02:30.

root/auto-update/ScheduledScan/StartTime root/auto-update/ServerURL

Sets the start time of the first scheduled update scan period in the format HH:MM, using the 24-hour time format. For example, 4:35 p.m. would be 16:35.

Sets the IP address or domain name of the update server used when ManualUpdate is enabled.

If set to 1, the Automatic Update system tray icon is enabled.

If set to 1, Automatic Update is enabled at system startup.

root/auto-update/VisibleInSystray root/auto-update/enableOnBootup root/auto-update/enableSystrayLeftClickMenu If set to 1, the left-click menu for the Automatic Update system tray icon is enabled.

root/auto-update/enableSystrayRightClickMenu If set to 1, the right-click menu for the Automatic Update system tray icon is enabled.

root/auto-update/gui/auto-update/ManualUpdate Controls the state of the Enable manual configuration widget in the Automatic Update utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

root/auto-update/gui/auto-update/ServerURL Controls the state of the Server widget in the Automatic Update utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

root/auto-update/gui/auto-update/ enableOnBootup root/auto-update/gui/auto-update/password

Controls the state of the Enable Automatic Update on system

startup widget in the Automatic Update utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Password widget in the Automatic

Update utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

root > auto-update 143

Table E-24 root > auto-update (continued)

Registry key

root/auto-update/gui/auto-update/protocol root/auto-update/gui/auto-update/tag root/auto-update/gui/auto-update/user root/auto-update/password root/auto-update/path root/auto-update/preserveConfig root/auto-update/protocol root/auto-update/tag root/auto-update/user

Description

Controls the state of the Protocol widget in the Automatic Update utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the User name widget in the Automatic

Update utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

Sets the password used when ManualUpdate is enabled. This is only used when protocol is set to ftp. This value will be encrypted.

Sets the relative path from the default server URL for when

ManualUpdate is enabled. Typically, this is empty or set to auto-update.

If set to 1, the current thin client configuration settings will be preserved when an image update occurs via Automatic Update.

Sets the protocol used when ManualUpdate is enabled.

This registry key is obsolete. It previously set the tag number used for DHCP (137). This is now detected via the tag name auto-update.

Sets the username used when ManualUpdate is enabled. This is only used when 'protocol' is set to 'ftp'.

root > background

Table E-25 root > background

Registry key

root/background/desktop/color root/background/desktop/imagePath root/background/desktop/lastBrowseDir root/background/desktop/style root/background/desktop/theme

Description

If theme is set to none, this key stores the color used by the user-defined theme.

If theme is set to none, this key stores the desktop background image path used by the user-defined theme.

If theme is set to none, this key stores the last used directory.

If theme is set to none, this key stores how the background image is placed on the desktop (such as center, tile, stretch, fit, and fill).

Specifies the system theme setting. This value is set via the

Background Manager utility in the Control Panel. The valid values depend on the themes that exist on the system. This can be set to none to let the user define the theme, to auto to have the system automatically set the appropriate protocol's theme for

Smart Zero, or to default to use the default theme for ThinPro.

144 Appendix E Registry keys

root > config-wizard

Table E-26 root > config-wizard

Registry key

root/config-wizard/FirmwareUpdate/ firmwareUpdateTimeout root/config-wizard/FirmwareUpdate/ firmwareUpdateURL root/config-wizard/FirmwareUpdate/ preserveConfig root/config-wizard/enableConnectionCheck root/config-wizard/enableNetworkCheck root/config-wizard/updateCheck

root > desktop

Table E-27 root > desktop

Registry key

root/desktop/shortcuts/<action>/command root/desktop/shortcuts/<action>/enabled root/desktop/shortcuts/<action>/shortcut

root > entries

Table E-28 root > entries

Registry key

root/entries/<UUID>/command root/entries/<UUID>/folder root/entries/<UUID>/icon root/entries/<UUID>/label root/entries/<UUID>/metaInfo root/entries/<UUID>/onDesktop root/entries/<UUID>/onMenu

Description

Sets the command that is run by the shortcut.

If set to 1, the shortcut is enabled.

Sets the shortcut name.

Description

Description

Sets the timeout period in seconds for when checking for updates.

If set to -1, there is no timeout.

Sets the FTP URL for image updates.

If set to 1, the current thin client configuration settings will be preserved when an image update occurs via the initial configuration wizard.

If set to 1, the connection check at system startup is enabled.

If set to 1, the network check at system startup is enabled.

If set to 1, the update check at system startup is enabled.

root > config-wizard 145

root > keyboard

Table E-29 root > keyboard

Registry key

root/keyboard/DrawLocaleLetter root/keyboard/SystrayMenu/keyboardLayout root/keyboard/SystrayMenu/languages root/keyboard/SystrayMenu/virtualKeyboard root/keyboard/VisibleInSystray root/keyboard/XkbLayout root/keyboard/XkbModel root/keyboard/XkbOptions root/keyboard/XkbVariant root/keyboard/enable2 root/keyboard/layout root/keyboard/layout2 root/keyboard/model root/keyboard/model2 root/keyboard/numlock root/keyboard/rdp_kb root/keyboard/switch root/keyboard/variant root/keyboard/variant2

Description

If set to 1, the keyboard system tray icon will draw the language locale string instead of using static images.

If set to 1, the right-click menu on the keyboard system tray icon offers an option to open the Keyboard Layout utility in the Control

Panel.

If set to 1, the right-click menu on the keyboard system tray icon offers an option to open the Language utility in the Control Panel.

If set to 1, the right-click menu on the keyboard system tray icon offers an option to open the virtual keyboard.

If set to 1, the keyboard system tray icon is displayed and indicates the current keyboard layout.

This is an internal key used to map to an XKB keyboard layout.

This key should not need to be modified.

This is an internal key used to map to an XKB keyboard model.

This key should not need to be modified.

This is an internal key used to map to XKB keyboard options. This key should not need to be modified.

This is an internal key used to map to an XKB keyboard variant.

This key should not need to be modified.

If set to 1, the secondary keyboard layout can be switched to via the keyboard shortcut defined by switch.

Sets the primary keyboard layout.

Sets the secondary keyboard layout.

Sets the primary keyboard model.

Sets the secondary keyboard model.

If set to 1, the Num Lock function is enabled at system startup.

This is an internal key used to map to an RDP keyboard map. This key should not need to be modified.

Sets the keyboard shortcut for switching between the first and second keyboard layout (enable2 must also be set to 1). Valid values are as follows: grp:ctrl_shift_toggle, grp:ctrl_alt_toggle, grp:alt_shift_toggle.

Sets the primary keyboard variant.

Sets the secondary keyboard variant.

146 Appendix E Registry keys

root > logging

Table E-30 root > logging

Registry key

root/logging/general/debug root/logging/general/debugLevel root/logging/general/showDebugLevelBox

Description

If set to 1, debugging is enabled for all debug-supported subsystems. This is usually used in conjunction with generateDiagnostic.sh or the System Information

Diagnostic tool to generate a diagnostic bundle with system debug logs included.

Sets the debug level. This value will be leveraged by other modules to generate the corresponding logs.

If set to 1, the Debug level option on the System Logs tab of the

System Information window will be available to standard users.

If set to 0, the option is available to administrators only.

root > mouse

Table E-31 root > mouse

Registry key

root/mouse/MouseHandedness root/mouse/MouseSpeed root/mouse/MouseThreshold

Description

If set to 0, the mouse is right-handed. If set to 1, the mouse is left-handed.

Sets the acceleration of the mouse pointer. Typically, a value from

0 to 25 is in the usable range. A value of 0 completely disables acceleration, causing the mouse to move at a constant slow, but measurable pace.

Sets the number of pixels before mouse acceleration is enabled. A value of 0 sets the acceleration to a natural curve that gradually scales acceleration, allowing for both precise and quick movements.

root > restore-points

Table E-32 root > restore-points

Registry key

root/restore-points/factory

root > screensaver

Table E-33 root > screensaver

Registry key

root/screensaver/SlideShowAllMonitors

Description

Specifies which snapshot to use for a factory reset.

Description

If set to 1, the screen saver slide show will be shown on all monitors. If set to 0, the slide show will be shown on the primary monitor only.

root > logging 147

Table E-33 root > screensaver (continued)

Registry key

root/screensaver/SlideShowInterval root/screensaver/SlideShowPath root/screensaver/enableCustomLogo root/screensaver/enableDPMS root/screensaver/enableScreensaver root/screensaver/enableSleep root/screensaver/lockScreen root/screensaver/logoPath root/screensaver/mode root/screensaver/off root/screensaver/origImageCopyPath root/screensaver/standby root/screensaver/suspend root/screensaver/timeoutScreensaver root/screensaver/timeoutSleep

root > security

Table E-34 root > security

Registry key

root/security/mustLogin

Description

Sets the interval in seconds for switching images in the screen saver slide show.

Specifies the directory that contains the images for the screen saver slide show.

If set to 1, the custom image defined in logoPath is used for the screen saver.

If set to 0, monitor power management is disabled. This causes the monitor to always stay on unless turned off manually.

If set to 1, the screen saver is enabled.

If set to 1, sleep mode is enabled.

If set to 1, a password is required to return to the desktop from the screen saver.

Sets the path to a custom image to use for the screen saver.

Sets the rendering mode for the screen saver image (such as

Center, Tile, and Stretch). If set to Default, the image is displayed without any processing. If set to SlideShow, the screen saver will cycle through images in the directory specified by SlideShowPath.

Sets the timeout delay in minutes before the monitor turns off.

This is the path where the custom image is saved when mode is set to Default.

Sets the timeout delay in minutes before the monitor goes into standby mode.

Sets the timeout delay in minutes before the monitor goes into suspend mode.

Sets the timeout delay in minutes before the screen saver starts.

Sets the timeout delay in minutes before the thin client goes into sleep mode.

Description

If set to 1, all users are forced to log in before accessing the desktop.

148 Appendix E Registry keys

root > sshd

Table E-35 root > sshd

Registry key

root/sshd/enabled root/sshd/userAccess

root > time

Table E-36 root > time

Registry key

root/time/NTPServers root/time/TimeServerIPAddress root/time/WebServerURL root/time/timezone root/time/use24HourFormat root/time/useDHCPTimezone root/time/useNTPServers

Description

If set to 1, the SSH daemon is enabled and the thin client can be accessed via SSH.

If set to 1, standard users can connect to the thin client via SSH.

Description

Specifies NTP servers to use via a comma-separated list. Private

NTP servers or large virtual NTP clusters such as pool.ntp.org are the best choices to minimize server load.

Clear this value to return to using DHCP servers (tag 42) instead of a fixed list.

Sets the time server used by the Linux net command. These servers are typically the domain controller servers on the corporate network. This should be used when NTP servers are not configured or they are not responding. The Linux net command identifies this server on its own. However, specific server IP addresses can be provided here if desired.

Sets the web server URL (such as hp.com) to use when fetching the time using the http protocol. This URL can be within an intranet or over the Internet.

Sets the time zone. Time zones should be specified as defined by

Linux Timezone in the Date and Time utility in the Control Panel, and they should be in the following format: <region>/

<subregion>.

If set to -1, the system chooses the format automatically according to the locale. If set to 0, the a.m./p.m. format is used. If set to 1, the 24-hour format is used.

If set to 1, the thin client will attempt to set the time zone via

DHCP. To properly set the time zone via this registry key, ensure that the DHCP server for the thin client forwards the tcode DHCP tag (which is usually tag 101, although 100 and 2 can work also).

If set to 1, the use of NTP time servers to synchronize the thin client clock is enabled. If this is enabled, ensure that an NTP server is specified via DHCP or via NTPServers.

root > sshd 149

root > touchscreen

Table E-37 root > touchscreen

Registry key

root/touchscreen/calibrated root/touchscreen/enabled root/touchscreen/maxx root/touchscreen/maxy root/touchscreen/minx root/touchscreen/miny root/touchscreen/port root/touchscreen/swapx root/touchscreen/swapy root/touchscreen/type

Description

This registry key is either used internally or reserved for future use. The value should not be changed.

If set to 1, the touch screen input is enabled.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Specifies the port that is connected to the touch screen.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Specifies the controller type of the touch screen.

root > translation

Table E-38 root > translation

Registry key Description

root/translation/coreSettings/localeMapping/

<LanguageCode> root/translation/coreSettings/localeSettings Sets the locale for the thin client. This locale will also be forwarded to the remote connection. Valid locales are en_US

(English), de_DE (German), es_ES (Spanish), fr_FR (French), ru_RU (Russian), ja_JP (Japanese), ko_KR (Korean), zh_CN

(Simplified Chinese), and zh_TW (Traditional Chinese).

root/translation/gui/LocaleManager/name

These are internal keys used to provide the text string next to the appropriate language on the language selector. These keys should not need to be modified.

root/translation/gui/LocaleManager/status

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

root/translation/gui/LocaleManager/title root/translation/gui/LocaleManager/widgets/ localeSettings

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the locale setting widget in the Language utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

150 Appendix E Registry keys

root > usb-update

Table E-39 root > usb-update

Registry key

root/usb-update/authentication root/usb-update/enable root/usb-update/height root/usb-update/searchMaxDepth root/usb-update/width

Description

If set to 1, an administrator password is required to do USB updates.

If set to 1, USB update auto-detection is enabled.

Sets the height of the USB Update window in pixels.

Sets the depth of subdirectories to be searched for updates.

Setting a high search depth can cause delays on USB flash drives that have thousands of directories.

The width of the USB Update window in pixels.

root > users

Table E-40 root > users

Registry key

root/users/gui/hptc-user-rights/name root/users/gui/hptc-user-rights/status root/users/gui/hptc-user-rights/title root/users/root/password root/users/user/SSO

Description

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Sets the administrator password. If empty, Administrator Mode is locked.

This registry key is either used internally or reserved for future use. The value should not be changed.

root/users/user/WOL root/users/user/XHostCheck

If set to 1, Wake On LAN (WOL) is enabled.

If set to 1, only the systems listed under root/users/user/ xhosts are allowed to remotely control the thin client.

If set to 1, the AD/DDNS Manager is accessible by standard users.

root/users/user/apps/hptc-ad-dns-mgr/ authorized root/users/user/apps/hptc-agent-mgr/ authorized root/users/user/apps/hptc-auto-update/ authorized root/users/user/apps/hptc-background-mgr/ authorized

If set to 1, the HPDM Agent is accessible by standard users.

If set to 1, the Automatic Update utility is accessible by standard users.

If set to 1, the Background Manager is accessible by standard users.

root/users/user/apps/hptc-cert-mgr/authorized If set to 1, the Certificate Manager is accessible by standard users.

root/users/user/apps/hptc-clientaggregationmgr/authorized

If set to 1, the Client Aggregation utility is accessible by standard users.

root > usb-update 151

Table E-40 root > users (continued)

Registry key Description

root/users/user/apps/hptc-date-mgr/authorized If set to 1, the Date and Time utility is accessible by standard users.

root/users/user/apps/hptc-dhcp-mgr/authorized

If set to 1, the DHCP Option Manager is accessible by standard users.

root/users/user/apps/hptc-display-prefs/ authorized root/users/user/apps/hptc-easy-update/ authorized

If set to 1, the Display Preferences utility is accessible by standard users.

If set to 1, the Easy Update utility is accessible by standard users.

root/users/user/apps/hptc-i18n-mgr/authorized If set to 1, the Language utility is accessible by standard users.

root/users/user/apps/hptc-keyboard-layout/ authorized root/users/user/apps/hptc-mixer/authorized

If set to 1, the Keyboard Layout utility is accessible by standard users.

If set to 1, the Sound utility is accessible by standard users.

root/users/user/apps/hptc-mouse/authorized If set to 1, the Mouse utility is accessible by standard users.

root/users/user/apps/hptc-network-mgr/ authorized

If set to 1, the Network Manager is accessible by standard users.

root/users/user/apps/hptc-printer-mgr/ authorized

If set to 1, the Printers utility is accessible by standard users.

root/users/user/apps/hptc-restore/authorized If set to 1, the Snapshots utility is accessible by standard users.

root/users/user/apps/hptc-screenlock-mgr/ authorized

If set to 1, the Screensaver utility is accessible by standard users.

root/users/user/apps/hptc-security/authorized If set to 1, the Security utility is accessible by standard users.

root/users/user/apps/hptc-shortcut-mgr/ authorized

If set to 1, the Keyboard Shortcut Manager is accessible by standard users.

root/users/user/apps/hptc-sshd-mgr/authorized If set to 1, the SSHD Manager is accessible by standard users.

root/users/user/apps/hptc-task-mgr/authorized If set to 1, the Task Manager is accessible by standard users.

root/users/user/apps/hptc-text-editor/ authorized

If set to 1, the Text Editor is accessible by standard users.

If set to 1, the ThinState utility is accessible by standard users.

root/users/user/apps/hptc-thinstate/ authorized root/users/user/apps/hptc-touchscreen/ authorized

If set to 1, the Touch Screen utility is accessible by standard users.

root/users/user/apps/hptc-usb-mgr/authorized If set to 1, the USB Manager is accessible by standard users.

root/users/user/apps/hptc-user-rights/ authorized

If set to 1, the Customization Center is accessible by standard users.

If set to 1, the VNC Shadow utility is accessible by standard users.

root/users/user/apps/hptc-vncshadow/ authorized root/users/user/apps/hptc-xterm/authorized If set to 1, the X Terminal is accessible by standard users.

CAUTION:

Enabling X terminal access is a security risk and is not recommended in a production environment. The X terminal should only be enabled for use in debugging a protected, nonproduction environment.

152 Appendix E Registry keys

Table E-40 root > users (continued)

Registry key

root/users/user/apps/scim-setup/authorized root/users/user/hideDesktopPanel root/users/user/kioskMode root/users/user/launchConnectionManager root/users/user/rightclick root/users/user/ssoconnectiontype root/users/user/switchAdmin root/users/user/xhosts/<UUID>/xhost

Description

If set to 1, the SCIM Input Method Setup utility is accessible by standard users.

If set to 1, desktop panels such as the taskbar are not started or shown in the desktop.

This registry key is either used internally or reserved for future use. The value should not be changed.

If set to 1, the Connection Manager launches at system startup.

If set to 1, the right-click menu for the desktop is enabled.

This registry key is either used internally or reserved for future use. The value should not be changed.

If set to 1, switching to Administrator Mode is enabled.

Specifies the IP address or hostname of a system that will be allowed to remotely control the thin client when XHostCheck is enabled.

root > vncserver

Table E-41 root > vncserver

Registry key

root/vncserver/coreSettings/enableVncShadow root/vncserver/coreSettings/ userNotificationMessage root/vncserver/coreSettings/ vncNotifyShowTimeout

Description

If set to 1, the VNC shadowing server for the thin client is enabled.

Sets the notification message that is shown to the user when someone is attempting to connect to the thin client using VNC.

If set to 1, a timeout is applied to the notification dialog that is shown to the user when someone is attempting to connect to the thin client using VNC.

root/vncserver/coreSettings/vncNotifyTimeout Sets the timeout in seconds for the notification dialog that is shown to the user when someone is attempting to connect to the thin client using VNC.

root/vncserver/coreSettings/vncNotifyUser

If set to 1, a notification is shown to the user when someone is attempting to connect to the thin client using VNC.

root/vncserver/coreSettings/vncPassword Sets the password for VNC shadowing. The key vncUsePassword must also be enabled.

root/vncserver/coreSettings/vncReadOnly root/vncserver/coreSettings/ vncRefuseInDefault root/vncserver/coreSettings/ vncTakeEffectRightNow root/vncserver/coreSettings/vncUsePassword root/vncserver/coreSettings/vncUseSSL

If set to 1, VNC shadowing will operate in view-only mode.

If set to 1, VNC requests are refused automatically if the user does not interact with the notification dialog before the timeout.

If set to 1, VNC settings take effect immediately after being modified.

If set to 1, the password specified in vncPassword is required for VNC shadowing.

If set to 1, SSL is used for VNC connections.

root > vncserver 153

Table E-41 root > vncserver (continued)

Registry key

root/vncserver/gui/VNCShadowManager/name root/vncserver/gui/VNCShadowManager/status root/vncserver/gui/VNCShadowManager/title root/vncserver/gui/VNCShadowManager/widgets/ enableVncShadow root/vncserver/gui/VNCShadowManager/widgets/ userNotificationMessage root/vncserver/gui/VNCShadowManager/widgets/ vncNotifyShowTimeout root/vncserver/gui/VNCShadowManager/widgets/ vncNotifyTimeout root/vncserver/gui/VNCShadowManager/widgets/ vncNotifyUser root/vncserver/gui/VNCShadowManager/widgets/ vncPassword root/vncserver/gui/VNCShadowManager/widgets/ vncReadOnly root/vncserver/gui/VNCShadowManager/widgets/ vncRefuseInDefault root/vncserver/gui/VNCShadowManager/widgets/ vncTakeEffectRightNow

Description

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

This registry key is either used internally or reserved for future use. The value should not be changed.

Controls the state of the Enable VNC Shadow widget in the VNC

Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

Controls the state of the User Notification Message widget in the

VNC Shadow utility. If set to active, the widget is visible in the

UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the VNC Show Timeout for Notification widget in the VNC Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the numerical widget in the VNC Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

Controls the state of the VNC Notify User to Allow Refuse widget in the VNC Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Set Password widget in the VNC Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

Controls the state of the VNC Read Only widget in the VNC

Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

Controls the state of the Refuse connections in default widget in the VNC Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the Re-set VNC server right now widget in the VNC Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the

154 Appendix E Registry keys

Table E-41 root > vncserver (continued)

Registry key

root/vncserver/gui/VNCShadowManager/widgets/ vncUsePassword root/vncserver/gui/VNCShadowManager/widgets/ vncUseSSL

Description

widget is hidden. If set to read-only, the widget is visible in the read-only state.

Controls the state of the VNC Use Password widget in the VNC

Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

Controls the state of the VNC Use SSL widget in the VNC Shadow utility. If set to active, the widget is visible in the UI and the user can interact with it. If set to inactive, the widget is hidden. If set to read-only, the widget is visible in the readonly state.

root > vncserver 155

Index

A

AD/DDNS Manager 10

add-ons 1

audio redirection

RDP 43

VMware Horizon View 49

B

Background Manager 10

C

Certificate Manager 24

certificates

installing 24

VMware Horizon View 50

Citrix

HDX MediaStream 29

HP True Graphics 30

settings, connection-specific 34

settings, general 31 support matrix 31

client aggregation 12

client configuration 13

server configuration 14

Component Manager 18

Connection Manager controls 6

connections

common settings 26

hiding 10

types 1

Control Panel

AD/DDNS Manager 10

Background Manager 10

Client Aggregation 12

Component Manager 18

Customization Center 10

Date and Time 10

DHCP Option Manager 25

Display Preferences 14

Easy Update 10

Factory Reset 10

Keyboard Shortcuts 11

Language 10

Mouse 9

Network 15

overview 9

SCEP Manager 11

SCIM Input Method Setup 9

Screensaver 10

Security 10

Serial Manager 11

Snapshots 11

Snipping Tool 11

Sound 9

SSHD Manager 11

Task Manager 11

Text Editor 11

ThinState. See HP ThinState

Touch Screen 9

utilities, hiding 10

VNC Shadow 23

Wireless Statistics 11

X Terminal 11

custom connections 57

D

date and time settings 10

device redirection

RDP 42

VMware Horizon View 48

DHCP options 25

display preferences 14 display profiles 14

E

Easy Update 10

F

factory reset 10

finding more resources 1

G

getting started 3

H

HDX MediaStream 29

HP Device Manager. See HPDM Agent

HP Smart Client Services

installing 58 overview 58

Profile Editor. See Profile Editor

supported operating systems 58

HP TeemTalk. See TeemTalk

HP Velocity 18

HPDM Agent 10

I

image updates 1

imaging. See HP ThinState interface

navigating 5

K

keyboard shortcuts 11

kiosk mode 27

L

language settings 10

M

mass storage redirection

RDP 42

VMware Horizon View 48

MMR

VMware Horizon View 48

mouse settings 9

multimedia redirection

RDP 41

N

network settings

accessing 15

DNS 17

HP Velocity 18

IPSec 17

VPN 18

wired 16 wireless 16

P

parallel printer configuration 65

passwords, change 10

printer configuration 65

156 Index

printer redirection

RDP 43

VMware Horizon View 49

printers 14

Profile Editor

using 62

R

RDP

audio redirection 43

device redirection 42 mass storage redirection 42

multi-monitor sessions 41 multimedia redirection 41

printer redirection 43

RemoteFX 40

settings, connection-specific 36 settings, general 36

smart card redirection 44

USB redirection 42

registry keys 81

RemoteFX 40

RFX. See RemoteFX

S

SCEP Manager 11, 24

SCIM 9

screensaver settings 10 security settings 10

Serial Manager 11

serial printer configuration 65

smart card redirection

RDP 44

VMware Horizon View 49

Smart Zero login screen

customizing 73

snapshots 11

Snipping Tool 11

sound settings 9

SSH 55

SSHD Manager 11

system diagnostics 68

system information

viewing 7

system information screens

hiding 7

T

Task Manager 11

taskbar

using 5

TeemTalk 53

Telnet 57

text editor 11

thin clients updating. See updating thin clients

ThinPro profile

adding files 63

adding symbolic link 64

certificates 63

loading 62 modifying 62

registry settings 63

saving 65

ThinState. See HP ThinState

touch screen settings 9

troubleshooting 67 firmware corruption 67 network connectivity 67

using system diagnostics 68

U

updating thin clients

broadcast update 59

DHCP tagging update 60

DNS alias update 60 manual update 60

USB redirection

RDP 42

USB Manager 15

VMware Horizon View 48

V

VMware Horizon View

audio redirection 49

certificate security levels 51

certificates 50 changing protocols 50

device redirection 48 keyboard shortcuts 48 mass storage redirection 48

MMR 48 multi-monitor sessions 48

printer redirection 49

settings 45

smart card redirection 49

USB redirection 48

webcam redirection 50

VNC Shadowing 23

W

Web Browser

settings, connection-specific 52 settings, general 52

webcam redirection

VMware Horizon View 50

websites

Citrix support 1

HP support 1

Microsoft support 1

VMware support 1

wireless statistics 11

X

X Terminal 11

XDMCP 55

Index 157