Difference between revisions of "Virtual Centre"

Line 171:

== Update Manager ==

=== Import Offline Bundle ===

Useful for when you need to apply additional drivers etc to your ESX's

Often drivers are only available as an ISO, in which case you need to mount the image and extract the offline bundle ZIP file (use something like [http://www.winimage.com/download.htm WinImage]

# Open '''Update Manager Administrator''', and go to the '''Patch Repository''' tab

# Click on the '''Import Patches''' link

# Locate the ZIP file and click next, the bundle will be imported

In order to deploy the bundle you'll need to create a baseline with the bundle as a member. You've three choices here

* Create an individual baseline for that bundle, then when newer versions of the driver become available, just add it to the existing baseline

** Best for situations where you've different types of hardware being managed by the same vCentre and so you need to distinguiish between different ESX's and different bundles

* Add the bundle to an existing baseline

** Best for when you've got uniform hardware, and you like to apply uniform waves (aka controlled releases) of deployments to your ESX's

* Create an individual baseline for that bundle, that gets added to when new versions become available, and add the baseline to a baseline group which applies to clusters etc (hybrid of both of the above)

=== Import updates from another VC ===

Useful when you've a isolated VC (without internet access), and another with a full compliment of updates.

@@ Line 171: / Line 171: @@
 == Update Manager ==
+=== Import Offline Bundle ===
+Useful for when you need to apply additional drivers etc to your ESX's
+Often drivers are only available as an ISO, in which case you need to mount the image and extract the offline bundle ZIP file (use something like [http://www.winimage.com/download.htm WinImage]
+# Open '''Update Manager Administrator''', and go to the '''Patch Repository''' tab
+# Click on the '''Import Patches''' link
+# Locate the ZIP file and click next, the bundle will be imported
+In order to deploy the bundle you'll need to create a baseline with the bundle as a member. You've three choices here
+* Create an individual baseline for that bundle, then when newer versions of the driver become available, just add it to the existing baseline
+** Best for situations where you've different types of hardware being managed by the same vCentre and so you need to distinguiish between different ESX's and different bundles
+* Add the bundle to an existing baseline
+** Best for when you've got uniform hardware, and you like to apply uniform waves (aka controlled releases) of deployments to your ESX's
+* Create an individual baseline for that bundle, that gets added to when new versions become available, and add the baseline to a baseline group which applies to clusters etc (hybrid of both of the above)
 === Import updates from another VC ===
 Useful when you've a isolated VC (without internet access), and another with a full compliment of updates.

Difference between revisions of "Virtual Centre"

Navigation menu

Search