Produttore : HP File Size : 373.09 kb File Nome : Lingua di insegnamento:

Vai a scaricare

PSG to HP Software Delivery Guide
September 2, 2009

workstations, and thin clients. HP Client Automation is available in three editions: Starter,
Standard, and Enterprise editions.

Most of the HP Client Automation software resides on a server. The RALF component comes
preinstalled on HP Thin Clients, and it’s only purpose is to register with the HP Client
Automation console on the server so that a full management agent can then be remotely pushed
out to the client. Once the full agent is pushed out, the client can be fully managed remotely by
the HP Client Automation management console. The version of RALF that comes with the HP
thin clients is compatible with all three editions of HP Client Automation. RALF does not have
a GUI.

Once the HP Thin Client is connected to a network, powered on, and the OS finished loading,
RALF will automatically communicate out from the thin client using port 3465 and attempt to
find a HP Client Automation server that has a name of “hpcaserver”. This can be the actual
servername, or it can be a DNS alias that has been created. At boot-up, RALF will attempt to
contact the server once per hour until it locates the server, or until 24 hours has elapsed. When
RALF locates the server, it will register itself, and will stop any further attempts to contact the
server. After 24 hours, if RALF has not located the HPCA server, it will stop trying, until the
thin-client is re-booted. Then, the cycle will repeat.

1. Does the thin client boot up to the desktop properly? If not, PSG 1LS needs to resolve this by
whatever means usual.
2. Is the thin client connected to a live network jack? If not, instruct the customer to plug the network
cable into a live network jack.
3. Was the thin client initially powered up and connected to the network before the HP Client
Automation server was created? If so, reboot the thin client. RALF will only attempt to find the Client
Automation server once an hour for 24 hours before giving up until the thin client is rebooted. This
limits the amount of network traffic for customers that will not use Client Automation.
4. Does the thin client have a valid IP address? If not, investigate why up to the normal limits of what
PSG 1LS would do for this issue.
5. Can the thin client ping any other system on the network? If not, investigate why up to the normal
limits of what PSG 1LS would do for this issue.
6. Can thin client ping the name or IP of the HP Client Automation server? If not, investigate why up
to the normal limits of what PSG 1LS would do for this issue.
a. RALF uses a default name of HPCAServer for the Client Automation server. If the customer
did not use this name when creating the Client Automation server, they must create a DNS
alias name of HPCAServer that points to the HPCA server name they choose. Additional
help on how to create a DNS alias should be routed to HP Software support.
7. Has the customer uninstalled RALF? If so, instruct the customer to reimage their system. The latest
images on www.hp.com under the Drivers and Support section for their thin client model.
8. Has the customer created their own custom image? If so, proceed with whatever the normal PSG
TC support policy is on this. If we still support this, insure the rest of these steps are checked.
a. PSG does not provide RALF as a standalone application. If the customer is using their own
custom image and needs RALF, instruct them to get RALF from the full HP Client Automation
installation they must already have in order to use RALF, and install RALF per the HP Client
Automation instructions. Client Automation can be downloaded from
2

---

...

Questo manuale è adatto anche per i modelli :
Computer - HP Compaq t5530 Thin Client (373.09 kb)
Computer - HP Compaq t5720 Thin Client (373.09 kb)
Computer - HP Compaq t5725 Thin Client (373.09 kb)

Scarica la tua

Per scaricare, digitare 2 cifre :