On This Page Introduction
What the time zone changes mean for users
Microsoft products affected by DST and TZ changes
What users can do to ease the transition to a new DST rule or TZ change
Microsoft IT deployment guidance
General sequence of update actions and special considerations
Supporting the DST changes on Windows operating systems
Preparing other Microsoft software products for the DST 2008 changes
Third-party daylight saving time support information
Additional resources
List of material revisions to this article
Introduction
This article applies to users in the following regions that experienced daylight saving time (DST) and time zone (TZ) changes, particularly those in Canada and the United States:
U.S. and Canada (where DST is observed): The U.S. Energy Policy Act of 2005, passed by the U.S. Congress July 2005, extended daylight saving time in the U.S. by approximately four weeks. These four weeks are referred to in this article as the "extended DST period." For more information about DST and time zone changes, visit MSN Encarta and MSDN blogs. Canada chose to follow the U.S. change, in regions where DST is observed.
In much of Canada and the United States, DST begins on the second Sunday of March (this year, on March 9, 2008), several weeks earlier than in years prior to 2007. DST will end later on the first Sunday of November (November 2, 2008). This resulted in a new DST period that is approximately three to four weeks longer than in years prior to 2007.
- Other regions: Microsoft provided updates for several other regions or countries that enacted time zone changes, as outlined in Knowledge Base article 951072, "August 2008 cumulative time zone update for Microsoft Windows operating systems." For a current up to date list of current DST and TZ changes for the Windows operating system, see Microsoft Knowledge Base article 914387, "How to configure daylight saving time for Microsoft Windows operating systems."
Top of page What the time zone changes mean for users
When time zone or day light saving time changes are made, the time zone settings for your computer's system clock may be incorrect. This may happen during the time between the new transition date and the old transition date for your time zone unless certain updates are applied to your computer. This depends on where you live and which time zone you have selected.
Generally, when your time zone settings are incorrect your clock may be off by one hour. Applications running on your Windows-based computer may not display the correct time. To address this, Microsoft provides many free updates and tools to update your system automatically.
While changes in daylight saving time may apply to a specific time zone, the change may affect customers based outside those time zones around the world. In addition, customers who interact or integrate with systems that are based in an affected time zone or who rely on the date/time calculations may be affected. Customers who live outside an affected time zone and yet are affected should follow the guidance provided by Microsoft.
Potential Customer Impact
The change in DST will have an effect on many automated and technology reliant products. Individual consumers, small to medium size businesses, and large corporations may be affected by the new change in time. Computer-system related issues include, for example:
- Calendar and scheduling applications
- Date/time calculations (current and historical)
- Transaction logging (UTC versus local time)
- Tariff billing applications
In many cases, making the necessary changes to accommodate the new DST legislation will be a relatively minor task. Users may have to manually adjust the time on their devices when the change occurs.
In other cases, more substantial efforts may be required. In some cases, systems and applications may have to be updated directly, while in others, the application may inherit or "read" the date and time information from the underlying system on which it resides so the changes need only be made to that underlying system. Given the broad range of technology that is used today, and the integration of systems between customers, vendors, and partners, business and IT managers should determine what actions should be taken to lessen the impacts of DST and TZ changes on their organizations. Customers who have purchased new hardware or devices and who have not applied existing updates may want to check their systems and make sure they have the latest updates.
As mentioned earlier, when a change in daylight saving time or a time zone is made to a specific region, the change may affect users based outside that region. For example:
- Companies or organizations with operations, customers, or vendors based in an affected time zone may be affected.
- Companies or organizations that interact or integrate with systems that are based in an affected time zone or that rely on date/time calculations may be affected.
- Users in areas affected by time zones that do not observe DST (see below), but who travel to or interact with people in locations that do follow DST will be affected and should install the Windows operating system update.
Top of pageMicrosoft products affected by DST and TZ changes
Microsoft Product Updates
Microsoft is dedicated to helping customers in making these transitions as seamless as possible for companies and for organizations affected by new DST rules and time zone changes. Microsoft is further committed to working with others in the industry to address the broader challenges presented by these changes, and to provide various updates and tools to customers to address DST and TZ changes.
As noted in this article, Microsoft product teams are moving to a regular cadence for publishing updates that reflect newly legislated DST rules and time zone changes. This effort follows the established regular update cadence for the Windows operating system. These regular "Cumulative DST and Time Zone Updates" are scheduled for release annually in November/ December (to the Download Center and Windows Update, respectively) for the following calendar year. As needed, Microsoft will also provide a semi-annual update in the July/August timeframe to accommodate late-breaking changes that may occur in the second half of the calendar year.
Several Microsoft products are affected by DST
For Microsoft products that are affected by DST and TZ changes, the most recent versions will not require an update. However, earlier versions will. For more information, see the section on Supporting the DST changes on Windows operating systems.
| Some of the Microsoft products that are affected by DST changes |
- Microsoft Windows
- Microsoft Windows Mobile
- Microsoft Windows SharePoint Services
- Microsoft Exchange Server
- Microsoft Office Outlook
- Microsoft Office Live Meeting
- Microsoft Dynamics CRM
- Microsoft SQL Server Notification Services
- Microsoft Commerce Server
|
Depending on the particular product or scenario, these updates will be released through Microsoft Customer Support Services (CSS), hotfixes incorporated in Knowledge Base articles, Windows Update, Microsoft Update, Windows Server Update Services (WSUS), and the Microsoft Download Center. For more information about products that are affected by the DST changes and that may require action, see the Microsoft products affected by DST section.
Top of page What users can do to ease the transition to a new DST rule or TZ change
All people who use Microsoft products that are affected by the time change should give extra attention to meetings and appointments that are scheduled between the extended DST periods for a given time zone. (In this article, the terms "meetings" and "appointments" will be used interchangeably.) Users should view all appointments between these date ranges as suspect until they communicate with all meeting invitees to make sure that the item shows up correctly on everyone's calendar, both internally and externally. To minimize confusion during the affected date ranges, it is best to:
- Include the time of the meeting in the e-mail request so that invitees can double-check the correct meeting time (such as, "Project brainstorming - 11:00 A.M. Central Time").
- Use caution with the appointments and meetings in the extended DST period. When in doubt, verify the correct time with the organizer.
- Consider printing your weekly calendars during the extended DST period. Print before you apply the Windows update and run the Outlook or Exchange Time Zone Data Update tools. This will help you keep track of which meetings were scheduled before and after you run the update. Note that the update contains the updated time zone definitions.
Top of pageMicrosoft IT deployment guidance
The following links provide information that Microsoft learned in deploying daylight saving time changes in the enterprise during the changes that occurred in 2007 in the U.S. This information may help your organization in preparing for changes.
XPS format:
To view these documents on computers that do not have Vista or Internet Explorer 7 installed, visit the following Web site to download and install the free XPS viewer:
http://www.microsoft.com/whdc/xps/viewxps.mspx
PDF format:
To view these documents on computers that do not have the Adobe reader software installed, visit the following Web site to download and install the free PDF viewer:
http://www.adobe.com/products/acrobat/readstep2.html
Top of page General sequence of update actions and special considerations
Because many calendar environments have an interconnected system of applications, each environment must be adjusted to accommodate the new DST rules.
Recommended sequence of DST update actions
Note Please note that KB articles may be superseded. Please review the documentation carefully before you apply any updates.
To update your computer, follow this sequence.
| For IT administrators who are running Microsoft Exchange Server |
| 1. | Apply updates to Windows operating systems on individual workstations. | Windows Server KB article 951072 (as of August 2008) | |
| 2. | Apply updates to Windows operating systems on Windows Servers. | Windows Server KB article 951072. | |
| 3. | Apply the Exchange Server DST update. | Exchange Server 2003 KB article 956398. For other versions of Exchange Server see the List of products affected by daylight saving time. | |
| 4. | The IT administrator has one of four alternatives (pros and cons of each alternative are described later in this article):- Push out the Outlook Time Zone Data Update tool to the clients and let the users update their own mailboxes.
- Run the Exchange Calendar Update tool against all affected users, servers, or both.
- Do not run the Exchange Calendar Update tool or the Outlook Time Zone Data Update tool. Ask users to examine their calendars and rebook as necessary.
- Run the Exchange Calendar Update tool against all affected users, servers, or both, but only modify recurring appointments. Then ask users to rebook single instance appointments that fall into the extended DST period or ask them to run the Outlook Time Zone Data Update tool.
| IT administrators are strongly advised to refer to the Exchange Calendar Update tool (941018) and consider all potential effects on their IT environments and user base of those alternatives before they run the Exchange Calendar Update tool. | Exchange Time Zone Data Update tool 941018. Outlook Time Zone Data Update tool 931667. Utilizing Time Zone Data Update Tool for Microsoft Office Outlook V3.0 functionality in the Exchange Calendar Update Configuration Tool V 2.0 (blog post) |
| For small business, home, or consumer computer users running Windows and Outlook but not Exchange Server |
| 1. | Apply updates to Windows operating systems on individual computers. | Windows operating systems KB article 951072 (as of August 2008). |
| 2. | Run the Outlook Time Zone Data Update tool. Note Run the tool as soon as possible after you apply the updates to help ensure consistent application of DST rules. | Outlook Time Zone Data Update tool - KB 931667. |
| For mobile device users running Windows Mobile or Windows CE |
| 1. | Apply updates to Windows operating systems on individual computers. | Windows operating systems KB article 951072 (as of August 2008). |
| 2. | Run the Outlook Time Zone Data Update tool. Note Run the tool as soon as possible after you apply the updates to ensure consistent application of DST rules. | Outlook Time Zone Data Update tool - KB 931667. |
| 3. | Apply updates to Windows Mobile. | Windows Mobile KB article 950885 (March 2008). |
The following items should be noted to help ensure maximum accuracy of calendar updates:
- Rapid succession of steps is important: As mentioned earlier, it is better to run the Outlook or Exchange Time Zone Data Update tool as soon as possible after the time that the Windows operating system time zone updates are applied to all computers. If calendar items in the extended DST period are scheduled after the operating system updates are applied but before the tool is run, they will incorrectly be moved one hour earlier. To correct such calendar items, organizers should manually update such items to help make sure that they are scheduled accurately for themselves and all invitees.
- All connected devices must be updated: Even if you correctly update your computer, when you view your calendar from a non-updated mobile device running Windows Mobile, your calendar items during the extended DST period will be shifted by one hour. Items created on a Windows Mobile device that does not have the update applied must be updated on your computer by running the Outlook Time Zone Data Update tool again.
- If other users have not updated their calendars, it will affect other users: The Outlook Time Zone Data Update tool only updates meetings for which the user is the organizer and then automatically sends updates for those meetings to attendees. So, meetings that you are invited to but did not organize will not be updated until the organizer updates the meeting and an update is sent to you through Outlook. You must accept these updates in Outlook to correct your calendar on these meetings. Additionally, meetings created by a delegate on your behalf from a computer that does not have the update installed must be updated on your computer by running the Outlook Time Zone Data Update tool again.
Users have the option to accept the change: The tool will prompt meeting invitees about whether to change meeting times. The invitees must accept the updated meeting requests for the changes to be accurately reflected in their calendars.
- If the tool incorrectly prompts a user to move a meeting, the user has the option of un-selecting those meetings from the list and they will not be moved.
- Special considerations for single-instance calendar items created with Outlook 2003: Single-instance calendar items created with Outlook 2003 contain no time zone information so it is impossible for the Outlook Time Zone Data Update tool to determine whether they need to be updated. Recurring calendar items have the time zone information embedded. As a result, if the user has created single-instance calendar items in the extended DST period after applying the Windows operating system update that updates the time zone definitions but before they run the Outlook Time Zone Data Update tool, then they must be certain to instruct the tool not to update them by un-selecting those meetings from the list.
Time Zone information is now embedded to calendar items with the release of Office 2003 SP3. For more information, see the following article in the Microsoft Knowledge Base:
938802 Issues that are fixed in Outlook 2003 by Office 2003 Service Pack 3
- Special considerations for recurring calendar items: Recurring calendar items created by Outlook Web Access will not be updated correctly if the Exchange Server computer is updated before the desktop client that is running the update tool (applies to both Outlook and Exchange tools). Users who create recurring calendar items must be aware of this and carefully review their calendar after the update is complete, regardless of which sequence of steps were followed in their Exchange environment.
- Update resource mailbox calendars: Follow the procedures listed here to correctly update calendars in resource mailboxes.
IT administrators should fully understand and analyze the implications of the four alternatives for deploying the Outlook or the Exchange version of the tool. The respective pros and cons of each scenario are described below. For more information, please refer to Microsoft Knowledge Base articles 931667 and 941018.
- Run the Exchange Time Zone Data Update tool against all affected users, servers, or both.
- Pros: Streamlined experience for users.
- Cons: Potential risks to IT environment of running Exchange Time Zone Update tool. More likely to incorrectly modify single-instance appointments.
- Push out the Outlook Time Zone Data Update tool to the clients and let the users update their own mailboxes.
- Pros: Less likely to incorrectly modify single-instance appointments. Avoid potential risks to IT environment of running the Exchange Time Zone Update tool.
- Cons: Difficult to make sure that all users run this tool correctly and in a timely manner. Educational effort is needed to lessen confusion for users.
- Run the Exchange Time Zone Data Update tool against all affected users, servers, or both, but only modify recurring appointments. Then ask users to rebook single instance appointments that fall into the affected period or ask them to run the Outlook Time Zone Data Update tool.
- Pros: Less likely to incorrectly modify single-instance appointments.
- Cons: Potential risks of both the Exchange and Outlook Time Zone Update tools; all users will have to run the tool and risks of running the Exchange Time Zone Data Update tool still exist.
- Do not run the Exchange Time Zone Update tool or the Outlook Time Zone Update tool. Ask users to examine their calendars and rebook as necessary.
- Pros: Same as alternative #1-less likely to incorrectly modify single-instance appointments. Avoid potential risks to IT environment of running the Exchange Time Zone Update tool.
- Cons: Unless all users rebook all appointments, some calendar items will be one hour off in extended DST period.
If the steps above are not followed correctly, the following actions apply:
- If Outlook Time Zone Data Update tool is run before Windows operating systems updates are applied to all computers:
If you run the Outlook Time Zone Data Update tool before the system has the Windows operating system update, the tool will not list any calendar items to update because it will not yet recognize the new DST rules.
- If the Outlook Time Zone Data Update tool is run multiple times:
Generally, it is safe to run the tool multiple times because the tool will see all the appointments that were updated and ignore them. That said, if the user explicitly instructs the tool to ignore a set of appointments (for example, single instance appointments that are targeted at a different time zone or that the user created after updating time zone rules but before they run the time zone update tool) then the tool will continue to list those appointments in future runs and the user will have to explicitly ignore those appointments again. Similarly, it is safe to run the Outlook Time Zone Data Update tool after the Exchange Time Zone Data Update tool has been run.
Top of page Supporting the DST changes on Windows operating systems
For Windows Vista, Windows Server 2008, Windows XP Service Pack 2 (SP2), Windows Server 2003 SP1 and SP2, Windows Embedded for Point of Service, and Windows Fundamentals for Legacy PCs, Microsoft will release a single global time zone update that will include changes for the latest cumulative DST change. This time zone update will also include changes for other related DST changes and time zone behavior and settings.
| Products affected by this change in daylight saving time: |
| Windows Vista, Windows Server 2008 | Update available | See knowledge base article 951072 (Aug 2008). |
Windows XP SP2
Windows Server 2003 SP1
Windows Server 2003 SP2
Windows Embedded for Point of Service
Windows Fundamentals for Legacy PCs | Update available | Windows XP SP2 (also applicable to Windows Embedded for Point of Service and Windows Fundamentals for Legacy PCs) and Windows Server 2003 SP1 and SP2 updates are available for production deployment for all customers through the Microsoft Download Center, Knowledge Base article 951072, Windows Update and WSUS. This update is high priority or critical. |
Windows Small Business Server 2003 Std Ed.
Windows Small Business Server 2003 Prem Ed.
Windows Small Business Server 2003 R2 Std Ed.
Windows Small Business Server 2003 R2 Prem Ed. | Update available | Several SBS components require updates (Windows Server, Exchange Server, Outlook 2003, Windows SharePoint Services, SQL Server). Use the product list to determine which updates must be applied. |
| Windows 2000 | Update available - (under Extended Hotfix Support) | Windows 2000 has passed the end of Mainstream Support and will not be receiving an update without Extended Hotfix Support. All versions of Windows can be manually updated by using the Tzedit.exe utility or by using other techniques documented in Knowledge Base article 914387, Online Webcast 930688, and similar articles for other countries. That is the preferred method of remediation for any product outside Mainstream Support. (The Tzedit.exe tool lets you create and edit time zone entries for the Date/Time settings in Control Panel, especially for daylight saving time.) |
| Windows XP SP1 | Not Supported | Windows XP SP1 is no longer supported. Find information about support options for Windows XP SP1. |
| Windows NT 4.0 | Not Supported | Windows NT 4.0 is no longer supported. Find information about support options for Windows NT 4.0.
All versions of Windows can be manually updated using the Tzedit.exe utility or by using other techniques documented in Knowledge Base article 914387 and similar articles for other countries, which is the preferred method of remediation for any product outside Mainstream Support. |
Top of page Preparing other Microsoft software products for the 2008 DST changes
Daylight saving time fixes for non-Windows Microsoft products are shown in the following table. For more information, see Microsoft Support Lifecycle.
| Other Microsoft applications |
| Outlook | Microsoft Office Outlook 2007: The Outlook Time Zone Data Update tool is highly recommended when using Outlook 2007. There is a built-in tool that is included in Outlook 2007. However, the latest Outlook Time Zone Data Update tool includes many improvements over the included tool. See Knowledge Base article 931667 for more information. Microsoft Office Outlook 2003, Microsoft Outlook XP, and Microsoft Outlook 2000: If you are running Outlook 2003, Outlook 2002, or Outlook 2000 in a non-Microsoft Exchange Server IT environment, you will have to run the Outlook Time Zone Data Update tool after the applicable Windows updates are downloaded by you or the IT administrator. The tool is currently available from the Microsoft Download Center. For more information, see KB article 931667. As stated in the General Sequence section, a hotfix is available from Microsoft Customer Support to allow Outlook 2003 to stamp all appointments with the time zone information. This increases accuracy when using the Exchange Time Zone Data Update tool for time zone extraction. Office 2003 SP2 must be installed. It is also scheduled to be included with Office 2003 SP3. Contact your Technical Account Manager or Microsoft Customer Support Services for more information. All versions: For recommendations and prescriptive guidance for updating Outlook calendars to comply with DST 2007 rule changes, review the Daylight Saving Time Correction for Microsoft Office Outlook Calendars - Help desk guidelines Web site. The goal is to give the Outlook user a "personal touch" experience to help them understand what is happening with their calendars. You might find this helpful when you deal with end-user questions or when answering their helpdesk calls about the subject. |
| Office | Office 2003 and 2007 Microsoft Office: Upcoming changes to DST might affect the time stamps on the file properties and the tracked changes in Microsoft Office programs, such as Word, Excel, PowerPoint, and Project. Items that were revised within an hour of midnight may experience problems with the new DST dates. Those dates may affect the time or date that is stamped in items that are created or modified. This occurs during the extended-DST periods or previous extended-DST periods in the following items. For more information about this issue, visit the How daylight saving time (DST) changes in 2007 affect time stamps in Officefiles Web site. |
| Exchange Server | Microsoft Exchange Server 2007: See Knowledge Base articles 941421. Microsoft Exchange Server 2003 Service Pack 2: See Knowledge Base articles 956398 and 931915. Microsoft Exchange Server 2003 Service Pack 1 is no longer supported. Microsoft Exchange 2000 Server and Exchange Conferencing Server 2000: Updates are available now. Exchange 2000 Server is under Extended Support. For more information about Extended Hotfix Support Agreements, please refer to Option #2 on the Lifecycle Announcement Web site. Microsoft Exchange Server 2003 Lotus Notes Connector: Download available on the Microsoft Download Center. Exchange versions out of mainstream support without EHSA or CSA: No workaround or update available. Exchange Update tool: The Exchange Time Zone Data Update tool only works on server-side calendars. These are local calendars that a user might have that can only be updated by the Outlook Time Zone Data Update tool. For more information about the Exchange Time Zone Data Update tool, see Knowledge Base article 956399. The Exchange Time Zone Data Update tool will allow IT administrators to update Resource Calendars. For more information, see the "Update conference rooms and resource mailboxes" section of Knowledge Base article 956399. |
| Microsoft Office SharePoint Server | Microsoft Office SharePoint Server 2007: Update coming soon |
| Windows SharePoint Services | Windows SharePoint Services 3.0: See Knowledge Base article 956612. Windows SharePoint Services 2.0: Update coming soon |
| SQL Server Notification Services | SQL Server 2005 Notification Services and SQL Server 2000 Notification Services: An update is currently available. See Knowledge Base article 931815. |
| Groove | Office Groove 2007, Groove Virtual Office 3.0, and Groove Virtual Office 3.1: For instructions to correct daylight saving time 2008 issues, see KB article 932607. |
| Office Live Meeting | Live Meeting 2005: See Knowledge Base article 939107 for DST changes that you must make in Microsoft Office Live Meeting 2005 for the year 2008. |
| Commerce Server | Commerce Server 2007 and Commerce Server 2002: See Knowledge Base article 932395. |
| Microsoft BizTalk Server | Microsoft BizTalk Server (all versions) are not affected by DST 2007 changes. However, for more information about fixes for preexisting issues related to daylight saving time, see KB article 931960 for Microsoft BizTalk Server 2004 or KB article 931961 for Microsoft BizTalk Server 2006. Although related to BizTalk Server’s handling of DST, these issues are not specific to DST 2008. |
| Microsoft Dynamics CRM | Microsoft CRM 3.0: Update coming soon |
| Pro-Clarity | Analytics Server does not require any updates. However, the operating system on the computer that is running Pro-Clarity should be updated as referenced on the Supporting the DST changes on Windows operating systems page. |
| Visual SourceSafe | Visual SourceSafe 2005 and 6.0d: See KB article 931804. |
| Windows Mobile | Windows Mobile: See KB article 949168 for information about how to update your Windows Mobile device. |
| Entourage | Entourage 2004: See Microsoft Office 2004 for Mac 11.3.7 Update. |
| Visual Studio (all versions) | See the Visual Studio and daylight saving time change page. |
Visual Studio 2002
Visual Studio .NET 2002 | Fix is available. See Fix: Visual C++ .NET 2002 C runtime daylight saving time 2007 update for the TZ environment variable problem. |
Visual Studio 2002 SP1
Visual Studio .Net SP1 | Fix is available. See Fix: Visual C++ .NET 2002 Service Pack 1 C runtime daylight saving time 2007 update for the TZ environment variable problem. |
Visual C++ .NET 2003
Visual Studio 2003
Visual Studio .NET 2003 | Fix is available. See Fix: Visual C++ .NET 2003 C runtime daylight saving time 2007 update for the TZ environment variable problem. |
Visual Studio .NET 2003 SP1
Visual Studio 2003 SP1 | Fix is available. See Fix: Visual C++ .NET 2003 Service Pack 1 C runtime daylight saving time 2007 update for the TZ environment variable problem. |
Visual C++ 2005
VC++ Express 2005
Visual Studio 2005
Visual Studio 2005 Team Edition | Fix is available. See Fix: Visual C++ .NET 2005 C runtime daylight saving time 2007 update for the TZ environment variable. |
VC++ Redist package 2005 SP1
VC++ Express 2005 SP1
Visual C++ 2005 SP1
Visual Studio 2005 SP 1 | Fix is available. See Fix: Visual C++ .NET 2005 SP1 C runtime daylight saving time 2007 update for the TZ environment variable. |
| Visual C++ Runtime Library | Fix is available. See Fix: Windows-based applications that use the TZ environment variable may not work as expected because of changes to DST. |
Windows Services For UNIX 3.0
Windows Services For Unix (SFU) 3.5
Subsystem for UNIX-based Applications (SUA) in Windows Server 2003 R2
Subsystem for UNIX-based Applications (SUA) in Windows Vista | See Knowledge Base articles 942894 and 942878. |
Top of page Third-party daylight saving time support information
The following links may provide additional information on third-party software that works with Microsoft software as it relates to the effect of the change in daylight saving time for 2008. Microsoft provides third-party contact information to help you find technical support: please contact your vendor for the most current information and updates for DST and TZ changes. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Top of page Additional resources
Windows operating systems
- August 2008 cumulative time zone update for Microsoft Windows operating systems (951072)
- How to configure daylight saving time for the United States (914387)
- Support Webcast: Deploying Microsoft Windows 2000 updates for daylight saving time changes for worldwide use (930688)
Other Microsoft products
- How to address daylight saving time by using the Exchange Calendar Update Tool (941018)
- Appointments appear off by one hour when you use Collaboration Data Objects to obtain calendar information from Exchange Server 2003 (924580)
- Addressing daylight saving time using the Outlook Time Zone Data Update Tool (931667)
- FIX: U.S. daylight saving time changes in 2007 do not occur on the correct day on Windows CE 5.0-based devices (921095)
- How to configure time zone information in Windows SharePoint Services by modifying the Timezone.xml file (888253)
- DST time zone update for SQL Server 2005 Notification Services and for SQL Server 2000 Notification Services (931815)
- How to prepare SQL Server 2005 and SQL Server 2000 for changes to daylight saving time in 2008 (931975)
Other
Top of page List of material revisions to this article
(After January 15, 2007)
| January 18, 2007 | Windows SharePoint Services update release date on Microsoft. Update change from January 23, 2007 to January 29, 2007. |
| January 24, 2007 | BizTalk Server added to affected product list. |
| January 29, 2007 | Exchange Server 2003 SP1 update is available (February). |
| January 30, 2007 | SQL Server 2005 Notification Services and SQL Server 2000. Notification Services added to affected products. |
| January 31, 2007 | Office Live Meeting added to affected product list. |
| January 31, 2007 | Visual SourceSafe added to affected product list. |
| January 31, 2007 | Time Zone Data Update Tool for Microsoft Office Outlook released. |
| February 2, 2007 | BizTalk Server entries removed after determination product not directly affected by DST 2007 issues. |
| February 6, 2007 | Add Windows Embedded, Legacy PC, Visual Studio info. |
| February 8, 2007 | Add Windows and SQL Server info. |
| August 4, 2007 | Add August 2007 cumulative time zone update for Microsoft Windows operating systems |
| August 14, 2008 | Added section on 2008 start and end dates for the United States and Canada. Revised section on other regions/ countries that enacted time zone changes in 2007, with a link added to Microsoft KB 914387. Added section on As noted here, Microsoft product teams are moving to a regular update cadence for publishing updates that reflect newly legislated DST rules and time zone changes. This effort following the Windows regular cadence. Under Microsoft Product updates, added section and link to "Microsoft products affected by DST" at http://support.microsoft.com/gp/dst_prodlist. |
| October 10, 2008 | Updated for DST 2008. Updated product KB articles and descriptions to the current updates. |
| October 16, 2008 | Added Office SharePoint Server 2007 to product list |
This information represents the current view of Microsoft Corporation on the issues discussed as of the date of publication and is subject to change without notice. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This information is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION contained herein.
Revised: October 16, 2008
