HP ThinPro 5.2 - Administrator Guide

Selecting the platform for a ThinPro prole
Use the Platform screen in the Prole 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 conguration
●
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\auto-
update\Packages
To congure a ThinPro prole’s platform settings:
1. On the Platform screen in the Prole Editor, select an OS Build ID that corresponds to the desired image
version.
IMPORTANT: Be sure to create a dierent ThinPro prole 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 conguration to either standard (ThinPro) or zero (Smart Zero).
NOTE: For older image versions, this setting is greyed out and set to zero automatically.
Conguring a default connection for a ThinPro prole
To congure a default connection for a ThinPro prole:
1. On the Connection screen in the Prole Editor, choose the desired connection type from the Type drop-
down list.
NOTE: The available connection types dier depending on whether you chose the ThinPro or Smart
Zero conguration on the Platform screen.
2. In the Server eld, type the name or IP address of the server.
Modifying the registry settings of a ThinPro prole
To change default registry settings for a ThinPro prole:
1. On the Registry screen in the Prole 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 eld.
Adding les to a ThinPro prole
Use the Files screen in the Prole Editor to add conguration les that will be installed on the thin client
automatically when the ThinPro prole is installed. This is typically used for the following reasons:
●
To add certicates
●
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 prole 63