hello
Google
Welcome to Carpe Diem: Flaphead@Home Sign in | Join | Help

Carpe Diem: Flaphead.com

Seize the Day

News


  • Add to Technorati Favorites <script type="text/javascript" src="http://technorati.com/embed/3ni3q36ikc.js"> </script>
    This information is provided "AS IS" with no warranties, and confers no rights. Also some of the information contains my views and thoughts.
    <script src="http://widgets.technorati.com/t.js" type="text/javascript" charset="UTF-8"></script>

    Add Me! - Search Engine Optimization

    I heart FeedBurner

More DST 2007

This is turning into a REALLY REALLY BIG issue. 

To be clear the new DST change periods are: March 11, 2007 to April 1, 2007 and from October 28, 2007 to November 4, 2007.

New DST Start

March 11, 2007
(three weeks earlier)

Previous DST Start

April 1, 2007

Previous DST End

October 28, 2007

New DST End

November 4, 2007
(one week later)

 So Microsoft Articles to date are:

Blackberry Articles: US Daylight Saving Time Changes and Blackberry

IBM Articles: Lotus software- Daylight Saving Time (DST) changes for 2007 will affect Lotus software products

Also remember that any other Application that uses CDO will need to be updated.  Check with your Application vendor first.

Outlook is looking like it's going to be a pain in the butt.  The problem is that when you apply the Windows Operating System Update for DST 2007 you will have Outlook calendar appointments off by 1 hour during the DST Change periods.

The solution requires three things to be in place for Outlook calendar items to be updated properly.

  1. The Operating System update to change the time zone information.  928388 or 914387 (available now).
  2. The Exchange Server 2003 Update for CDO.  926666 (available now).
  3. The Outlook Time Zone Data update Tool and the Exchange Time Zone Update Tool. (not released yet).

If all of these patches and tools are not used together, then there will be calendar inconsistencies.  If you install update 928388 or 914387 for the operating system without doing anything else, users are notice that the meetings during the DST change periods are ahead by 1 hour.  This is expected behavior without installing the Exchange server hotfix 926666 patch and using the Outlook or Exchange tool to rebase the appointments that are in the DST change period. 

The Outlook tool is due to be released in January 2007 through the Microsoft Download Center that can update calendar items in Outlook to accommodate the changes in DST during the Extended DST period. This program is called the Time Zone Data Update Tool for Microsoft® Office Outlook® (Time Zone Data Update Tool).
Microsoft Office Outlook 2007, the newest version of Outlook, has the ability to automatically detect the DST change and prompt the process that updates a person’s calendar to conform to the new daylight saving time rules. However, the Time Zone Data Update Tool contains enhancements that improve upon what is available in Outlook 2007and should be run instead of the out-of-the-box Outlook 2007 experience.

The Time Zone Data Update Tool is necessary to update calendar items that occur during the Extended DST periods for the following earlier versions of Microsoft Outlook:

  • Microsoft Office Outlook 2003
  • Microsoft Outlook 2002
  • Microsoft Outlook 2000

The following table describes the situations when you should download and run the Time Zone Data Update Tool:

 

Outlook 2007 Outlook 2003, Outlook 2002, Outlook 2000
Not required to use the Time Zone Data Update Tool. But it is highly recommended because it includes numerous improvements. Run the Time Zone Data Update Tool.
In environments running Microsoft Exchange, a special version of the Time Zone Data Update Tool may be used to update multiple Exchange mailboxes on the server. In environments running Microsoft Exchange, a special version of the Time Zone Data Update Tool may be used to update multiple Exchange mailboxes on the server.

 

Check out the scenarios at the bottom of 931667 and MAKE SURE YOU READ THIS: http://office.microsoft.com/en-us/outlook/HA102086071033.aspx

In the mean I will keep an eye on the Exchange Download Centre (http://www.microsoft.com/downloads/results.aspx?freetext=&productID=899CABAF-A55E-402B-AA90-5114BD4C014E&categoryId=&period=120&sortCriteria=date&nr=50&DisplayLang=en)

Technorati tags: , , ,
Posted: 23 January 2007 11:33 by Paul Flaherty

Comments

Flaphead on TechNet said:

This is turning into a REALLY REALLY BIG issue. I blogged this earlier: http://blogs.flaphead.dns2go.com/archive/2007/01/23/more-dst-2007.asp

# January 23, 2007 17:50

Chris said:

Thanks for the excellent info!

# January 31, 2007 15:38

ziffle85 said:

What is the best approach for installing DST 2007 Patch for Exchange on a cluster? Is it safe to do the offline node first, fail over then do the other one? Or is it best to bring Exchange down completely and do them both at the same time?

# February 1, 2007 19:16

klinstifen said:

I second ziffle85's comment.  I have been looking for documentation concerning Exchange clusters, but MS site is lacking...anyone?

# February 8, 2007 03:17

Mike said:

Not only microsoft is affected....here's a list of other products, including sun and linux that are impacted: http://www.technologyrage.com/site/2007/01/vendor_links_1.html

I also blogged about this a month ago, and delivered the bad news to blackberry and others before that...Where were the software vendors in 2005?

# February 10, 2007 13:25

Austin said:

Try this link.... it gives you a general idea how to patch cluster servers

http://support.microsoft.com/kb/328839/en-us

# February 21, 2007 02:44

David Sharpe said:

Thanks for pointing this out.  IT professionals worldwide need to be cognizant of the DST2007 problem, especially if your organization, your organizations customers, or your partners have a physical or electronic presence in the United States or Canada. There is a small but growing body of information available online to help address the DST2007 problem. For example, there is a tool available at sharpebusinesssolutions.com/dst2007.htm to help with one of the toughest parts of the problem - unsupported versions of Microsoft Windows.

# February 25, 2007 20:08
New Comments to this post are disabled