It depends on your model. Like a Wyse terminal, you can deploy an .ini via FTP, and push by DHCP where to get it.
Network Mode (Stateless) FTP/DHCP server and profile setup
This
section provides basic instruction for how to configure a network
environment so HP Compaq t5135 Thin Clients can access the HP-format
global profile “global.ini” file and the user profile .ini files on an
FTP server, using DHCP scope options. By default, upon booting up and
successfully logging in at the group logon screen with a specific user
name (i.e., john), any HP Compaq t5135 Thin Client connected to the
network environment as configurated in the following sections will
automatically be configured with the settings captured in the
HP-format “global.ini” file and the settings in the user profile
“john.ini” file.
There is the scope option you need :
Configure a DHCP server: Assign four scope-based options and set their
values to match the configuration of the FTP server configured in Step
1. For example:
● FTP Server IP Address: 161 = 10.0.0.2
● FTP Server Path: 162 = /hp
● FTP Server User Name: 184 = anonymous
● FTP Server Password: 185 = anonymous
To get the format, you need to export it from one thinclient.
To create a global.ini file
Start the t5135 and make the desired
changes through the ThinConnect Settings button.
Once all of the
desired settings are selected, capture the settings file using the
ThinState 32 HP Compaq t5125/t5135 Thin Clients, build S1ST0031
Capture tool from within the t5135 image (see Management on page 22
for more information about ThinState).
ThinState will capture a file
named profile.ini and save that file onto a USB storage device. Access
the USB storage device and change the name of the config.ini file to
global.ini. After renaming the file, place in the FTPROOT/HP folder on
your Microsoft Windows Server or Linux FTP server. The global.ini file
contains the settings that will be propagated onto all thin clients
connected to the FTP server.
Every setting on the t5135 can be
configured with this file, including screen size, application to
connect to (such as RDP/ICA connections), security, keyboard settings,
Altiris server information, WOL and VNC settings, etc.
User
profile.ini files are created exactly the same way as global.ini
files. After capturing the config.ini using ThinState Capture, rename
the config.ini to the specific name for each specific user.
User
profile.ini files are used to override specific global.ini settings or
add different settings for an individual user. See the following for
instructions for where to place the global.ini and user profile.ini
files.
From http://h20565.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c00957439