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-200810214-UG: Updated Time Zone Rules (1007054)

Details

Release Date: 11-06-2008

Download Size:
352KB
Download Filename:
ESX350-200810214-UG.zip
md5sum:
b2b210f189ac2239890b4536549cdf82
 
Product Versions ESX 3.5 Update 3
Patch Classification General
Supersedes ESX350-200712406-BG
ESX350-200802306-BG
Requires ESX350-200810202-UG
Virtual Machine Migration or Shutdown Required No
Host Reboot Required No
PRs Fixed 285463
Affected Hardware N/A
Affected Software N/A
RPMs Included tzdata
Related CVE numbers None



Solution

Summaries and Symptoms

This patch updates the tzdata RPM with revised time zone rules for the service console. The new time zone rules reflect changes to Daylight Savings Time (DST) in the following regions:

  • Argentina
  • Chile (mainland)
  • Cuba
  • Easter Island
  • Iraq
  • Morocco
  • Pakistan
  • Palmer Polar Station, Antarctica
  • Salas y Gomez Island
  • Syria
  • Venezuela

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

  • 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: