HP Z620 HP Remote Graphics Software 5.4.7 - Page 101

Remote Computer (Sender) checklist, Network Interface binding

Page 101 highlights

Remote Computer (Sender) checklist Modification and verification of the Sender state can be performed either by connecting a keyboard, mouse, and monitor directly to the Remote Computer, or by using Remote Desktop Protocol to log in remotely to the Remote Computer. In either case, verify each of the following items: 1. OPTIONAL: Ensure RGS Sender licensing is set up-Beginning at RGS 5.2.0, HP implemented licensing for the RGS Sender. For an overview of RGS licensing, see RGS licensing on page 12 . For detailed information on RGS licensing, see the HP Remote Graphics Software Licensing Guide, available at http://www.hp.com/support/rgs_manuals. NOTE: Step 1 is optional because you can establish a connection from the Receiver to the Sender without a Sender license. However, as shown in Figure 2-2 Dialog generated when the RGS Sender is unlicensed on page 13, an error dialog will be displayed in the Remote Display Window if the Sender license file is missing or invalid. If you don't set up RGS licensing now, you can do it after you've verified you can establish an RGS connection. 2. Ensure you have a login account on the Remote Computer-When establishing an RGS connection, the Remote Computer will prompt you for a user name and password. Ensure that you have a login account on the Remote Computer. 3. Verify the Remote Computer login account does not have a blank password-The Remote Computer will not allow a connection for any account with a blank or undefined password. Any accounts on the Remote Computer used for connection by the Local Computer must have password protection. 4. OPTIONAL: Disable Guest login access-By default, Windows allows any user who can access a computer over the network to login with Guest access. Because this is a potential security issue, HP recommends that you disable Guest logins on the Remote Computer. To disable this policy, open the "Control Panel", selecting "Administrative Tools", selecting "Local Security Policy", expanding the "Local Policies", expanding "Security Options", and setting "Network access: Sharing and security model for local accounts" to "Classic - local users authenticate as themselves". For more information on this topic, go to: http://support.microsoft.com/kb/103674 5. Ensure that the RGS Sender is running on the Remote Computer-This can be done on Windows as follows: a. Click on Start b. Right click on My Computer c. Select manage from the menu. d. In the Computer Management console, click the + sign to expand Services and Applications and select Services. The service Remote Graphics Sender should be listed as Started. 6. Verify that the rgdiag.exe diagnostics tool passes all tests on the RGS Sender on Windows-This tool may be run any time after Sender installation. Refer to Using the RGS Diagnostics Tool on Windows on page 75 for information on running this tool. 7. Network Interface binding-Beginning with RGS 5.4.0 the Sender defaults to listening to multiple network interfaces if the computer is so equipped. If the Remote Computer has multiple network interfaces, the Sender will dynamically add or remove network interfaces without Remote Computer (Sender) checklist 85

  • 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
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247

Remote Computer (Sender) checklist
Modification and verification of the Sender state can be performed either by connecting a keyboard,
mouse, and monitor directly to the Remote Computer, or by using Remote Desktop Protocol to log in
remotely to the Remote Computer. In either case, verify each of the following items:
1.
OPTIONAL: Ensure RGS Sender licensing is set up
—Beginning at RGS 5.2.0, HP
implemented licensing for the RGS Sender. For an overview of RGS licensing, see
RGS licensing
on page
12
. For detailed information on RGS licensing, see the HP Remote Graphics Software
Licensing Guide, available at
support/rgs_manuals
.
NOTE:
Step 1 is optional because you can establish a connection from the Receiver to the
Sender without a Sender license. However, as shown in
Figure
2
-
2
Dialog generated when the
RGS Sender is unlicensed
on page
13
, an error dialog will be displayed in the Remote Display
Window if the Sender license file is missing or invalid. If you don’t set up RGS licensing now, you
can do it after you’ve verified you can establish an RGS connection.
2.
Ensure you have a login account on the Remote Computer
—When establishing an
RGS connection, the Remote Computer will prompt you for a user name and password. Ensure
that you have a login account on the Remote Computer.
3.
Verify the Remote Computer login account does not have a blank password
—The
Remote Computer will not allow a connection for any account with a blank or undefined
password. Any accounts on the Remote Computer used for connection by the Local Computer must
have password protection.
4.
OPTIONAL: Disable Guest login access
—By default, Windows allows any user who can
access a computer over the network to login with Guest access. Because this is a potential security
issue, HP recommends that you disable Guest logins on the Remote Computer. To disable this
policy, open the "Control Panel", selecting "Administrative Tools", selecting "Local Security
Policy", expanding the "Local Policies", expanding "Security Options", and setting "Network
access: Sharing and security model for local accounts" to "Classic – local users authenticate as
themselves". For more information on this topic, go to:
kb/103674
5.
Ensure that the RGS Sender is running on the Remote Computer
—This can be done
on Windows as follows:
a.
Click on
Start
b.
Right click on My Computer
c.
Select manage from the menu.
d.
In the Computer Management console, click the
+
sign to expand Services and Applications
and select Services. The service Remote Graphics Sender should be listed as Started.
6.
Verify that the rgdiag.exe diagnostics tool passes all tests on the RGS Sender on
Windows
—This tool may be run any time after Sender installation. Refer to
Using the RGS
Diagnostics Tool on Windows
on page
75
for information on running this tool.
7.
Network Interface binding
—Beginning with RGS 5.4.0 the Sender defaults to listening to
multiple network interfaces if the computer is so equipped. If the Remote Computer has multiple
network interfaces, the Sender will dynamically add or remove network interfaces without
Remote Computer (Sender) checklist
85