VMware 4817V62 Administration Guide - Page 71

Managing the vSphere Client Inventory, Understanding vSphere Client Objects

Page 71 highlights

Managing the vSphere Client Inventory 6 The topics in this section describe how to manage the objects in your vSphere environment. The views and capabilities displayed vary depending on whether the vSphere Client is connected to a vCenter Server system or an ESX/ESXi host. Unless indicated, the process, task, or description applies to all kinds of vSphere Client connections. This chapter includes the following topics: n "Understanding vSphere Client Objects," on page 71 n "Add an Inventory Object," on page 73 n "Moving Objects in the Inventory," on page 74 n "Remove an Inventory Object," on page 74 n "Browsing Datastores in the vSphere Client Inventory," on page 75 Understanding vSphere Client Objects Inventory objects in the vSphere Client include folders, datacenters, clusters, resource pools, datastores, and networks. These objects are used to help manage or organize monitored and managed hosts, as well as virtual machines. Each object in the vSphere Client has a particular place in the overall object hierarchy. An object's position in the hierarchy is determined by the object's functionality. An object's name must be unique with its parent. vApp names must be unique within the Virtual Machines and Templates view. Identifying Objects in the vSphere Client Inventory Inventory objects in the vSphere Client represent resources in your virtual infrastructure. Objects in vSphere Client are as follows: Root folder In vCenter Server only. Child objects are datacenters or subfolders. The root folder is set as a default for every vCenter Server system. You can change the name, but not add or remove it. Folders In a vCenter Server Connected Group, there is one root folder for each vCenter Server system in the group. The name of the root folder is the name of the vCenter Server system which it represents. In vCenter Server only. Child objects are datacenters, hosts, clusters, networking objects, datastores, virtual machines, templates, or subfolders. VMware, Inc. 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
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364

Managing the vSphere Client
Inventory
6
The topics in this section describe how to manage the objects in your vSphere environment.
The views and capabilities displayed vary depending on whether the vSphere Client is connected to a vCenter
Server system or an ESX/ESXi host. Unless indicated, the process, task, or description applies to all kinds of
vSphere Client connections.
This chapter includes the following topics:
n
“Understanding vSphere Client Objects,”
on page 71
n
“Add an Inventory Object,”
on page 73
n
“Moving Objects in the Inventory,”
on page 74
n
“Remove an Inventory Object,”
on page 74
n
“Browsing Datastores in the vSphere Client Inventory,”
on page 75
Understanding vSphere Client Objects
Inventory objects in the vSphere Client include folders, datacenters, clusters, resource pools, datastores, and
networks. These objects are used to help manage or organize monitored and managed hosts, as well as virtual
machines.
Each object in the vSphere Client has a particular place in the overall object hierarchy. An object’s position in
the hierarchy is determined by the object’s functionality.
An object's name must be unique with its parent. vApp names must be unique within the Virtual Machines
and Templates view.
Identifying Objects in the vSphere Client Inventory
Inventory objects in the vSphere Client represent resources in your virtual infrastructure.
Objects in vSphere Client are as follows:
Root folder
In vCenter Server only. Child objects are datacenters or subfolders. The root
folder is set as a default for every vCenter Server system. You can change the
name, but not add or remove it.
In a vCenter Server Connected Group, there is one root folder for each vCenter
Server system in the group. The name of the root folder is the name of the
vCenter Server system which it represents.
Folders
In vCenter Server only. Child objects are datacenters, hosts, clusters,
networking objects, datastores, virtual machines, templates, or subfolders.
VMware, Inc.
71