Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

VMware ESX 3.5, Patch ESX350-200810208-UG: Updates esxupdate Documentation (1007048)

Details

Release Date: 11-06-2008

Download Size:
88KB
Download Filename:
ESX350-200810208-UG.zip
md5sum:
ff26757af4cbff1a6d86e60d4d4672e3


Product Versions ESX 3.5 Update 3
Patch Classification General
Supersedes None
Requires ESX350-200810202-UG
Virtual Machine Migration or Shutdown Required No
Host Reboot Required No
PRs Fixed 292427
Affected Hardware N/A
Affected Software N/A
RPMs Included VMware-esx-docs
Related CVE numbers None

Solution

Summaries and Symptoms

This patch fixes the following issue: The esxupdate query command does not display obsolete bundles.

Symptoms: In prior releases of ESX, the esxupdate query command does not list the obsolete bundles. To resolve this issue, esxupdate adds two new options:

  • -a or –-listall displays all installed bundles, including obsolete bundles.
  • -o or –-onlyobsolete displays only obsolete installed bundles.

Deployment Considerations

None beyond the required patch bundles and reboot information listed in the table, above.

Patch Download and Installation

See the VMware Update Manager Administration Guide for instructions on using Update Manager to download and install patches to automatically update ESX Server 3.5 hosts.

To update ESX Server 3.5 hosts when not using Update Manager, download the most recent patch bundle from http://support.vmware.com/selfsupport/download/ and install the bundle using esxupdate from the command line of the host. For more information, see the ESX Server 3 Patch Management Guide.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 1 Ratings
Actions
KB: