Skip to main content

VMware Update Manager - Changing Default Location for patch repository

Today I had installed VMware Update Manager (5.5 Environment) with its default settings for downloading patches. I wanted to check and also change the path of this location. After looking within the VI client under the update manager configuration tab I could not see any reference of where this location is.

VMware has an article which describes how to see and change the location of this repository KB1004152.

1. Open vci-intergrity.xml file which by default is at C:\Program Files\VMware\Infrastructure\Update Manager\vci-integrity.xml. If you are using 64-bit Windows then the default location would be C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vci-integrity.xml

2. Search for "patchstore" and you should see something similar to below displaying what the current patch repository path is

3. Modify the path to what you would like it to be which I have got below as "D:\Patch\" and save the file

4. The new location would be empty so at this point you could copy the old directory's data to the new location. Please Note If your old location is like my one under "ProgramData" then you would need to change the view to "Show hidden files, folders, and drives" in Windows explorer.

5. Restart Update Managers service in Windows Services

6. Log back in to vCenter and open Update Manager. Go to configuration tab then download settings. Click "Download Now"

7. If you go to your new repository you should see it getting populated with new items.

8. Final step once you are happy with all of it then delete the data from the old repository location to reclaim space.

All information was gather from KB1004152.


Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://,udp:// 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net