2,187
edits
m (Added VMware category) |
m (Added "Update Manager" bits) |
||
Line 27: | Line 27: | ||
'''Windows 2003:''' | '''Windows 2003:''' | ||
In the case of Windows 2003 the downloaded executable is a Hot Fix which must be run (Installed) on a matching OS to create deploy.cab then use something like WinZip to extract the files into the appropriate directory (see below). | In the case of Windows 2003 the downloaded executable is a Hot Fix which must be run (Installed) on a matching OS to create deploy.cab then use something like WinZip to extract the files into the appropriate directory (see below). | ||
== Update Manager == | |||
=== Import updates from another VC === | |||
Useful when you've a isolated VC (without internet access), and another with a full compliment of updates. | |||
# Copy the updates from to the VC, copy the entire Data directory | |||
#* Default location for updates <code> C:\Documents and Settings\All Users\Application Data\VMware\Vmware Update Manager\Data</code> | |||
# On the isolated VC, run a version of the following example command to update the Update Manager database | |||
#* <code> vmware-updateDownloadCli -p <path to patches>\Data -f esx -U <user ac> </code> | |||
=== Scan/Remediate fails === | |||
* '''VMware Update Manager had a failure''' | |||
* '''Patch metadata for <ESX> missing, please download patch metadata first''', despite the fact that Update Manager is fully up to date. | |||
* <code>/var/log/vmware/esxupdate.log</code> shows connection errors | |||
# On the VC, stop the VMware Update Manager Service | |||
# Edit vci-integrity.xml file | |||
#* Normally found in <code>C:\Program Files\VMware\Infrastructure\Update Manager\</code> | |||
# Edit the following entry, adding the VC IP address | |||
#* <code><PatchDepotUrl>+http://VC-IP/vci/hostupdates/hostupdate</PatchDepotUrl> </code> | |||
# Restart the VMware Update Manager Service | |||
[[Category:VMware]] | [[Category:VMware]] |