Deploy / Configure Update Manager components according to a deployment plan

Deploy / Configure Update Manager components according to a deployment plan:

As part of the VCAP6 – DCV we are going to perform Objective 1.3 – Deploy and Configure Update Manager Components

For the complete VCAP – DCV Checklist visit Checklist

Part of this objective we will perform below tasks.

  • 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

VMware Update Manger- Use? Scope?

Update manager facilitates a centralized, automated patch and version management for VMware vSphere and extends it support for VMware ESXi hosts, virtual machines, and virtual appliances.

Using update manager we can perform tasks such as upgrade/patch esxi hosts, install and update 3rd party software on hosts and also upgrade of virtual machine hardware, VMware Tools and virtual machine appliances.

Update manager client plugin supports both vSphere Desktop client as well as the vSphere Web Client. Update manger web client is available from the vSphere version 5.1 U1. Even we have web client support we still need to relay on the vSphere Desktop client for certain major tasks.

If you look at the below chart you will understand the capabilities of both Web Client and Desktop client.

Desktop Client
Configure the Update Manager settings
Create and manage baselines and baseline groups
View Update Manager events
Review the patch repository and available virtual appliance upgrades
Review and check notifications
Import ESXi images
View compliance and scan results for each selected inventory object
Attach and detach baselines and baseline groups from a selected inventory object
Scan a selected inventory object
Stage patches or extensions to hosts
Remediate a selected inventory object
 
Web Client
Attach and detach baselines and baseline groups from a selected inventory object
View compliance and scan results for each selected inventory object
Scan a selected inventory object

Check out the vMware Update process chart.

Update Manger Process

 

Use case of UMDS (VMware vSphere Update Manager Download Service)

If you have a tight security implemented for your vCenter server and if it is not exposed to the internet then we can use UMDS (VMware vSphere Update Manager Download Service) service to download vMware Update manager patches. One important point to note that UMDS cannot be install on the same vCenter server.

Let’s see how to setup a fully functional vSphere Update services and its components.

  1. Mount the vSphere server 6 ISO and run the Autorun. Choose the Windows Update Manager>Server to start the installation. (If you wish to choose the Microsoft SQL 2012 Express you have an option to check the box, if you have a larger environment it is always recommended to install a complete installation of SQL Server.
  2. VUM installation is pretty easy and straight forward (I will assume that you complete this task)
  3. Once the VUM is installed lets install the UMDS in a preferred server where you have internet access. (SQL server is required)
  4. Then install the UM Client by executing the file named VMware-UMClient.exe under the Updatemanager folder in VCenter Server ISO. (vSphere Client is prerequisite for installing UM Client)
  5. Configure a shared repository as below screenshot (It supports either Local Drive, HTTP or HTTPS locations as a shared repository) Once the repository is validated you can start downloading the patches.
  6. To setup a HTTP/HTTPS shared repository you need to use any webserver service.
  7. The same repository settings will be replicated on your vCenter server VUM configuration.

    If you click on Import Patches link it will let you browse any shared location and allow you to add patches/updates manually to the repository. The best USE CASE of this feature would be, when you need to deploy a 3rd party driver/package (VIB) to your VMware ESXi Hosts.

    VUM Smart Rebooting

    Smart rebooting is another great feature on the VUM to assist in the remediation process of vApps. Once it is enabled VUM will make sure the vApp startup dependencies are maintained by selectively rebooting the virtual appliances in a sequence defined within the vApp. By default this feature is enabled so keeping it default will ensure an effective vApp remediation process.

    Another good feature of Virtual Machine remediating is it can configure to take snapshots before doing a remediation. It gives a junction point and allows to rollback.

    Configuring Baselines and Baselines Groups.

    There are two types of Baselines can be created under the Baselines and Group tab. One is for Host and the other one is for Virtual Machines and Virtual Appliances.

    Baselines can be Upgrade, Extensions or patch baselines. Baseline groups are combination of multiple Upgrade baselines, Multiple Patches baseline and Multiple Extensions baselines.

    Once the baselines are created it can be attached to a Host/Virtual Machine/Virtual Appliances.

    1. In-order to attach a baseline to a host fist select the host and click on the Update Manager Tab on the right side.
    2. Then click on Attach and select appropriate Baseline Group and click on Attach.
    3. Finally click on Stage> and then Remediate to start the process.
    4. When it reaches the Cluster Remediation Option click on the Generate Report button to see the recommendation that needs to perform before starting the remediation. It is also a good practice to select the Disable High Availability Admission Control.. and Disable FT if it is Enabled.