VMware VS4-ENT-PL-A Setup Guide - Page 236

Add VIBs to an Image Profile

Page 236 highlights

vSphere Installation and Setup 3 Run the New-EsxImageProfile cmdlet to create the new profile and use the -CloneProfile parameter to specify the profile you want to clone. New-EsxImageProfile -CloneProfile My_Profile -Name "Test Profile 42" This example clones the profile named My-Profile and assigns it the name Test Profile 42. You must specify a unique combination of name and vendor for the cloned profile. What to do next See "Examining Depot Contents," on page 242 for some examples of filtering. Customize the image profile by adding or removing VIBs. See "Add VIBs to an Image Profile," on page 236. Add VIBs to an Image Profile You can add one or more VIBs to an image profile if that image profile is not set to ReadOnly. If the new VIB depends on other VIBs or conflicts with other VIBs in the profile, a message is displayed at the PowerShell prompt and the VIB is not added. You can add VIBs from VMware or from VMware partners to an image profile. If you add VMware VIBs, the Image Builder PowerCLI performs validation. If you add VIBs from two or more OEM partners, no errors are reported but the resulting image profile might not work. Install VIBs from only one OEM vendor at a time. You might be able to add VIBs even if the resulting image profile is invalid. NOTE VMware can support only environments and configurations that have been proven to be stable and fully functional through rigorous and extensive testing. Use only those supported configurations. If you have to go outside of that clearly defined space, use custom VIBs. Custom VIBs lower your host compliance and, as a result, supportability. But you know the changes you made, and can maintain those changes with the custom VIB mechanism. Prerequisites n Install the VMware PowerCLI and all prerequisite software. See "Install Image Builder PowerCLI and Prerequisite Software," on page 233. n If you encounter problems running PowerCLI cmdlets, consider changing the execution policy. See "Using Image Builder Cmdlets," on page 234. n Administrators performing this task must have some experience with PowerCLI or Microsoft PowerShell. Procedure 1 Run Add-EsxSoftwareDepot for each depot you want to work with. Depot Type Remote depot ZIP file Cmdlet Run Add-EsxSoftwareDepot -DepotUrl depot_url. a Download the ZIP file to a local file path. b Run Add-EsxSoftwareDepot -DepotUrl C:\file_path\offlinebundle.zip The cmdlet returns one or more SoftwareDepot objects. 2 Run Get-EsxImageProfile to list all image profiles in all currently visible depots. Get-EsxImageProfile The cmdlet returns all available profiles. You can narrow your search by using the optional arguments to filter the output. 236 VMware, Inc.

  • 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

3
Run the
New-EsxImageProfile
cmdlet to create the new profile and use the
-CloneProfile
parameter to
specify the profile you want to clone.
New-EsxImageProfile -CloneProfile My_Profile -Name "Test Profile 42"
This example clones the profile named
My-Profile
and assigns it the name
Test Profile 42
. You must
specify a unique combination of name and vendor for the cloned profile.
What to do next
See
“Examining Depot Contents,”
on page 242 for some examples of filtering.
Customize the image profile by adding or removing VIBs. See
“Add VIBs to an Image Profile,”
on page 236.
Add VIBs to an Image Profile
You can add one or more VIBs to an image profile if that image profile is not set to ReadOnly. If the new VIB
depends on other VIBs or conflicts with other VIBs in the profile, a message is displayed at the PowerShell
prompt and the VIB is not added.
You can add VIBs from VMware or from VMware partners to an image profile. If you add VMware VIBs,
the Image Builder PowerCLI performs validation. If you add VIBs from two or more OEM partners, no
errors are reported but the resulting image profile might not work. Install VIBs from only one OEM vendor
at a time.
You might be able to add VIBs even if the resulting image profile is invalid.
N
OTE
VMware can support only environments and configurations that have been proven to be stable and
fully functional through rigorous and extensive testing. Use only those supported configurations. If you
have to go outside of that clearly defined space, use custom VIBs. Custom VIBs lower your host compliance
and, as a result, supportability. But you know the changes you made, and can maintain those changes with
the custom VIB mechanism.
Prerequisites
n
Install the VMware PowerCLI and all prerequisite software. See
“Install Image Builder PowerCLI and
Prerequisite Software,”
on page 233.
n
If you encounter problems running PowerCLI cmdlets, consider changing the execution policy. See
“Using Image Builder Cmdlets,”
on page 234.
n
Administrators performing this task must have some experience with PowerCLI or Microsoft
PowerShell.
Procedure
1
Run
Add-EsxSoftwareDepot
for each depot you want to work with.
Depot Type
Cmdlet
Remote depot
Run
Add-EsxSoftwareDepot -DepotUrl
depot_url
.
ZIP file
a
Download the ZIP file to a local file path.
b
Run
Add-EsxSoftwareDepot -DepotUrl C:\
file_path
\
offline-
bundle
.zip
The cmdlet returns one or more
SoftwareDepot
objects.
2
Run
Get-EsxImageProfile
to list all image profiles in all currently visible depots.
Get-EsxImageProfile
The cmdlet returns all available profiles. You can narrow your search by using the optional arguments
to filter the output.
vSphere Installation and Setup
236
VMware, Inc.