Microsoft and Windows 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.
Part of the software embedded in this
product is gSOAP software.
Portions created by gSOAP are Copyright
(C) 2001-2004 Robert A. van Engelen,
Genivia inc. All Rights Reserved.
Second Edition (August 2007)
First Edition (June 2007)
Document Part Number: 453252–003
THE SOFTWARE IN THIS PRODUCT WAS
IN PART PROVIDED BY GENIVIA INC AND
ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE
AUTHOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Copyright (c) 1998-2007 The OpenSSL
Project. All rights reserved.
Copyright (C) 1995-1998 Eric Young
(eay@cryptsoft.com). All rights reserved.
Administrator's Guide
Business PCs
Third Edition (December 2007)
About This Book
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.
NOTE:Text set off in this manner provides important supplemental information.
iii
iv About This Book
Table of contents
1 Introduction
What's New in This Release ................................................................................................................ 2
Window Position Enhancements (Easier Moves) ................................................................ 4
Global and Local Client Configuration Files ......................................................................... 4
Ease of Multi-Display Deployment and Web Administrator Setup ....................................... 5
User Resource Management Controls ................................................................................ 6
Enhanced “Add New User” Searches .................................................................................. 6
Key Features ........................................................................................................................................ 6
Personal Workstation Clients ............................................................................................. 24
Create a Service Account .................................................................................................. 25
Obtain Administrative Rights ............................................................................................. 25
v
3 Installation
Install the HP SAM Web Server and SQL Software ........................................................................... 26
Install and Validate the HP SAM Registration Service Software ........................................................ 28
Install and Validate the HP SAM Client Software ............................................................................... 31
Deploy the HP SAM Registration Service to All HP SAM Computing Resources .............................. 41
Deploy HP SAM Client Software to All HP SAM Access Devices ...................................................... 41
4 Administration
Log In ................................................................................................................................................. 43
General Navigation and User Interface Design .................................................................................. 43
Managing the HP SAM Administrator Access List ............................................................................. 44
HP SAM Administrator Console Tabs ................................................................................................ 46
Setting Up Smart Card Login on the Access Device .......................................................................... 67
Change the Firewall ........................................................................................................... 25
Active Directory .................................................................................................................. 25
Grant Users HP SAM Administrator Access ...................................................................... 28
Configure HP SAM System Settings ................................................................................. 28
Install the HP SAM Registration Service ........................................................................... 28
Create the HP SAM Registration Service Configuration File ............................................. 29
Start/Restart the HP SAM Registration Service ................................................................. 30
Test the HP SAM Registration Service .............................................................................. 31
Internet Explorer-Based Client ........................................................................................... 32
Windows XPe-Based Client ............................................................................................... 32
Windows CE 5.0-Based Client ........................................................................................... 33
HP Blade Workstation Client Series .................................................................................. 34
SQL Server ......................................................................................................................................... 70
vi
Appendix B Frequently Asked Questions
Appendix C Registration Service Error Codes
Appendix D Glossary
Index ................................................................................................................................................................... 79
vii
viii
1Introduction
HP Remote Client Solutions are designed to support a variety of users’ needs, from the most basic
computing tasks to more demanding professional and technical applications, while giving IT greater
control over technology resources, simplifying desktop management, increasing agility and, in many
cases, reducing total cost of ownership.
Underlying HP Remote Client Solutions is a unified infrastructure that enables client deployment,
session allocation, balancing of computing resources, and supports the business needs of a diverse set
of users though the use of a common set of tools.
The HP Session Allocation Manager (HP SAM) system is the control point in managing an HP Remote
Client Solutions deployment. HP SAM manages the assignment of connections from an end-user's client
access device to desktop sessions running on computing resources in a centralized location (typically,
a data center). HP SAM makes these desktop sessions available to users as they are needed.
For more information about HP Remote Client Solutions, visit
http://www.hp.com/go/rcs.
1
What's New in This Release
Multi-Level Administrator
●
Multi-Session – role assignment
●
Single Location Client Configuration
●
Blade Service Windows XP 64-bit
●
Blade Service PWS Workstation
●
USB session simplification
●
Reconnect All Button
●
Legal Banner
●
Window Position Enhancements (Easier Moves)
●
Global and Local Client Configuration Files
●
Ease of Multi-Display Deployment and Web Administrator Setup
●
User Resource Management Controls
●
Enhanced “Add New User” Searches
●
Multi-Level Administrator
The HP SAM administrator or domain administrator has full rights to all Asset Groups in the HP SAM
server. Asset Groups allow focused management of business group assets:
Clients
●
Resources
●
Users, OUs, SGs
●
Roles
●
Monitor Layout IDs
●
Policies
●
Logs
●
Reports
●
The HP SAM administrator or domain administrator also creates the administrative groups.
Administrator groups can be assigned to control one or more asset group.
●
Users within each administrator group can control all assets in the Asset Groups identified.
●
Administrators will only be able to see assets associated with Asset Groups they control.
●
NOTE:The HP SAM administrator or domain administrator has full rights to all Asset Groups in the
HP SAM server.
2Chapter 1 Introduction
Multi-Session – Role Assignment
This feature allows administrators to assign roles in Monitor Layout IDs as they do with static
assignments. Administrators can specify a position on the client device and a resolution for the blade
chosen within the role.
Single Location Client Configuration
This feature allows Administrators to set up sessions on an access device (with resolutions and offsets),
and then save that to the server as a Monitor Layout ID. The Administrator can determine the following:
Static assignments and roles for monitor layout ID
●
Position and resolution of each session
●
Disconnected sessions are not saved back to the database. A disconnected session will be removed if
it is currently in the database for the specified monitor layout ID.
The HP Sam server administrator may make the following changes:
Set up the HP SAM client device to hide the Save button on the HP SAM Connection Bar
●
Change the monitor layout ID of the client device
●
Set up or change the default monitor layout ID based on a monitor layout ID stored in the HP SAM
●
client configuration file
Blade Service Windows XP 64-bit
This feature provides support for HP SAM blade service on Windows XP 64-bit on the HP ProLiant
xw460c Blade Workstation (Intel Pentium Xeon) platform.
Blade Service PWS Workstation
This feature allows HP SAM blade service to be supported on the HP xw8400 Workstation and the HP
xw9400 Workstation. The following operating systems are covered:
Windows XP Professional 32
●
Windows XP Professional 64
●
USB Session Simplification
This feature allows the user to remap USB devices to a selected session from the HP SAM Connection
Bar.
USB enablement is based on policy. The administrator may specify which static resources or roles can
use USB and which cannot.
NOTE:This feature requires RGS 5.1.3 or later.
Reconnect All Button
This is a new feature on the HP SAM Connection Bar. This enhancement allows the user to click
Reconnect All and reconnect to all disconnected sessions. The user must enter a password for each
credential initially used to make the connections.
What's New in This Release3
Legal Banner
This allows a legal disclaimer to be displayed before logon. Name the file disclaimer.<file
type> and copy the file into the appropriate directory (create the folder, if necessary). The following are
the default paths:
Access Device Client: Installing the legal banner on an access device causes the banner to be
●
displayed on that access device only. Name the file disclaimer.<file type> and copy the
file into the following directory (create the folder, if necessary) on the access device:
◦
◦
Web Client: Installing the legal banner on a SAM Web server causes the banner to be displayed
●
to all users connecting via Web Client. Name the file disclaimer.<file type> and copy the
file into the following directory (create the folder, if necessary) on the HP SAM server:
◦
NOTE:Replace $LANG with the appropriate folder name for the language desired: EN for English, JP
for Japanese, FR for French, DE for German, KO for Korean, or CN for Simplified Chinese.
Web Client: C:\program files\hewlett-packard\SAM\webclient\images\$LANG
\disclaimer.<file type>
JPG
●
GIF
●
BMP
●
NOTE:This feature is enabled by default if the disclaimer file is found in the correct location.
Window Position Enhancements (Easier Moves)
This feature provides additional enhancements for managing a multi-session environment by using the
HP SAM Connection Bar to identify and adjust window positions.
Global and Local Client Configuration Files
This feature allows administrators to 'lock down' certain options, while allowing other options to be
altered by users.
There are three levels of files:
Global: hprdc_admin.sam
●
Local: hprdc_accessdevice.sam
●
Personal: hprdc.sam
●
4Chapter 1 Introduction
The order of precedence is:
Personal file is read first.
●
XPe: Anywhere on file system (double-click hprdc.sam)
◦
XPe search locations used in this order—when one is found, it stops looking:
◦
%AppData%; Default for XP: C:\Document and Settings\<username>\Application Data
\hprdc.sam. Default for Vista: C:\users\<username>\AppData\Roaming\hprdc.sam
Parameters in the local file override the personal parameters
●
XP file location is the install directory. Default: C:\Program Files\Hewlett-Packard\HP Session
◦
Allocation Client\hprdc_accessdevice.sam
Workstation Client OS file location: /opt/hpsam/hprdc_accessdevice.sam (/root/writable/opt/
◦
hpsam/hprdc_accessdevice.sam)
Parameters in the global file override the personal and local parameters
●
XP file location is the install directory. Default: C:\Program Files\Hewlett-Packard\HP Session
◦
Allocation Client\hprdc_admin.sam
Workstation Client OS file location: /opt/hpsam/hprdc_admin.sam (/root/writable/opt/hpsam/
◦
hprdc_admin.sam)
Ease of Multi-Display Deployment and Web Administrator Setup
The administrator now has two new ways to assign resources:
Select a single user as a template and use this template to apply dedicated resources and user
●
attributes to multiple users at once.
Select a role and have dedicated resources automatically assigned to multiple users from the role.
●
This feature can be accessed on the Manage Users page when performing the Assign Resources
operation or on the Add New Users page after clicking Save to add users to SAM.
Attributes assigned by template include the following:
Dedicated resources (including backup resources or roles)
●
Roles
●
Policies
●
What's New in This Release5
Monitor layout IDs
●
Asset Groups
●
NOTE:The Template User must have a dedicated resource in a role and there must be enough
available resources in that role to satisfy the users during automatic assignment of dedicated resources.
NOTE:This feature allows administrators to clone from a single user to many users, but not to clone
to Organizational Units (OUs) or Security Groups (SGs).
User Resource Management Controls
HP SAM now allows a user to perform certain functions from the HP SAM Connection Bar. The
administrator controls end user access to the features.
Logoff of the resource
●
Restart the resource
●
Cycle power on the resource
●
The following requirements must be met for Logoff and Restart:
The server must be set up to accept SSL connections to allow usernames and passwords to be
●
transmitted to the server.
The HP SAM service account must have local administrator privileges on the resource to be granted
●
permissions to reboot or logoff a user from the blade.
The following requirements must be met for Power Cycle:
Version 4.15 or later IA software must be used on the enclosure(s).
●
An HP BladeSystem bc2000 Blade PC or an HP BladeSystem bc2500 Blade PC is required.
●
The IA password must be saved in HP SAM on the Manage Data Centers page.
●
These functions can apply to either individual sessions or to all sessions using the Disconnect or
Disconnect All button, respectively.
Enhanced “Add New User” Searches
The feature is an enhanced way of searching for users, SGs, and OUs in AD. It now shows results as
you type, and it allows expansion of SGs and OUs to see the users in them.
Key Features
Allocation system to assign users to computing resources (such as blade PCs or workstation
●
blades)
Self-registration of computing resources
●
Central management of access device remote connection settings
●
Follow-me roaming and persistence support to enable reconnection to an open session from a
●
different access device
Customizable administration levels
●
6Chapter 1 Introduction
Usage and Capacity Planning reports
●
Dedicated user/display to computing resource mapping
●
HP SAM is logically broken up into three areas:
HP SAM client application running on a thin client or other access device
●
HP SAM registration service running on a computing resource
●
HP SAM server and SQL database
●
Overview
HP SAM enables automatic provisioning of remote computing resources to users.
Figure 1-1 HP SAM Configuration
HP SAM can be configured to enable a user to connect to the desktop session of a particular remote
computing resource (identified by its hostname or IP address)—this is known as a static connection. In
Figure 1-1 HP SAM Configuration on page 7, HP SAM has been configured to statically connect user
Tom to blade PC 1 with an IP address of 15.2.76.100. Regardless of which access device Tom uses,
he is automatically connected to blade PC 1 at address 15.2.76.100.
HP SAM can also be configured to enable a user to connect to any of a pool of computing resources—
this is known as a dynamic connection. HP SAM allows the administrator to define one or more roles
for each computing resource. A computing resource with a role of “abcde”, for example, might be
configured with applications to conduct stock transactions or accounting functions. In
SAM Configuration on page 7, HP SAM has been configured to allow user Mai to dynamically connect
to one of the three blade workstations supporting the role of “abcde.”
HP SAM uses HP Remote Graphics Software (RGS) or Microsoft® Remote Desktop Protocol (RDP) to
connect between access devices and computing resources.
RGS has features which make it particularly suitable for remote computing. RGS provides extremely
fast capture, compression, and transmission of the desktop image (the actual frame buffer pixels) using
standard TCP/IP networking. For more information on RGS, visit
http://www.hp.com/go/rgs.
Figure 1-1 HP
Overview7
How HP SAM Works
1.When a user on an access device (desktop, notebook, thin client) requests a desktop session, the
HP SAM client sends a request to the HP SAM Web server.
a.If configured, HP SAM supports server failover. If the HP SAM Web server does not respond,
the HP SAM client goes down the list to the next HP SAM Web server.
b.The HP SAM client sends the user name and domain information to the HP SAM server.
2.The HP SAM Web server receives the user name and domain from the HP SAM client. The Web
server validates this information with the Microsoft Active Directory server. The account must be
valid and enabled in Active Directory 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 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). If the
user has no existing desktop session, the HP SAM Web server checks its internal database
to see what resources are available and connects the user to an appropriate resource.
b.The data returned to the HP SAM client is an IP address (or Host name, 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.
NOTE:HP SAM uses HP Remote Graphics Software (RGS) or Microsoft® Remote Desktop
Protocol (RDP) to connect between access devices and computing resources.
RGS has features which make it particularly suitable for remote computing. RGS provides
extremely fast capture, compression, and transmission of the desktop image (the actual frame
buffer pixels) using standard TCP/IP networking. For more information on RGS, visit
http://www.hp.com/go/rgs.
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. This step is omitted if the user has already entered the
password on the HP SAM client and either RDP is used or RGS in Single Sign-on mode is enabled.
NOTE:With RDP or RGS 5.1 or later, HP SAM allows users with expired passwords to log on.
They are then required to update their passwords immediately.
6.Once the user logs in, the HP SAM registration service on the computing resource reports back to
the HP SAM Web server.
7.Once the user disconnects or logs out, the HP SAM registration service updates the HP SAM Web
server with the new information.
8Chapter 1 Introduction
Overview9
HP SAM Software Components
The following are the primary components of HP SAM.
HP SAM Client—The HP SAM Client runs on the access device and displays the graphical
●
interface employed by the user to request a connection from a client computer to a computing
resource. When the user requests a connection, the HP SAM client communicates this request to
the HP SAM Web Server for execution.
HP SAM Web Server—The HP SAM Web Server (web server) runs on Windows Server 2003 and
●
manages the operation of HP SAM. A request is made to the web server when a user on an access
device requests a connection to a computing resource. The web server validates the request, and
then communicates back to the access device to orchestrate the connection. In addition, the web
server supports a browser interface to allow the HP SAM administrator to set up, configure, and
administer HP SAM. The web server also creates and accesses a database in Microsoft SQL
Server.
HP SAM Registration Service—The HP SAM Registration Service (registration service) runs on
●
the computing resource and communicates the status of the computing resource and its
connections to the HP SAM Web Server.
NOTE:Refer to the documentation that shipped with your computing resource and your access device
to determine which of the above components are factory-installed on your hardware and which
components you’ll need to install. For example, the HP SAM Client and the RGS Receiver are both
factory-installed on the HP dc72 Blade Workstation Client. Other RGS software is optional and must be
acquired separately. For more information on RGS, visit
http://www.hp.com/go/rgs.
Remote Graphics Software (RGS)
RGS is a communication protocol similar to Microsoft Remote Desktop Protocol (RDP). HP SAM allows
you to use either RGS or RDP.
RGS has a couple of advantages over RDP:
RGS has advanced graphics capabilities that provide a better video viewing experience that allows
●
users to connect to the desktop of a remote computer over a standard computer network.
RGS supports multiple monitors configured with an offset layout.
●
Thin clients are set to use RGS when possible. If both RGS and RDP are installed on the access device,
RGS is the default. If RGS is installed on both access device and computing resource, RGS is used. If
one or both do not have RGS, then RDP is used.
NOTE:Smart Card log-in using HP SAM client does not work with RGS.
HP RGS is optional and must be acquired separately. For information on HP RGS, visit
http://www.hp.com/go/rgs. To view the HP Remote Graphics Software User Guide, visit
http://www.hp.com/support/rgs_manuals and scroll down to the User guide heading.
10Chapter 1 Introduction
Common Tasks
Setting up HP SAM
1.Install HP SAM. See Installation on page 26.
2.Add users.
a.Add new users. See
b.Create administrative groups, assign users, and customize permissions. See
Administrative Permissions on page 47.
3.Create a policy. See
4.Create a role. See
5.Assign computing resources or roles to the users. See
Manage Resource Roles on page 46.
Add New Users on page 52.
Create or Update a Policy on page 59.
Manage Users on page 48.
Manage
Common Tasks11
Setting up a User with a Dynamic Resource
HP SAM enables computing resources to be dynamically shared among users.
Figure 1-2 Dynamic Connection Example
In Figure 1-2 Dynamic Connection Example on page 12, we need to grant user Mai access to computing
resources. A pool of three blade workstations has been assembled, each configured to support the role
of “abcde”.
We assign Mai a role of “abcde.” See
▲
This means Mai is now authorized to access any computing resource which supports a role of “abcde.”
Therefore, when Mai requests connection to an “abcde” computing resource, HP SAM automatically
connects her access device to one of the three blade workstations (presuming one is available)
supporting that role.
Manage Users on page 48.
12Chapter 1 Introduction
Setting up a User with Static (Dedicated) Resources
Dedicated (static) resource assignment allows one or more specific computing resources to be assigned
to a user and it allows one or more computing resources to be assigned as backup.
Support for Static roaming allows users to work from other locations. The differing display configurations
can be stacked on the client desktop to provide full access with fewer monitors.
Figure 1-3 Static (Dedicated) Connection Example
In Figure 1-3 Static (Dedicated) Connection Example on page 13, we need to grant user Tom access
to a specific computing resource. A blade PC has been configured to support Tom.
1.We assign blade PC 1 with an IP address of 15.2.76.100 to Tom. See
Manually on page 49.
2.To make sure Tom has a computing resource even if blade PC 1 is down, we assign blade PC 3
with an IP address of 15.2.76.102 to act as backup to blade PC 1. See
Manually on page 49.
Now, regardless of what client computer Tom uses, he is automatically connected to blade PC 1 at
address 15.2.76.100. If blade PC 1 fails, Tom clicks Connect and is automatically connected to blade
PC 3.
NOTE:If a blade is in a dynamic role and is reassigned as a dedicated resource to a user, that blade
is no longer available for allocation in the dynamic role to any other user, even if the current status is
Available. It is highly recommended that dedicated resources not be assigned to a dynamic resource
role, which will then help you accurately track the list of Available and In Use resources.
To Assign Resources
To Assign Resources
Common Tasks13
Configuring a Monitor Layout for a User
HP SAM allows a user to connect to multiple computing resources, thus running simultaneous RGS or
RDP sessions. Blades can be made available either by static assignment to the user or by assignment
to roles allocated to the user.
Static user/display ID to computing resource mapping allows a specific combination of user ID and client
ID to be mapped to a specific computing resource or a specific group of computing resources. When
that user logs on to that client using RGS, the preconfigured computing resources are displayed at a
specific location and resolution on the client monitor or monitors.
Figure 1-4 Monitor Layout Example
In Figure 1-4 Monitor Layout Example on page 14, user Lee has static access to two blade PCs. HP
SAM needs to be configured to display the information from these blade PCs on Lee's two monitors.
1.We create a monitor layout ID first. See
2.We assign the new monitor layout ID to Lee's access device. See
on page 55.
3.We assign the Monitor Layout ID to Lee and select the two blade PCs already assigned to him as
resources for that Monitor Layout ID. See
Both monitors have the same resolution width and height, so we enter 1280 and 1024, respectively,
next to each blade PC selected.
HP SAM treats the set of monitors as a single unit. To display output from each blade PC on a
different monitor, we have to specify the horizontal and vertical offset, the distance from upper left,
at which the output should appear.
We want output from blade PC 4 to be displayed on Lee's left monitor and output from blade PC
5 to be displayed on his right monitor, as shown in
on page 15. To display output from blade PC 4 on the left monitor, the upper left position, we
set both the horizontal and vertical offsets to 0. To display output from blade PC 5 on the right
monitor, we must set the horizontal offset one monitor resolution over, so we set that horizontal
offset to 1280. The display is not lowered, however, so the vertical offset is still 0.
Support for Static roaming allows users to work from other locations. If Lee logs in from another client,
the differing display configurations can be stacked on the client desktop to provide full access with fewer
monitors.
Manage Monitor Layout on page 56.
Manage Access Devices
Manage Users on page 48.
Figure 1-5 Monitor Offset Configuration Example
14Chapter 1 Introduction
Figure 1-5 Monitor Offset Configuration Example
Common Tasks15
2Requirements
HP SAM Hardware and Software Requirements
HP SAM Web and SQL Server Requirements
You can install HP SAM on one or more failover HP SAM Web servers with one central HP SAM SQL
database. You can also install HP SAM on one server hosting both the HP SAM Web server and SQL
database.
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
●
Recommended:
The recommended configuration depends on the scale of deployment:
Number of active users
●
Number of computing resources (such as blade PCs)
●
Geographic location and/or network architecture
●
Fault tolerance decision
●
HP SAM Web Server Software Requirements
Minimum:
One of the following operating systems must be installed:
Windows Server 2003, Standard Edition, with Service Pack 2
●
Windows Server 2003, Enterprise Edition, with Service Pack 2
●
Windows Server 2003 R2, Standard Edition, with Service Pack 2
●
Windows Server 2003 R2, Enterprise Edition, with Service Pack 2
●
16Chapter 2 Requirements
NOTE:You must install Microsoft .NET Framework Version 2.0 for the HP SAM version 2.2 Web
Server to function. It is recommended that Microsoft .NET Framework 2.0 is installed after IIS, for
appropriate asp.net registration.
SSL:
It is recommended that you configure SSL on the HP SAM Web server (which includes installing a
certificate) to encrypt your password and browser session when you log into the HP SAM administrator
console.
Only certain virtual directories under the main HP SAM Web site can be set to Require secure channel(SSL):
Manage: Access to the Web Administrator console
●
Client: Communication line between client and HP SAM server
●
Resource: Communication line between resource and HP SAM server
●
HP SAM Hardware and Software Requirements17
HP SAM SQL Database Server Hardware Requirements
If you have an existing SQL database server, you can install the HP SAM database on the same server.
However, a separate dedicated HP SAM SQL database server for HP SAM is highly recommended to
support future scaling of environment. See illustrations of possible setups allowing for load distribution
following this procedure.
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 (such as blade PCs)
●
Geographic location and/or network architecture
●
Fault tolerance decision
●
18Chapter 2 Requirements
HP SAM Hardware and Software Requirements19
20Chapter 2 Requirements
Loading...
+ 63 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.