In December 2006, Western Australia (WA) started a 3 year trial of Daylight Savings (DST) to determine whether to adopt DST.  The referendum results announced on 17th of June reported a majority of voters responding ‘No’ to adopting DST.

The rejection of daylight savings in WA means products which maintain their DST information will require an update to remove DST from the WA time zone. If an update or configuration change is not made to these products they will continue to observe the DST offset and transition into a DST offset on 25th October.

A list of Microsoft products impacted by time zone and DST changes can be found here:

List of products affected by daylight saving time

http://support.microsoft.com/gp/dst_prodlist

Microsoft DST Update Policy

In order to achieve transitions to new DST and time zones policies, Microsoft requests that governments provide the following:

1. Ample advance notice (1 year or more) of the planned change.

2. Official published confirmation of planned changes to DST or time zones.

3. Concentrated efforts on promoting the change to the affected citizens.

The Windows product team has established an annual update schedule for DST and time zone (TZ) releases with provisions for semi-annual cumulative updates as needed. More detail on this can be found here:

Microsoft Policy in Response to DST/TZ Requests

http://support.microsoft.com/gp/dst_ms_response/en-us

Product Specific Information

Following is the product specific information for currently supported Windows client and server products, Exchange Server, and SharePoint Server. These solutions are available immediately to remediate this problem.

Windows Vista, Windows 7, Windows Server 2003/R2, Windows Server 2008/R2

A hotfix has been made available and can be downloaded from here:

A hotfix is available to update the Daylight Saving Time for the "(GMT+02:00) Cairo" and "(GMT+08:00) Perth" time zones for the year 2009 for Windows Server 2003-based, Windows Vista-based, Windows Server 2008-based, and Windows 7-based computers

http://support.microsoft.com/kb/974176

Windows XP and Windows 2000

Windows XP or Windows 2000 are in the Extended Support phase of the product Support Lifecycle.  Products in the Extended Support phase only receive security updates.  DST updates are provide in accordance with Microsoft Policy in Response to DST/TZ Requests.

Options available to for these products are:

· Customers can create the registry key to update Windows XP and Windows 2000 machines. The registry key changes can be deployed following the instructions in the KB article:

How to configure daylight saving time for Microsoft Windows operating systems

http://support.microsoft.com/kb/914387

· A packaged hotfix may be able to be purchased for DST updates for affected Microsoft products in Extended Support via an Extended Hotfix Support (EHS) contract. More information on this is available from here:

Obtaining daylight saving time updates for Microsoft products

http://support.microsoft.com/gp/lifean22

Exchange Server 2007

Exchange Server 2007 uses the operating system for DST information. Customers will need to apply the appropriate Windows operating system update 974176 then perform calendar rebasing. This is necessary to correct recurring appointments spanning the previous DST transition date.

Calendar rebasing references:

How to address time zone changes by using the Time Zone Data Update Tool for Microsoft Office Outlook

http://support.microsoft.com/kb/931667

How to address daylight saving time by using the Exchange Calendar Update Tool

http://support.microsoft.com/kb/941018

The Australia 2008 Daylight Saving Planning Guide also contains references on calendar rebasing

DST - TechNet - Australia Eastern & Central 2008 Daylight Saving Changes

http://technet.microsoft.com/en-au/bb821275.aspx

Exchange Server 2003

With the release of the hotfix listed in KB article 924335, Collaboration Data Objects (CDO) time zone values will be read dynamically from Windows time zone information during a service restart. A CDO hotfix is released only if a new time zone must be added to the daylight saving time definitions.

Previously, Exchange Server 2003 used hard-coded tables to store DST information. These static tables were used across the different components of Exchange Server 2003 and by some 3rd party products. In the past, if the definition for an existing time zone had to be changed, a change had to be made to the hard-coded time zone tables in CDO and a CDO hotfix released.

Customers will need to apply the hotfix listed in KB article 924335 and the appropriate Windows operating system update 974176 then perform calendar rebasing. This is necessary to correct recurring appointments spanning the previous DST transition date.

CDO reference

CDO time zone tables cannot be automatically updated from the registry values of the Windows operating system on Exchange Server 2003

http://support.microsoft.com/kb/924335

Calendar rebasing references:

How to address time zone changes by using the Time Zone Data Update Tool for Microsoft Office Outlook

http://support.microsoft.com/kb/931667

How to address daylight saving time by using the Exchange Calendar Update Tool

http://support.microsoft.com/kb/941018

The Australia 2008 Daylight Saving Planning Guide also contains references on calendar rebasing

DST - TechNet - Australia Eastern & Central 2008 Daylight Saving Changes

http://technet.microsoft.com/en-au/bb821275.aspx

Windows SharePoint Servers (WSS) / SharePoint 2003 / Microsoft Office SharePoint Server (MOSS) 2007

Windows SharePoint Services (WSS) uses its own Timezone.xml file to store time zone information. The Timezone.xml file includes the start date and time for daylight saving time and for standard time for a specific time zone.
The Timezone.xml can be manually edited by following the guidance in the KB article:

How to manually update the DST period for a time zone definition in Windows SharePoint Services by modifying the Timezone.xml file

http://support.microsoft.com/kb/888253

 

Nick