HP Xw460c HP Integrated Lights-Out 2 User Guide for Firmware 1.75 and 1.77 - Page 166

Directory-enabled remote management, Introduction to directory-enabled remote management

Page 166 highlights

Directory-enabled remote management Introduction to directory-enabled remote management This section is for administrators who are familiar with directory services and the iLO 2 product and want to use the HP schema directory integration option for iLO 2. You must be familiar with the "Directory services (on page 134)" section and comfortable with setting up and understanding the examples. Directory-enabled remote management enables you to: • Create Lights-Out Management Objects You must create one LOM device object to represent each device that will use the directory service to authenticate and authorize users. Refer to the "Directory services (on page 134)" section for additional information on creating LOM device objects for Active Directory ("Directory services for Active Directory" on page 147) and eDirectory ("Directory services for eDirectory" on page 157). In general, you can use the HP provided snap-ins to create objects. It is useful to give the LOM device objects meaningful names, such as the device network address, DNS name, host server name, or serial number. • Configure the Lights-Out management devices Every LOM device that uses the directory service to authenticate and authorize users must be configured with the appropriate directory settings. Refer to "Configuring directory settings (on page 52)" for details on the specific directory settings. In general, you can configure each device with the appropriate directory server address, LOM object distinguished name, and any user contexts. The server address is either the IP address or DNS name of a local directory server or, for more redundancy, a multi-host DNS name. Creating roles to follow organizational structure Often, the administrators within an organization are placed into a hierarchy in which subordinate administrators must assign rights independently of ranking administrators. In this case, it is useful to have one role that represents the rights assigned by higher-level administrators and to allow the subordinate administrators to create and manage their own roles. Using existing groups Many organizations will have their users and administrators arranged into groups. In many cases, it is convenient to use the existing groups and associate the groups with one or more Lights-Out Management role objects. When the devices are associated with the role objects, the administrator controls access to the Lights-Out devices associated with the role by adding or deleting members from the groups. When using Microsoft® Active Directory, it is possible to place one group within another or nested groups. Role objects are considered groups and can include other groups directly. Add the existing Directory-enabled remote management 166

  • 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

Directory-enabled remote management 166
Directory-enabled remote management
Introduction to directory-enabled remote
management
This section is for administrators who are familiar with directory services and the iLO 2 product and want
to use the HP schema directory integration option for iLO 2. You must be familiar with the “Directory
services (on page
134
)" section and comfortable with setting up and understanding the examples.
Directory-enabled remote management enables you to:
Create Lights-Out Management Objects
You must create one LOM device object to represent each device that will use the directory service to
authenticate and authorize users. Refer to the "Directory services (on page
134
)" section for
additional information on creating LOM device objects for Active Directory ("
Directory services for
Active Directory
" on page
147
) and eDirectory ("
Directory services for eDirectory
" on page
157
). In
general, you can use the HP provided snap-ins to create objects. It is useful to give the LOM device
objects meaningful names, such as the device network address, DNS name, host server name, or
serial number.
Configure the Lights-Out management devices
Every LOM device that uses the directory service to authenticate and authorize users must be
configured with the appropriate directory settings. Refer to "Configuring directory settings (on page
52
)" for details on the specific directory settings. In general, you can configure each device with the
appropriate directory server address, LOM object distinguished name, and any user contexts. The
server address is either the IP address or DNS name of a local directory server or, for more
redundancy, a multi-host DNS name.
Creating roles to follow organizational structure
Often, the administrators within an organization are placed into a hierarchy in which subordinate
administrators must assign rights independently of ranking administrators. In this case, it is useful to have
one role that represents the rights assigned by higher-level administrators and to allow the subordinate
administrators to create and manage their own roles.
Using existing groups
Many organizations will have their users and administrators arranged into groups. In many cases, it is
convenient to use the existing groups and associate the groups with one or more Lights-Out Management
role objects. When the devices are associated with the role objects, the administrator controls access to
the Lights-Out devices associated with the role by adding or deleting members from the groups.
When using Microsoft® Active Directory, it is possible to place one group within another or nested
groups. Role objects are considered groups and can include other groups directly. Add the existing