Configure Update Manager Download Service for VUM

By | 18/08/2017

Last year I wrote a post on how to install and configure VUM and UMDS, but never got chance to connect UMDS to VUM and ended up downloading patches directly on VUM server via internet.

Once again I am playing with UMDS in lab and in this post we will cover why we need UMDS and how to configure it.

I am not covering steps for installing VUM/UMDS here because they are pretty straight forward and if you are new to these things, you can read the instructions about installation steps from here.

What is Update Manager Download Service?

Update Manager Download Service (UMDS) is an optional component which you can deploy with update manager. We can download upgrades for virtual appliances, patch metadata, patch binaries and notifications etc using UMDS.

Why we need UMDS when VUM is there?

Its a obvious question to ask that why we need UMDS when VUM is capable of downloading and installing patches on Esxi hosts/vApps. The answer of this lies in 2 use cases discussed below:

  • If the security policies in your your environment deny Internet access for the Update Manager VM(s), you can configure UMDS on a server that has Internet Access and automate the export process and transfer files from the UMDS to the Update Manager server by setting up a Web Server on the VM on which UMDS is installed.
  • There is a one to one mapping between VUM and vCenter and if you have multiple vCenter servers in your environment, you can save yourself from deploying ‘n’ number of VUM servers and just configure a single repository in UMDS and pointing all the VUM servers to that central repository and thus saving space/resources.

After you download patch data and notifications with UMDS, and export the downloads so that they become available to the Update Manager server, Update Manager deletes the recalled patches and displays the notifications on the Notifications tab.

Exploring UMDS

Post installation of UMDS, you can use the vmware-umds command to configure the UMDS server. This executable is located in the installation directory of UMDS, which defaults to C:\Program Files (x86)\VMware\Infrastructure\Update Manager.

To list the current configuration of UMDS, run ‘vmware-umds  -G’ command

To list all available option with umds, run vmware-umds command without any arguments

dls-0.0.PNG

You can list the host platforms that is supported by UMDS 6.0 by running below command:

Configure URLs for Hosts and Virtual Appliances

By default VUM have few URL’s configured for downloading the patches etc. You can add/remove additional download URL’s for Host and VA as shown below:

Configuring UMDS and connecting it to VUM

1: Disable patch download for older version of Esxi hosts

By default UMDS 6.0 is configured to download host patches for Esxi 5.0/51. If your environment do not have any 5.X hosts, you can disable patch downloads for these by running below command:

I have disabled all 5.X versions in my lab setup.

2: Enables the download of ESXi host updates only

If you do not wish to update any virtual appliance in your environment using VUM, you can disable the downloads for VA’s by running below command:

You can play around other options available with enabling/disabling downloads as show below:

Change the UMDS Patch Repository Location

Default directory where UMDS stores all downloaded patches etc is C:\ProgramData\VMware\VMware Update Manager\Data\. You can change it by running below command:

Note: If you are running the commands from windows powershell, you need elevated access to power shell else you are gonna get registry can’t be updated error.

Downloading and Exporting Patches

Run ‘vmware-umds -D’ command to instruct UMDS to download patches based on current configuration. Once the download is completed, you will see the details about number of patches downloaded, size of the download etc.

dls-0.PNG

Once the download of patches is completed, we need to export it so that VUM server can use these. There are 2 ways of doing so:

1: Export the downloaded patches to an external drive and use it for importing it on VUM server. You can do so by creating a new directory for exporting the patches and then running the export command as shown below:

2: Second method is exporting via IIS. You need to add IIS role in your UMDS server. I am not going to cover the steps for IIS installation as there are tons of articles available on internet for doing so.

Once the IIS role has been installed, we need to add our patch repository directory as a virtual directory in IIS server.

Connect to the Web Server via IIS manager and select the default website and right click on it to add a virtual directory. Provide an alias name and location of directory where UMDS downloaded the patches

dls-6

Once the directory is added, select it and click on MIME Types.

dls-7

add .vib and .sig file extensions as MIME types.

dls-8

dls-9

Once the MIME types have been added, select the virtual directory once again and click on Directory Browsing

dls-11.PNG

Enable the directory browsing so that we can access it over URL

dls-12

Form your VUM server, try accessing the virtual directory by typing http://UMDS-FQDN/virtualdirectoryame

dls-13

Configure VUM to use the shared repository instead of direct Internet Connection

Login to Web Client, navigate to Update Manager, select the VUM Server and move to the Manage tab. Go to Settings-> Download Settings and click Edit

dls-14

Select Use a shared repository and enter the URL for the download location configured previously

dls-15

Verify the configuration by refreshing the Web Client

dls-16

And that’s it. VUM will now download the patches from UMDS instead of internet.

In next post we will see how to create baselines and remediate Esxi hosts.

I hope you find this post informational. Feel free to share this on social media if it is worth sharing. Be sociable 🙂

Category: VMware vSphere 6.X

About Alex Hunt

Hi All I am Manish Jha. I am currently working in OVH US as Operations Support Engineer (vCloud Air Operations). I have around 7 Years of IT experience and have exposure on VMware vSphere, vCloud Director,vSphere Replication, vRealize Automation, NSX and RHEL. If you find any post informational to you please press like and share it across social media and leave your comments if you want to discuss further on any post. Disclaimer: All the information on this website is published in good faith and for general information purpose only. I don’t make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this blog is strictly at your own risk. The Views and opinions published on this blog are my own and not the opinions of my employer or any of the vendors of the product discussed.