Microsoft Outlook Web Access and Microsoft Collaboration Data Objects (CDO) daylight saving time transition change for Australia in the year 2006

Programs that are built by using Microsoft Collaboration Data Objects (CDO), such as Microsoft Outlook Web Access, may not correctly reflect the change to the daylight saving time transition date because CDO maintains an internal table to track time zone information. This table is not updated with changes that are made to the operating system time zone.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must install the following registry update before you apply the hotfix. The following file is available for download from the Microsoft Download Center:
Download the registry update package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=DDA845DE-9D70-487C-8F7C-093D4DFD1899&displaylang=en)

Additionally, you must install Microsoft Exchange Server 2003 Service Pack 2 (SP2) before you apply the hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You do not have to restart the computer after you apply the hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

This issue occurs only in the year 2006 because of the custom time zones that are required.

The Commonwealth Games are scheduled to be held during March 2006 in Melbourne, Australia. Several Australian states have changed the daylight saving time transition end date to the first Sunday of April 2006. These states include New South Wales, Victoria, Australian Capital Territory, South Australia, and Tasmania.

Daylight saving time for the year 2006

For the year 2006 only, the official daylight saving time transition dates for each of the states of Australia are as follows.Note Clocks are advanced at 2 A.M. by one hour on the start day to become Summer Time. Clocks are wound back at 3 A.M. by one hour on the end day to become Standard Time.

The change to the daylight saving time will affect the transition settings for the following time zones:

• (GMT + 10:00) Canberra, Melbourne, Sydney
• (GMT + 10:00) Hobart
• (GMT + 09:30) Adelaide

For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information about a solution to the same issue in Microsoft Exchange 2000 Server, click the following article number to view the article in the Microsoft Knowledge Base: For more information about other Microsoft products that are affected by this issue, click the following article number to view the article in the Microsoft Knowledge Base: