HP Bc1500 - BladeSystem - Blade PC User manual

HP PC Session Allocation Manager
(SAM) Administrator User Guide
Document Part Number: 416323-001
March 2006
This guide is intended to help an administrator set up and successfully
manage the HP PC Session Allocation Manager (SAM). The target
audience is the person who administers a CCI infrastructure, not the users
of such an environment. This guide assumes the administrator is familiar
with the HP CCI environment, and thus focuses specifically on providing
information related to setup and management of the HP SAM.

© Copyright 2006 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
Microsoft, Windows, Windows Server, ActiveX, Active Directory, and Notepad are trademarks of Microsoft
Corporation in the U.S. and other countries.
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.
This document contains proprietary information that is protected by copyright. No part of this document may be
photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard
Company.
ÅWARNING: Text set off in this manner indicates that failure to follow directions could result in bodily
harm or loss of life.
ÄCAUTION: Text set off in this manner indicates that failure to follow directions could result in damage to
equipment or loss of information.
HP PC Session Allocation Manager (SAM) Administrator User Guide
First Edition (March 2006)
Document Part Number: 416323-001

HP SAM Administrator User Guide www.hp.com iii
Contents
1 Introduction
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
1.1.1 Key Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
1.1.2 How It Works (High Level Overview). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
1.2 HP SAM Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
1.2.1 HP SAM Web and SQL Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . 1–3
1.2.2 HP SAM Blade Service Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
1.2.3 Client Access Device Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
1.2.4 Other Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5
2 Installation
2.1 Install the HP SAM Web Server and SQL Software. . . . . . . . . . . . . . . . . . . . . . . . 2–1
2.1.1 Grant Users HP SAM Administrator Access . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
2.1.2 Configure HP SAM System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
2.2 Install and Validate the HP SAM Blade Service Software . . . . . . . . . . . . . . . . . . . 2–3
2.2.1 Install the HP SAM Blade Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
2.2.2 Create the HP SAM Registration Service Configuration File . . . . . . . . . . . . 2–4
2.2.3 Start/Restart the HP SAM Registration Service. . . . . . . . . . . . . . . . . . . . . . . 2–5
2.2.4 Test the HP SAM Blade Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5
2.3 Install and Validate the HP SAM Client Software . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
2.3.1 Internet Explorer-Based Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
2.3.2 Windows XP Embedded-Based Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
2.3.3 Windows CE 5.0-Based Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
2.4 Deploy the HP SAM Blade Service to All HP SAM Blade PCs. . . . . . . . . . . . . . . 2–9
2.5 Deploy HP SAM Client Software to All HP SAM Access Devices . . . . . . . . . . . 2–10
3 Administration
3.1 Log-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
3.2 General Navigation and User Interface Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
3.2.1 Search Using Wildcards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
3.2.2 Display More (or Fewer) Items Per Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
3.2.3 Move Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
3.2.4 Sort Result List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
3.2.5 Select More Than One Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
3.3 Managing the HP SAM Administrator Access List . . . . . . . . . . . . . . . . . . . . . . . . 3–2
3.3.1 Add Individual Users to the HP SAM Administrator Role . . . . . . . . . . . . . . 3–3
3.3.2 Adding Security Groups or Organization Units to the
HP SAM Administrator Role 3–3
3.3.3 Remove Users From the HP SAM Administrator Role . . . . . . . . . . . . . . . . . 3–4
3.4 HP SAM Administrator Console Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4

iv www.hp.com HP SAM Administrator User Guide
Contents
3.4.1 Home Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
3.4.2 Users and Roles Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
3.4.3 Resources Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
3.4.4 Policies Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
3.4.5 System Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9
3.4.6 Reports Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
3.4.7 Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
A Firewall Rules
B Frequently Asked Questions
C Blade Service Error Codes
Glossary

HP SAM Administrator User Guide www.hp.com 1-1
1
Introduction
1.1 Overview
The Consolidated Client Infrastructure (CCI) solution from HP centralizes desktop computing
and storage resources into easily managed, highly secure data centers, while providing end users
the convenience and familiarity of a traditional desktop environment. Additionally, companies
have long used server-based computing (SBC) to create virtual instances of desktop applications
on a server that multiple remote users can access. HP’s CCI offers a new alternative for
virtualizing the desktop.
The HP PC Session Allocation Manager (HP SAM) system becomes the control point in
managing a CCI deployment. Specifically, it manages the assignment of Microsoft Remote
Desktop connections from a user's access device (client) to Remote Desktop sessions (blade PC).
Whether the session is one that resides on a dedicated physical blade or one that resides together
with other sessions on a virtual hardware platform, the HP SAM system can make these desktop
sessions available to users as they are needed.
1.1.1 Key Features
■Allocation system to assign users to computing resources (blade PCs)
■Self-registration of computing resources (blade PCs)
■Simple management of users to desktop sessions provisioning
■Central management of client Remote Desktop settings with optional user override
■Follow-me roaming and persistence support for user sessions
■Usage and Capacity Planning reports
HP SAM is logically broken up into three areas:
■HP SAM client application running on a thin client or other access device
■HP SAM blade service running on a computing resource
■HP SAM server and SQL database

1-2 www.hp.com HP SAM Administrator User Guide
Introduction
1.1.2 How It Works (High Level Overview)
1. When a user on a client access device (desktop, notebook, thin client) requests a desktop
session, the HP SAM client sends a request to the HP SAM Web server.
a. HP SAM supports server failover, if configured to do so. If the HP SAM Web server
doesn't respond, the HP SAM client goes down the list to the next HP SAM Web server.
b. The HP SAM client sends the username and domain information to the HP SAM server.
2. The HP SAM Web server receives the username and domain from the HP SAM client. It
validates this information with the Microsoft Active Directory server. The account identified
by the username and domain must be valid and enabled in the Active Directory in order to
continue.
3. The HP SAM Web server returns the appropriate desktop session information to the HP
SAM client.
a. The HP SAM Web server checks its internal database to see what resources are available
and connects the user to an appropriate resource. Prior to assigning a resource to the user,
the SAM Web server determines whether or not the user still has a desktop session
running and, if so, reconnects the user to that same session (i.e., follow-me roaming).
b. The data returned to the HP SAM client would be a DNS name (or IP address, depending
on how it is configured on the HP SAM Web server.)
c. If no computing resource is available, the HP SAM client informs the user.
4. The HP SAM client connects to the appropriate desktop session.
5. The user is then prompted at the login screen for the password. The user name and domain is
prepopulated by the HP SAM client.
6. Once the user logs in, the HP SAM blade service on the computing resource reports back to
the HP SAM Web server.
HP SAM Web
and SQL
Database
HP SAM Client
Application
HP SAM Blade
Service

HP SAM Administrator User Guide www.hp.com 1-3
Introduction
7. Once the user disconnects or logs out, the HP SAM blade service updates the HP SAM Web
server with the new information.
1.2 HP SAM Hardware and Software Requirements
1.2.1 HP SAM Web and SQL Server Requirements
HP SAM can be installed on one or more failover HP SAM Web servers with one central HP
SAM SQL database. It can also be installed on one server hosting both the HP SAM Web server
and SQL database.
1.2.1.1 HP SAM Web Server Hardware Requirements
Minimum:
x86-compatible server, such as an HP Proliant server with:
■Processor: Pentium 4, 1.0 GHz
■Hard drive: 10 GB (requires more if hosting both Web server and SQL database)
■System memory: 1 GB or more
Recommended:
The recommended configuration depends on the scale of deployment:
■Number of active users
■Number of computing resources (blade PCs)
■Geographic location and/or network architecture
■Fault tolerance decision
1.2.1.2 HP SAM Web Server Software Requirements
Minimum:
One of the following operating system must be installed:
■Windows Server 2003, Standard Edition, with Service Pack 1 or higher
■Windows Server 2003, Enterprise Edition, with Service Pack 1 or higher
✎Additionally, SSL must be configured on the HP SAM Web server (which includes installing a
certificate) to encrypt your password when you log into the HP SAM administrator console.

1-4 www.hp.com HP SAM Administrator User Guide
Introduction
1.2.1.3 HP SAM SQL Database Server Hardware Requirements
If you already have an existing SQL database server, the HP SAM database can be installed on
the same server. However, a separate dedicated HP SAM SQL database server for the HP SAM is
highly recommended to support future scaling of environment.
Minimum:
x86-compatible server, such as an HP Proliant server with:
■Processor: Pentium 4, 1.0 GHz
■Hard drive: 10 GB (requires more if running both Web server and SQL)
■System memory: 1 GB or more
Recommended:
The recommended configuration depends on the scale of deployment:
■Number of active users
■Number of computing resources (blade PCs)
■Geographic location and/or network architecture
■Fault tolerance decision
1.2.1.4 HP SAM SQL Database Server Software Requirements
Minimum:
■Microsoft SQL Server 2000 with Service Pack 3a
✎SQL server mixed mode authentication must be enabled.
1.2.2 HP SAM Blade Service Requirements
Hardware Requirements
■HP Blade PC
Software Requirements
■Windows XP Professional with Service Pack 1 or higher
■Terminal service enabled (Remote Desktop)
1.2.3 Client Access Device Requirements
1.2.3.1 Thin Client
Hardware Requirements
The HP SAM client may already be preinstalled on the HP thin clients. In this case, you just need
to configure the HP SAM client to connect to the appropriate HP SAM Web server. If the HP
SAM client is not preinstalled, then you must download and install it. The unit must have

HP SAM Administrator User Guide www.hp.com 1-5
Introduction
sufficient flash space to download, expand, and install the HP SAM client. This typically means
the thin client must have unused flash memory equaling at least 2.5 times (approximately 3 MB)
the size of the HP SAM client.
Software Requirements
One of the following operating systems:
■Windows XP Embedded
■Windows CE 5.0
1.2.3.2 Desktop or Notebook PC
Hardware Requirements
■Desktop or notebook PC
Software Requirements
One of the following operating systems:
■Windows XP
■Windows 2000 with Service Pack 3 or higher
1.2.4 Other Requirements
There are other requirements you must fulfill before you start the installation.
■“Create a Service Account” on page 1-5
■“Obtain Administrative Rights” on page 1-5
■“Change the Firewall” on page 1-6
■“Active Directory” on page 1-6
1.2.4.1 Create a Service Account
The HP SAM Web server needs to run under a domain user account in which it can execute the
HP SAM services on the local server.
■The account needs to be created prior to installation of the HP SAM server application.
■This account name and password should be changed as infrequently as possible to minimize
interruptions to HP SAM.
■The account must also be in the local server administrator group.
1.2.4.2 Obtain Administrative Rights
In order to fully install HP SAM, you must have the following administrative rights:
■Administrative rights on all computing resources (blade PCs)
■SQL administrative level account and password—only needed during setup
■Administrative rights on the HP SAM Web server

1-6 www.hp.com HP SAM Administrator User Guide
Introduction
1.2.4.3 Change the Firewall
If the network environment uses a hardware and/or software firewall, then you need to make
appropriate changes to the firewall for HP SAM to work. Refer to Appendix A, “Firewall Rules,”
for more details.
1.2.4.4 Active Directory
While Active Directory is not part of HP SAM, it is required for HP SAM to perform user
account management.

HP SAM Administrator User Guide www.hp.com 2-1
2
Installation
For new setup, the recommended order of installation is:
■“Install the HP SAM Web Server and SQL Software” on page 2-1
■“Install and Validate the HP SAM Blade Service Software” on page 2-3
■“Install and Validate the HP SAM Client Software” on page 2-6
■“Deploy the HP SAM Blade Service to All HP SAM Blade PCs” on page 2-9
■“Deploy HP SAM Client Software to All HP SAM Access Devices” on page 2-10
2.1 Install the HP SAM Web Server and SQL Software
The installation package (HPSAM-xx.MSI where xx is the language code; EN for English and
JP for Japanese) installs the HP SAM server application and/or HP SAM database. You may
install either one or both Web and SQL databases. The language chosen is meant for the
installation wizard only. Once the application is installed, the Web application detects the
browser language, and the user interface is shown in that same language, if application supports
that language. If it does not, the user interface is in English.
✎HP SAM can have one or more HP SAM Web servers. Each HP SAM Web server is equivalent to
each other in feature set. You can set it up such that they load balance each other and act as
failover servers. Additionally, each server has the capability to run an automated task
independently, such as synchronizing the computing resources or deleting HP SAM system log
data from the HP SAM database. See Chapter 3, “Administration,” for more details on these
scheduled events.
Steps:
1. Log in to the server under an account with administrative rights.
2. Run the HPSAM-xx.MSI install file (replace xx with EN for English or JP for Japanese).
3. Click Next on the welcome screen.
4. For HP SAM Web server installation, the installer asks for a user account. The user account
is the owner of the HP SAM Web site and the HP SAM server service.
✎It is highly recommended that the account be a service account and not a personal account. This
account name and password should be changed as infrequently as possible to minimize
interruptions to HP SAM.
5. On this screen, you have the choice to install the HP SAM Web application only, the
HP SAM SQL database only, or both. The default is both. Click on the pull-down arrow next
to SAM Web Site or SAM Database to see the list of options. Click Next to continue.

2-2 www.hp.com HP SAM Administrator User Guide
Installation
6. Leave the default installation folder as is or click the Browse button to change it. Click
Next to continue.
7. Enter the SQL server name, the SQL authentication User Name, and Password. The SQL
user account needs to have the ability to create a database on the SQL server in order for the
application to be installed properly. If the HP SAM database doesn't exist, the installation
creates one. If it already exists, then the installation links the Web server to the HP SAM
database server.
8. Click Next on the Web Resources Configuration screen.
9. Select New Web Site for new Web installation, or select existing to install on an existing
Web server or to upgrade HP SAM.
10. Click on the IP Address drop-down list and map the Web site to the appropriate IP address.
11. Click Next to start the installation or Cancel to exit.
12. Click Finish when the installation is complete.
13. If your network environment uses a hardware and/or software firewall, then you need to
make the following changes to the firewall for the HP SAM Web server and/or SQL server:
❏Web server
◆Incoming:
–From clients (TCP/ANY) to Web server (TCP/80—HTTP)
–From blades (TCP/ANY) to Web server (TCP/80—HTTP)
–From admin_workstation (TCP/ANY) to Web server (TCP/443—HTTPS)
–From blades (TCP/47777) to Web server (TCP/47777—Custom)
◆Outgoing:
–From Web server (TCP/ANY) to SQL_Server (TCP/1433—MSSQL))
Default
selection:
Click here to
NOT install.

HP SAM Administrator User Guide www.hp.com 2-3
Installation
–From Web server (TCP/ANY) to blades (TCP/139—RPC)
–From Web server (UDP/47777) to blades (UDP/47777—Custom)
❏SQL Server (only if not running on the same machine as the Web server)
◆Incoming:
–From Web server (TCP/ANY) to SQL_Server (TCP/1433)
◆Outgoing:
–None
2.1.1 Grant Users HP SAM Administrator Access
The Domain Administrator and Local Server Administrator are automatically members of the
HP SAM Administrator's Group. It is highly recommended that you update the system by adding
security group or individual name(s) to the HP SAM Administrator access list, instead of using
the Administrator account to log in. This helps track who did what and when.
To add other users as HP SAM administrators, go to the HP SAM administrator console and add
these users to the Administrator role. See “Users and Roles Tab” on page 3-4 for detailed
instructions.
2.1.2 Configure HP SAM System Settings
Log in to the HP SAM administrator console, go to the System Settings tab, and make
appropriate changes. See “System Settings Tab” on page 3-9 for detailed instructions.
2.2 Install and Validate the HP SAM Blade Service
Software
Manually installing this software consists of these steps:
1. “Install the HP SAM Blade Service” on page 2-3
2. “Create the HP SAM Registration Service Configuration File” on page 2-4
3. “Start/Restart the HP SAM Registration Service” on page 2-5
4. “Test the HP SAM Blade Service” on page 2-5
2.2.1 Install the HP SAM Blade Service
■Log in to the blade PC under an account with local administrative rights and run the
bladesvc-xx.msi file (replace xx with EN for English or JP for Japanese) to install the
service.
■Stop the service by going to the Control Panel (classic view) > Administrative Tools >
Services, and look for HP SAM Registration Service. If it's running, stop it.
■Customize the service CFG file to match the HP SAM. Go to the C:\Program
Files\Hewlett-Packard\HP PC Session Allocation Manager Registration Service folder
and edit the hpevent.cfg-sample file. For details on how to customize this file, see “Create
the HP SAM Registration Service Configuration File” on page 2-4.
■Once the configuration file has been customized, rename (or Save As) the sample file to
hpevent.cfg.

2-4 www.hp.com HP SAM Administrator User Guide
Installation
■Start the HP SAM Registration Service by going to Control Panel > Administrative
Tools > Services, and start the service under the name HP SAM Registration Service.
■If you have a firewall installed on the blade PC, enable the ports below.
❏Incoming:
◆From Web server (UDP/47777) to blade (UDP/47777)
◆From Web server (TCP/ANY) to blade (TCP/139)
◆From clients (TCP/ANY) to blade (TCP/3389)
❏Outgoing:
◆From blade (TCP/ANY) to Web server (TCP/80—HTTP)
◆From blade (UDP/47777) to Web server (UDP/47777)
✎Another option for enabling the port is by enabling the software service itself. Follow the firewall
instructions to enable the HP SAM Registration Service software.
2.2.2 Create the HP SAM Registration Service Configuration File
The HP SAM Registration Service configuration file is an INI text file, named hpevent.cfg. The
HP SAM Registration Service tries to locate the configuration file in the order of locations listed
below. Once the file is located, the search stops and the contents are extracted.
■In the same directory in which the service resides (usually C:\Program
Files\Hewlett-Packard\HP PC Session Allocation Manager Registration Service\)
■In %SystemRoot% (usually c:\windows\)
■In %SystemDrive% (usually c:\)
Below is a sample template. Two sections that must be updated are [WebServerList] and
[MyRoles]
[hpEventCfg]
Gateway=WebServerList
Role=RolesList
;ServicePort=47777
[WebServerList]
server1.yourdomain
server2.yourdomain
[RolesList]
sample-role-1
sample-role-2
[WebServerList]
The [WebServerList] section lists one or more HP SAM Web servers. Each HP SAM Web server
(primary and failover) is listed, one per line. The service uses this list in the order provided. The
first HP SAM Web server in the list is the one tried first; if it fails, the service proceeds to try the
remaining HP SAM Web servers in order. If a successful connection is established, the remaining
HP SAM Web servers are not used.

HP SAM Administrator User Guide www.hp.com 2-5
Installation
To modify the server line, change just the server1.yourdomain string to the appropriate
server name (use Web server DNS name or static IP address). For example:
■HPSAMservername
■10.1.2.3
[RolesList]
The [RolesList] section lists one or more roles to which the blade PC can belong. A role is a
functional collection of computing resources (blade PCs). The first role in the list is the blade
PC’s primary role. All other roles, if any, are considered non-primary.
Blade PCs are allocated to the user in the priority order below:
■Available blade PC assigned to this role only
■Available blade PC assigned to multiple roles, with this role being primary
■Available blade PC assigned to multiple roles, with this role being non-primary
✎If at any time the configuration file is changed on the blade PC, the service must be restarted for
the changes to take effect.
2.2.3 Start/Restart the HP SAM Registration Service
The service can be started or stopped from the services applet (Control Panel (classic view) >
Administrative Tools > Services) or from the command line.
■Under the services applet, it appears as HP SAM Registration Service.
■Additionally, the service can be started or stopped from the command line, using the syntax:
C:> net start daesvc and C:> net stop daesvc.
The service can also be started or stopped by tools like HP Rapid Deployment Pack. See the HP
Rapid Deployment Pack documentation for instructions.
2.2.4 Test the HP SAM Blade Service
Log into the HP SAM administrator console, click on the Resources tab, and search for the blade
PC within the role it was assigned.
■If the blade PC was not found, check the firewall settings and make sure that the service was
started on that blade PC.
■If the computing resource is found, select the Resources tab and select Synchronize from
the Operation drop-down menu at the lower right of the screen.
✎If the blade PC is marked off-line after the synchronize operation, this typically means the HP
SAM Web server is unable to communicate to the blade PC. Check the firewall setting on the
blade PC to make sure it allows incoming on port 47777 or the HP SAM Registration Service.
You can find out if the firewall is blocking the necessary traffic by disabling the firewall
temporarily and then reenabling it again later.

2-6 www.hp.com HP SAM Administrator User Guide
Installation
2.3 Install and Validate the HP SAM Client Software
HP SAM has Windows XP Embedded-based and Windows CE 5.0-based clients plus an
Microsoft Internet Explorer-based version of the HP SAM client. The Windows XP
Embedded-based client also works on Windows 2000 and Windows XP operating systems.
The HP SAM client requires that Remote Desktop Connection be functional on the client access
device.
There are differences in features between the HP SAM Internet Explorer-based client and the
other HP SAM clients.
HP SAM Client Comparison
2.3.1 Internet Explorer-Based Client
A client access device can access HP SAM using Internet Explorer. To use the HP SAM Internet
Explorer-based client, enter the server name (http://HPSAMservername) in the Internet
Explorer address bar.
If the access device is accessing the HP SAM server for the first time, the client needs to install
two ActiveX controls (HP SAM Time Zone Download Control and Remote Desktop Client
Control.) The installed location for these controls are in %SystemRoot%\Downloaded Program
Files\ folder.
There are other HP SAM Internet Explorer-based client configuration settings that you can
control from the HP SAM server. Refer to the System Settings section below for more
information.
Features Internet
Explorer-Based
Windows XP
Embedded-Based
Windows CE
5.0-Based
Operating System
Support
Windows 2000
Windows XP
Windows XP Embedded
Windows 2000
Windows XP
Windows XP Embedded
Windows CE 5.0
Automatic failover
support
√√
Requires Internet
Explorer browser
√
Requires ActiveX
controls to be
downloaded in
order to run
√
Languages English, Japanese English, Japanese English

HP SAM Administrator User Guide www.hp.com 2-7
Installation
✎It is recommended that the HP SAM Web server be added to the Trusted Sites list. This can be
done from Tools > Internet Options in the Security tab on the client access device.
If any firewall is installed, you need to make appropriate changes to allow the HP SAM server
client through. For example, if HP Sygate Security Agent is installed, add a rule to allow port
3389 for application IEXPLORE.EXE.
The HP SAM ActiveX controls are stored as source for distribution on the HP SAM Web server
during the Web server installation process.
If the ActiveX controls are replaced on the HP SAM Web server during an upgrade, the HP SAM
client is automatically upgraded to the newer version the next time the client access device
connects to the HP SAM Web server.
For the HP thin client running Windows XP Embedded, the installation of the ActiveX
components may be repeated every time the access device is rebooted, if it is not saved as part of
the thin client image.
2.3.2 Windows XP Embedded-Based Client
To install the HP SAM client on a Windows XP Embedded-based thin client or on a
desktop/notebook PC:
1. Log in to the access device under an account with local administrative rights and run the
scw32-xx.msi file (replace xx with EN for English or JP for Japanese) to install the Windows
XP-based client.
2. Follow the installation wizard.
3. After the software is installed, verify the program is placed on the start menu (Start > All
Programs > Hewlett-Packard > HP PC Session Allocation Client).
Customization Steps
(Recommended)
1. Start up the HP SAM client.
2. Enter in the HP SAM Web server name.
3. Click the Options button.
4. Change appropriate connection settings.
5. Click Save Settings button.
6. Select Desktop in the Save in drop-down box.
7. Click the Save button.
There are additional options to configure the settings. These can be set by manually editing the
.HP SAM file. Here is the list of supported keys and values within the [HPRDC] section.
■Gateways—string value. Points to the section that lists HP SAM Servers.
■DefaultPolicy—string value. This is the policy that should be selected by default.
■DefaultDomain—string value. This is a default value to be loaded in the Domain edit box
on the client UI. If this value is not specified, the program attempts to determine the domain
from the user's login information, which may or may not be accurate.

2-8 www.hp.com HP SAM Administrator User Guide
Installation
■Policies—string value. Points to the section that lists policies that are loaded in the client's
Connection Type drop-down box on the first tab of the Options section. This allows the
administrator to pre-define a number of policies associated with various connection types.
■Autodial—integer value, 0 or 1. If this value is set to 1, the program automatically tries to
connect on startup, without waiting for the user to enter login information. Default value is 0
(off).
■DefaultUsername—string value. If this value is not specified, the program attempts to
determine the user name from the user's login information, which may or may not be
accurate.
■DefaultInsecurePassword—string value. This field can be used to pre-populate the
password box. This field was intended for automated load testing in an environment where
security is not of importance.
ÄCAUTION: The DefaultInsecurePassword field is in plain text format and should not be used in a
production environment.
■Failover—integer value. When set to 1, this enables the failover capability of the client. If
there are multiple Web servers defined, the client fails over to the next available computing
resource when a connection to one fails. Turning this feature on limits the user’s ability to
type in a new HP SAM server; the user still has the ability to choose between Web servers
defined in the configuration file. Default value is 0 (off).
■EnablePassword—integer value, 0 or 1. When set to 1, this shows the Password box on the
client user interface. When set to 0, the password box is not available. Default is 0 (off).
■ConnectionPort—short integer value, in the range 1 to 65535. This is the port on which the
remote desktop service (such as Remote Desktop) listens on. For Remote Desktop, if not
specified, this value defaults to 3389. A value of 0 is ignored.
■UILanguage—Two-character language identifier. Currently the only identifier supported is
JP for Japanese. If the identifier is not supported or the property is not present in the
configuration file, the application defaults to US English. The language support DLL must
be present to support a particular language.
✎The UILanguage specified must either be the same language as the HP SAM client application
that you have installed or English. If you installed the English HP SAM client application, do not
change the value to any other language. In order to minimize disk space, the English HP SAM
client application does not contain any other HP SAM client language DLL.
Various methods are available to deploy the client application to multiple client access devices.
Following are two examples:
■Use software deployment tools like HP Rapid Deployment Pack.
a. Install the client application (scw32-xx.msi) on client units.
b. Update the client config file to work with the HP SAM (see customization steps above).
■Post the scw32-xx.msi and hprdc.sam file on a Web site or fileshare. Then instruct the
user(s) to
a. Download and install the client software (scw32-xx.msi).
b. Place the config file (hprdc.sam) on the desktop.

HP SAM Administrator User Guide www.hp.com 2-9
Installation
✎If there is any firewall installed, make appropriate changes to allow the HP SAM client through.
Do this at the application level instead of the port.
2.3.3 Windows CE 5.0-Based Client
To install the client on a Windows CE 5.0-based thin client:
1. Log in to the thin client under an account with local administrative rights and run the
scwce-en.cab file.
2. Follow the installation wizard to install.
3. After installation, click Start > Programs > HP PC Session Allocation Client to run
the client.
Customization Steps
(Recommended)
1. Run the client.
2. Enter the HP SAM server name.
3. Click the Options button.
4. Change connection settings, if needed.
5. Click the Save Settings button.
6. Select Desktop in the Save in drop-down box.
7. Click the Save button.
✎Additional settings can be set by manually editing the .SAM file. Refer to the Windows XP
Embedded section above for these options.
2.4 Deploy the HP SAM Blade Service to All HP SAM
Blade PCs
For high volume deployment, it is highly recommended that a software tool such as HP Rapid
Deployment Pack be used.
1. Install the service on all blade PCs.
2. Create the HP SAM blade service configuration file (hpevent.cfg) on a single blade and save
this file as a template to be used later.
3. Start or restart service on a single blade PC and verify that the unit self-registered into the
HP SAM Web server.
4. Deploy the HP SAM blade service configuration file (hpevent.cfg) to all appropriate blade
PCs and start the service on those units.

2-10 www.hp.com HP SAM Administrator User Guide
Installation
2.5 Deploy HP SAM Client Software to All HP SAM
Access Devices
To deploy the HP SAM Internet Explorer-based client, instruct your users to go to the HP SAM
server Web site(s) that you have set up.
Various methods can be used to deploy the Windows XP Embedded-based or Windows CE
5.0-based HP SAM client to the access devices. Following are two examples.
■Use software deployment tools such as HP Rapid Deployment Pack.
1. Install the HP SAM client on the access devices.
2. Update the client hprdc.sam file to connect to the HP SAM server.
■Post the HP SAM Windows XP Embedded-based client installation file and/or the HP SAM
Windows CE 5.0-based client installation file on a Web site or fileshare. If you have created
a hprdc.sam file for your environment, you should post this file also. Then instruct the
user(s) to
1. Download and install the client software (scw32-xx.msi or scwce-en.cab).
2. Place the config file (hprdc.sam) on the desktop.