VCAP6-DCV Deployment – Objective 1.3 – Deploy and Configure Update Manager Components 3


Main Study Page

Objective for 1.3 are broke down as the following

  • Deploy / Configure Update Manager components according to a deployment plan:
    • Configure VUM Update Manager download service
    • Configure a VUM shared repository
    • Configure VUM smart rebooting
    • Manually download updates to a VUM repository
    • Create and modify VUM baseline groups
  • Perform VUM orchestrated vSphere upgrades
  • Troubleshoot Update Manager problem areas and issues
  • Utilize Update Manager to reconfigure VUM settings

Deploy / Configure Update Manager components according to a deployment plan

The first stage for this objective is to install Update Manager, I have created a new Windows VM and mounted the vCenter .iso image.  Once mounted I choose to install Update Manager Server and choose to use the embedded SQL Express database option.

vcap1.3-01

Agree the license agreement and choose to install updates immediately or post deployment.  Point to the vCenter, if you have multiple vCenters you must have multiple Update Managers.  I use a service account that has permissions over vCenter

vcap1.3-02  vcap1.3-03

I then need to choose to install using the name or IP address and choose to use the default ports or change them, these can be changed post deployment.  Choose the install directory and a location to store the downloaded patches.  See the recommended sizings here, it is recommended to have at least 120GB for the patch repository

vcap1.3-04  vcap1.3-05

Install and finish.  Once complete the Update Manager will be registered in the Web Client, multiple Update Managers will be listed here

vcap1.3-07


Configure VUM Update Manager download service

Additionally to the Update Manager server there is also a Update Manager Download Service (UMDS) this is important for envionments where the Update Manager cannot download directly or where you have more then one Update Manager and need to use a central repository.  Check the documentation regarding prereqs here one of those is UMDS must be configured on a different server to the Update Manager server.  I have deployed another VM and mounted the vCenter .iso file but this time I select to install Update Manager Download Service I also choose to use the embedded SQL Express database option as before

vcap1.3-08

Similar to the Update Manager server install I choose if I want to configure a proxy server or not and a location for the install and patch repository.  For the UMDS I dont need to point it direct to vCenter this is only to download patches and upgrades.

vcap1.3-09  vcap1.3-10

Once installed I need to configure what I want to download and where to store the downloaded files if it is different from the install location.  To enable host upgrade downloads and virtual appliance upgrades I run the following command, to run this command first browse to the install directory

>vmware-umds -S –enable-host –enable-va

vcap1.3-13

To only enable host upgrade downloads

>vmware-umds -S –enable-host –disable-va

vcap1.3-14

It is possible to change the patch repositroy location by running the following

>vmware-umds -S –patch-store D:\VMDS

vcap1.3-15

To start the download I run the following and wait for it to complete

>vmware-umds -D

vcap1.3-16

It is possible to use the same script to point to different URLs and to import / export patch repositories.


Configure a VUM shared repository

When using multiple vCenters with multiple Update Managers it could be beneficial to point your Update Manager servers to use a share repository.  The shared repository can be on the network using a HTTP/S address, pointing to a UNC path or a mapped drive is not supported.

The following I will export my UMDS repository configured above and publish it using IIS.  First I create a folder in the root directory called UMDS

vcap1.3-17

I then export my UMDS repository to this folder, note I have installed IIS on the UMDS server so the export is to a local folder

>vmware-umds -E –export-store c:\inetpub\wwwroot\UMDS

vcap1.3-18

I now need to add the relevant MIME Types.  Open IIS – Sites – Default Web Site – UMDS – MIME Types – Add.  First add .vib with the MIME type of application/octet-stream

vcap1.3-20

I then add .sig and MIME type of application/octet-stream

vcap1.3-21

Finally make sure there is a MIME Type for .xml and test/xml.  Add if it is not already present

vcap1.3-22

Now if I browse to http://update-manager-download-service/UMDS I can see the repository

vcap1.3-24

Note if you are using Windows 2012 IIS you must enable Directory Browsing

vcap1.3-23

Now to create a share repository open the Web Client – Update Manager – Update Manager Server –  Manage – Settings – Download Settings – Edit.  Select Use a Shared Repository and enter http://update-manager-download-service/UMDS

vcap1.3-25

Choose Download Now and it should complete

vcap1.3-26


Configure VUM smart rebooting

Smart rebooting ensures vApp’s boot up in the correct order and is enabled by default.  To change the default setting open the Web Client – Update Manager – Update Manager Server –  Manage – Settings – vApp Settings

vcap1.3-27


Manually download updates to a VUM repository

It is possible to use Update Manager to add .vib files or upgrade ESXi using the build you want or even if there is a new patch you want to add without downloading everything.  To do this you can manually add files to the repository.  First download the .zip file then go to Web Client – Update Manager – Update Manager Server – Manage – Patch Repository – Import Patches 

vcap1.3-28


 

Create and modify VUM baseline groups

A Baseline can be created to install patches, host extensions or upgrades.  These Baselines can be grouped together and assigned to hosts, clusters, folders etc.  To create a Baseline Group go to Web Client – Update Manager – Update Manager Server – Manage – Host Baseline – Add Baseline Group

vcap1.3-29

Run through the wizard and add the Baselines to the group.


Perform VUM orchestrated vSphere upgrades

I have done a previous blog post on how to upgrade vSphere hosts using Update Manager see here


Troubleshoot Update Manager problem areas and issues

VMware have listed some of the regular issues in the documentation found here which I wont repeat, if you are sitting the exam it will be worth reviewing this.


Utilize Update Manager to reconfigure VUM settings

Update Manager server settings such as how it is registered with either DNS name or IP address, configured ports and download behaviour.  To change how Update Manager is registered with either DNS name or IP go to Web Client – Update Manager – Update Manager Server – Manage – Settings – Network Connectivity – Edit

vcap1.3-30

The settings page lists the configurable options

vcap1.3-31


Leave a comment

Your email address will not be published. Required fields are marked *

3 thoughts on “VCAP6-DCV Deployment – Objective 1.3 – Deploy and Configure Update Manager Components