[Guest Blogger] – Pierre Roman over coffee and DST


I was having a coffee with my good friend Pierre Roman earlier this week and the topic of Daylight Savings Time came up in discussion. As a Technical Account Manager at Microsoft, it’s part of his job to contact and inform all of his customers about the resources available to them. I asked if he’d be willing to share that info with the Canadian IT Pro blog – here’s a copy of his post. I hope you find it informative.

Remember – source for all things DST and Microsoft can be found here
(He references it at the end of his post as well).

Rick Claus
IT Pro Advisor

———-

I have been extremely busy coordinating with all my customers to mitigate the effects of the DST 2007 event. But I figured you could benefit from my research.

Sunday, March 11th, 2007 is the day when the newly approved time zone changes will take effect.  Daylight Saving Time (DST) starts and end dates for timezones in Canada and the United States will transition to comply with the Energy Policy Act of 2005.  Daylight Savings Time dates in affected areas will start three weeks earlier (2:00 A.M. on the second Sunday in March) and will end one week later (2:00 A.M. on the first Sunday in November).

DSTGraphic

• At this point in time, Mexico has decided not to implement the new DST 2007 rules with the US and Canada.

• Until very recently, Newfoundland, Canada had decided not to implement the DST changes.  They have now decided to follow suit with the US and the rest of Canada.

The following information has been compiled to help you understand what products are affected and what solutions are available.  Keep in mind that this is a dynamic issue and that things may change.  I will ensure that any changes are communicated back to the blog.

Microsoft products affected by 2007 DST changes

Several Microsoft products are affected by DST. Updates to these products are being developed and tested. Some of them are currently available, with the remainder scheduled to be released soon.

Microsoft Products affected by the DST legislation

  • Windows Client
    • Windows NT 4
    • Windows 2000
    • Windows XP SP1
    • Windows XP (SP2)
  • Windows Server
    •  Windows Server 2003
    • Windows Server 2003 (SP1)
  • Windows Mobile
  • Windows SharePoint Services v2.0
  • Microsoft Exchange Server
    • MS Exchange 5.5
    • MS Exchange 2000
    • MS Exchange 2003
    • MS Exchange 2007
  • Microsoft Office Outlook
    • Microsoft Office Outlook 2000
    • Microsoft Office Outlook XP
    • Microsoft Office Outlook 2003
    • Microsoft Office Outlook 2007
  • Microsoft Office Live Meeting
  • Microsoft Dynamics CRM
  • Entourage

Available Solutions

Windows NT 4 and Windows 2000

For Windows 2000 and Windows NT, there are several methods to manually update the machine:

  1. At the local machine, use TZEdit.exe (windows tool, see above for availability)
  2. At the local machine, import registry keys from an updated machine
  3. At the local machine, use the Timezone.exe utility (command-line tool)
  4. Use a logon script to import registry keys from an updated machine
  5. Use a logon script to execute the Timezone.exe utility
  6. Use VBScript http://support.microsoft.com/kb/221542/ or http://support.microsoft.com/?id=317211

Refer to the article “How to configure daylight saving time in 2007” for more information.  http://support.microsoft.com/?kbid=914387

Windows XP SP1

No solution.  You need to upgrade to SP2 and apply the available patch

Windows XP (SP2)

A patch is available at http://support.microsoft.com/kb/931836

Windows Server 2003

A patch is available at http://support.microsoft.com/kb/931836

Windows Mobile

An article that contains information about how to modify the registry to address the DST issue is available at http://support.microsoft.com/?id=923953.

Windows SharePoint Services

Windows SharePoint Services 3.0: No update needed.

Windows SharePoint Services 2.0: A single global time zone update including changes for the United States and Canada DST change is available via Microsoft Download Center and will be available on Microsoft Update on January 23 through. (WSS update does not include New Mexico time zones.)

Please see KB articles 924881 and 888253.

Microsoft Exchange Server

Microsoft calendar software such as Outlook depends on the operating system time zone information to display time information. However, Collaboration Data Objects (CDO)-based programs such as Outlook Web Access depend on separate internal time zone tables. This update modifies these internal time zone tables to match the changes in time zone settings. Without this update, calendar items in CDO-based programs will operate as if standard time is in effect during the extra weeks of daylight saving time.

Microsoft Exchange Server 5.5:

 The update is available now. Exchange Server 5.5 is under Custom Support phase until January 2008. Customers with Customer Support Agreements (CSAs) can request a hotfix through their Technical Account Managers. If you do not have a Premier contract and a CSA you cannot have access to that hotfix

Microsoft Exchange Server 2000/Exchange Conferencing Server 2000:

Updates are available now. Exchange Server 2000 is under Extended Support. For more information on Extended Hotfix Support Agreements, please refer to Option #2 on this Lifecycle Announcement web site. http://support.microsoft.com/gp/lifean22

Exchange Server 2003 Service Pack 1:

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

Microsoft Exchange Server 2003 Service Pack 2:

If you an IT administrator running Microsoft Exchange Server in your IT environment, you will need to take additional measures to ensure the proper operation of Exchange Server and to aid in adjusting Outlook calendar items. Exchange update now through CSS, Microsoft Update, and the Microsoft Download Center and through KB article 926666. http://support.microsoft.com/kb/926666

Microsoft Exchange Server 2007:

No update needed.

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

Microsoft also released a tool to help address the issue on Exchange servers. After you install the DST updates for Microsoft Windows and for Exchange Server, all old appointments that occur during the DST change periods will be incorrectly displayed as occurring one hour later. This is true for both recurring and single-instance appointments. These appointments must be updated so that they will be displayed correctly in Outlook, in Outlook Web Access, and in CDO-based applications.

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

Microsoft Office Outlook

During the extra weeks of daylight saving time, calendar items in your programs will operate as if standard time is in effect unless you apply an update. Outlook, Microsoft Exchange, and other products use daylight saving time rules in effect since 1987.

Without an update, the following will occur for Outlook calendar items that are active during the weeks of March 11, 2007, to April 1, 2007, and October 28, 2007, to November 4, 2007:

  • Single-instance appointments and reminders will appear one hour earlier than they should.
  • Recurring appointments will appear one hour earlier than they should.
  • All-day events will shift and span two days. Existing all-day events are associated with 24 specific hours instead of a given date. In the extra weeks of daylight saving time, the event appears to move backward by one hour, which is why all-day events will then span two days.

Microsoft Office Outlook 2000, Microsoft Office Outlook XP and Microsoft Office Outlook 2003: Microsoft released an Outlook Data Update tool.  http://support.microsoft.com/kb/931667

Microsoft Office Outlook 2007: Patch is not required

CDO depends third Party Application

Third Party applications that connect to Exchange may need to be updated.  Please ensure that you have communicated with the vendors.

CDO installed as part of an Exchange System Manager install (management machines/BES servers): This is just a component of Exchange, so use Exchange patch (926666) http://support.microsoft.com/kb/926666

Microsoft Dynamics CRM

Microsoft Dynamics CRM 3.0 requires a hotfix to comply with the new start and end dates for DST. This hotfix will be available in March 2007.

This article will be updated when the hotfix is available. http://support.microsoft.com/kb/925874

Entourage

Please refer to the Mactopia page for more information. See Microsoft Office 2004 for Mac 11.3.3 Update.

http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/Office2004/Office2004_1133.xml

Recommended order of patch application

 It is recommended that you do NOT to apply patches until the Outlook/Exchange Data Update Tools are released (Targeted for January).

  1. Apply updates to Windows operating systems on Windows Servers.
  2. Apply updates to Windows operating systems on individual workstations.
  3. Apply the Exchange Server DST update
  4. The IT administrator has one of four alternatives (pros and cons of each alternative are described below):
    1. Run the Exchange Time Zone Update tool against all affected users, servers, or both.
    2. Push out the Outlook Time Zone Update tool to the clients and let the users update their own mailboxes.
    3. Run the Exchange Time Zone 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 Update tool.
    4. Run neither the Exchange Time Zone Update tool nor the Outlook Time Zone Update tool. Ask users to examine their calendars and rebook as necessary.

IT administrators are strongly advised to refer to the Exchange Time Zone Update tool (930879) and consider all potential effects on their IT environments and user base of those alternatives before running the Exchange Time  Exchange Time Zone Update tool.

Official “Preparing for daylight saving time changes in 2007” site.

For official site information on this subject please visit:

http://www.microsoft.com/dst2007

I hope this helps a little,

Regards,

Pierre Roman
Technical Account Manager

Comments (4)

  1. Kent Chen says:

    This is very helpful.  A really good summary.

    I have been working on it for a while, the most difficult part is to update the old meetings by using either Exchange tool or Office tool.  Which one do you recommend?  I prefer the exchange tool but found it’s not easy to use and also might cause the performance issue too.

    By the way, what I found is actually one hour later than the meetings should be not earlier.

    Thanks, Kent

  2. David J. Veer says:

    This is quite helpful. I would have ideally liked to run the Exchange tool as opposed to the Office tool but it only works with Outlook 2003 and later, which is not appropriate for us. So it looks like its the manual way for us. Have any recommendations for running the Outlook Update Tool for 200 machines running Outlook 2000?

    Thanks,

    David

  3. Pierre Roman says:

    Good afternoon folks,

    I wanted to reply to both Kent and David’s queries.

    Kent, both tools are essentially the same. The Outlook tool has more feedback and interaction with the user.  The Exchange tool runs silently with text files as inputs.

    We have been telling Premier customers that the decision depends on your preference and on the sophistication of your users.

    David, My only recommendation is to ensure that the time window between patching the Server and workstation OS be as short as possible.

    Other than that, the most important action is to inform your users and to plan for errors. I strongly suggest that you include the meeting time in the subject or body of each calendar items for the delta period, just in case…

    I hope this is helpful, I apologize for the late reply, but this is an issue that is keeping me very busy with the Premier customer base.

    Regards,

    Pierre Roman

    MCSE 2003, MCTS Vista

  4. Anonymous says:

    Less than a week to go – are you ready? Sunday morning at 2 am, those of us in Canada and the US will

Skip to main content