HP NetServer AA 4000 HP NetServer AA 6200 Solution Release 3.0 Administrator&a - Page 87

Security Features for Remote Use of Endurance Manager, When running the Endurance Manager locally

Page 87 highlights

Chapter 4 Endurance Manager provides access to either or both IOPs. Security Features for Remote Use of Endurance Manager Security features within Endurance Manager provide • Protection against software installation and uninstallation from an unprivileged account. The Endurance Setup and Uninstall procedures require Administrator privileges. If a user account without Administrator privileges attempts to install or uninstall the software, one of the following error messages is displayed, and the operation fails. - For an attempted installation: Insufficient privilege for attempted operation. HP NetServer AA Setup requires ADMIN privilege. - For an attempted uninstall: Insufficient privilege for attempted operation. HP NetServer AA Uninstall requires ADMIN privilege. • Protection against Endurance Manager access to the server from an unprivileged account. Although all users can monitor status information using the Show command, only privileged users can control a server. If you do not have permission to access the server, Endurance Manager starts, but fails to connect to the system you are attempting to monitor remotely. Instead, the system displays a message explaining that it could not connect to the Endurance Manager Redirector. Full administrative access to the remote server requires administrative privileges. Typically, this means you must be a member of the Windows NT Administrator's group on the remote system. When running the Endurance Manager locally, the account under which you logged in sets your credentials to determine your level of privilege. If logged in under an account with administrative privileges, you can use all capabilities of the Endurance Manager to administer the server. If you are running the Endurance Manager remotely, your credentials depend on whether you can connect to the Manager in such a way as to have administrative group privileges. If you connect to the Manager using credentials that always authorize administrative privileges, you can fully manage the server. It is also possible to establish a connection using a shared disk to enable administrative credentials with the server, or the user must have a matching account set 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
  • 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
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281

71
Chapter 4
Endurance Manager
provides access to either or both IOPs.
Security Features for Remote Use of Endurance Manager
Security features within Endurance Manager provide
Protection against software installation and uninstallation from an unprivileged account.
The Endurance Setup and Uninstall procedures require Administrator privileges. If a user
account without Administrator privileges attempts to install or uninstall the software, one
of the following error messages is displayed, and the operation fails.
-
For an attempted installation:
Insufficient privilege for attempted
operation. HP NetServer AA Setup requires ADMIN privilege
.
-
For an attempted uninstall:
Insufficient privilege for attempted
operation. HP NetServer AA Uninstall requires ADMIN privilege
.
Protection against Endurance Manager access to the server from an unprivileged account.
Although all users can monitor status information using the Show command, only
privileged users can control a server.
If you do not have permission to access the server, Endurance Manager starts, but fails to
connect to the system you are attempting to monitor remotely. Instead, the system displays
a message explaining that it could not connect to the Endurance Manager Redirector.
Full administrative access to the remote server requires administrative privileges. Typically,
this means you must be a member of the Windows NT Administrator
s group on the remote
system.
When running the Endurance Manager locally, the account under which you logged in sets your
credentials to determine your level of privilege. If logged in under an account with
administrative privileges, you can use all capabilities of the Endurance Manager to administer
the server.
If you are running the Endurance Manager remotely, your credentials depend on whether you
can connect to the Manager in such a way as to have administrative group privileges. If you
connect to the Manager using credentials that always authorize administrative privileges, you
can fully manage the server. It is also possible to establish a connection using a shared disk to
enable administrative credentials with the server, or the user must have a matching account set