HP BladeSystem bc2000 Administrator's Guide HP Session Allocation Manager (HP - Page 79

Frequently Asked Questions, Policy, Password, Application, Ports and, Protocol, IEXPLORE

Page 79 highlights

B Frequently Asked Questions Question Answer Why do some users on the HP SAM client have to select a role to connect and others do not. 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. Can the user connect to multiple computing resources from the Yes. If multiple blades have been assigned to the user, the user same client access device? may connect to those blades. Additionally, if the user is in multiple roles, the user can connect to blades from each role. Why is my blade being marked offline even though I am able Check your firewall settings on the computing resource to to connect to it using Remote Desktop Connection? make sure the HP SAM port (47777) is allowed for incoming connection. My user is unable to connect to a computing resource on the Verify that the server is up and running and your firewall is browser-based Web client. What's going on? enabled to allow port 3389 for IEXPLORE.EXE 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? 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. Why are my settings not working as I set them on the client The settings on the client side may have been overridden by side? the forced settings on the HP SAM server in the Policy tab. Why does my user have to type the password twice every time to log into a computing resource? 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. I got an error during registration service upgrade installation. 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. How do I enable HP Sygate Security Agent on the Windows XP Embedded-based thin client for the HP SAM client(s)? 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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91

B
Frequently Asked Questions
Question
Answer
Why do some users on the HP SAM client have to select a role
to connect and others do not.
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.
Can the user connect to multiple computing resources from the
same client access device?
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.
Why is my blade being marked offline even though I am able
to connect to it using Remote Desktop Connection?
Check your firewall settings on the computing resource to
make sure the HP SAM port (47777) is allowed for incoming
connection.
My user is unable to connect to a computing resource on the
browser-based Web client. What’s going on?
Verify that the server is up and running and your firewall is
enabled to allow port 3389 for IEXPLORE.EXE
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?
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.
Why are my settings not working as I set them on the client
side?
The settings on the client side may have been overridden by
the forced settings on the HP SAM server in the
Policy
tab.
Why does my user have to type the password twice every time
to log into a computing resource?
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.
I got an error during registration service upgrade installation.
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.
How do I enable HP Sygate Security Agent on the Windows
XP Embedded-based thin client for the HP SAM client(s)?
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