Knowledge Base

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

ESX Server 3.5, Patch ESX350-200808202-UG: Update to VMware-esx-scripts (1005895)

Details

Release Date: 13 AUGUST 2008
Document Last Updated: 13 AUGUST 2008

 

Download Size:
312KB
Download Filename:
ESX350-200808202-UG.zip
md5sum:
b58c336b504cb8711f954938344e9ca7
Product Versions ESX Server 3.5 Update 2
Patch Classification Update
Supersedes
ESX350-200802403-BG
ESX350-200803208-UG
ESX350-200804408-BG
ESX350-200805502-BG
ESX350-200806201-UG
Requires None
ESX Server Host Reboot Required
 No
Restart hostd Required
service mgmt-vmware restart		 No
Maintenance Mode Required, Power Off or Migrate Virtual Machines
 No
PRs Fixed 225832 235118 245488 246833 247381 248781 251358 254709 260193 260427 263827 265326 270070 271903 273198 274833 274928 275001 275892 276530 277798 278632 279576 279689 281713 282244 284193 284332 293214
Affected Hardware N/A
Affected Software N/A
RPMs Included VMware-esx-scripts
Related CVE numbers None

Solution

Summaries and Symptoms

This patch includes a fix that improves the handling of obsolete requirements in patch bundles.

Deployment Considerations

None

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://www.vmware.com/download/vi/vi3_patches_35.html 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

  • 0 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)
  • 0 Ratings
Actions
KB: