Frequently Asked Questions - HP BladeSystem bc2000 - Blade PC Administrator's Manual

B

Frequently Asked Questions

Question
Why do some users on the HP SAM client have to select a role
to connect and others do not.
Can the user connect to multiple computing resources from the
same client access device?
Why is my blade being marked offline even though I am able
to connect to it using Remote Desktop Connection?
My user is unable to connect to a computing resource on the
browser-based Web client. What's going on?
Why is my client not switching to the failover server in my list? Make sure the FAILOVER=1 is defined in your .SAM file
Why are my users being asked to reconnect using the HP SAM
client every time there is a network glitch?
Why are my settings not working as I set them on the client
side?
Why does my user have to type the password twice every time
to log into a computing resource?
I got an error during registration service upgrade installation.
How do I enable HP Sygate Security Agent on the Windows
XP Embedded-based thin client for the HP SAM client(s)?
Answer
Users who are in more than one role need to select the role to
connect. Those users who are in only one role do not see this
screen. A user assigned a single dedicated resource does not
have to select a role. Also, when Monitor Layout IDs and when
Multi-Session Autoconnection are used, the user is not
prompted for a role.
Yes. If multiple blades have been assigned to the user, the user
may connect to those blades. Additionally, if the user is in
multiple roles, the user can connect to blades from each role.
Check your firewall settings on the computing resource to
make sure the HP SAM port (47777) is allowed for incoming
connection.
Verify that the server is up and running and your firewall is
enabled to allow port 3389 for IEXPLORE.EXE
The Auto-Reconnect setting is set to OFF. If your network is
set to log your users off when they are disconnected or timed
out, any network glitch that disconnects a user or times the
user out will also log the user off. Another user could then
connect. If the Auto-Reconnect setting is set to On, the original
user might then automatically re-connect and bump off the new
user. HP recommends that you set Auto-Reconnect to OFF.
The settings on the client side may have been overridden by
the forced settings on the HP SAM server in the Policy tab.
This should not happen. The Active Directory policy is requiring
the user to log in to the blade interactively. Either disable this
policy or remove the Password box from the HP SAM client
by setting PasswordEnable=0 in the .SAM file. This could also
be caused by using RGS in Easy Log-in or Default mode.
Check to see if the event log is open. If so, you must close the
log so the tool can remove the old executable and upgrade to
the new one.
Go to HP Sygate Security Agent advance rules and create a
new rule for HP SAM. Add IEXPLORE.EXE and/or
hprdcw32.exe to the Application tab. On the Ports and
Protocol tab, set protocol to TCP and type 80,3389 on the
remote port line if you want both clients to work. Otherwise,
make sure port 3389 is set for IEXPLORE. You can set port 80
for the Windows XPe-based client or leave it alone (all). For
advanced methods such as an Altiris script, you can create the
71