Tag: Windows Server

In order to be prepared for the DST 2007 changes, we recommend that customers install the Windows OS update for DST (KB 931836, also available via Microsoft Update if you don’t want to wait for it to install via Automatic Updates). When you install this update, appointments on your Office Outlook calendar that occur during three weeks in March and one week at the end of October and beginning of November to be off by one hour.

To address this issue, you then use the download and run the Outlook Time Zone Update Tool to update your Microsoft Outlook calendar items that fall in the extended DST period in 2007. The Outlook tool updates the Outlook appointments that were scheduled prior to applying the DST 2007 Windows OS update. The Outlook tool is referred to as rebasing tools and allows users (or IT administrators via the Exchange wrapper) to adjust – or ‘rebase’ – these appointments. 

See my previous blog entry on preparing your calendar items for DST in 2007. (And the Outlook Time Zone Data Update Tool is available for download here on the Microsoft Download Center.)

Microsoft Office Outlook 2007, the newest version of Outlook, can automatically update a person’s calendar to conform to the new daylight saving time rules. However, the Time Zone Data Update Tool contains additional improvements that are not available in Office Outlook 2007.

Tags: Microsoft, Windows Vista, Windows, Vista, Daylight Saving Time, Daylight Savings Time, DST. 669,817; 917,247; 963,612

I received a question from a customer who had applied the Windows OS update for daylight saving time in 2007 (kb 931836). They said that they noticed that after the update was applied, events in past years also adjucted to the new DST rules as well. “How does Windows handle historical events in software applications with daylight saving time updates?”

We will release a brief document that explains how documents and computers use and display time, and how Windows is impacted. Until then, here’s a brief explanation.

Overall, Windows software applications that handle time stamps typically store those time stamps in Universal Coordinated Time (UTC). The advantage of UTC is that it is universal and invariant; it is not subject to local time zones or daylight saving time (DST) changes. However, UTC is not a format that is meaningful to most users: imagine if you (like the BBC World Service does for radio programmes) referred to all events on your calendar in GMT… that might be a bit difficult to manage when talking to other people not used to GMT.

There’s a similar issue with computer software: most events with time are recorded by software and the computer in UTC, so computers convert UTC time to local time to make it easy for local users to understand. The conversion in Windows is based on two factors: first, the time zone as designated by the user; and second, whether or not DST has been selected in the Date and Time control panel. 

So, the change in DST should not in general affect the historical time stamps as recorded in UTC in documents, but it may impact how time stamps are interpreted (and therefore displayed) by the Windows operating system (folders, document properties like creation or edited times) and certain applications for a few weeks in 2007 as well as in previous years. We refer to these additional four weeks of DST (March 11, 2007 to April 1, 2007 and October 28, 2007 to November 4, 2007) as the ‘extended DST period’ – that’s the few weeks in between the second Sunday in March and the first Sunday in April. We refer to the equivalent dates in previous years as ‘previous extended DST periods.’

Many Microsoft and third party software applications already take this into consideration. For instance, time stamps in “track changes” and inserted comments in applications such as Microsoft Office Word, Excel and PowerPoint will record the time based on the time displayed by your Windows operating system clock. (There may some ‘home-grown’ line of business applications that don’t do this use the local system time rather than UTC.)

After you have applied the latest Windows XP time zone update, these time stamps will display the correct time for items modified during the extended DST period.  Additionally, no changes are made retroactively, so time stamps in previous extended DST periods will also display correctly. 

In Outlook, past calendar items that occurred during these previous extended DST periods may be off by an hour, as Outlook derives time based on the time zone and DST selected.

Here’s an example of the impact on displayed time stamps and what you’ll experience when you view document properties in Windows XP. Once you have applied the Windows time zone update for 2007, files created during the extended DST will display the correct ‘date modified’ time in file properties.  However, date modified time stamps that fall into previous extended DST periods (e.g., March 12, 2006 to April 2, 2006) will also be shifted by one hour. In this example, the document was created on March 20, 2006 and saved it at 7:28 PM. After you apply the Windows update, the file created last year will be erroneously updated and will show a time stamp in its ‘date modified’ properties of 8:28 PM (see below). 

For more info on the impact of DST, also see my reference to the article in IT Pro Magazine on daylight saving time, and Raymond Chen’s articles on “The Date/Time control panel is not a calendar” and DST for versions of Windows prior to the release of before Vista in “Why Daylight Savings Time is nonintuitive.”

Bookmark this on Delicious
 

Tags: Microsoft, Windows Vista, Windows, Vista, Daylight Saving Time, Daylight Savings Time, DST. 446,841; 695,692; 878,993

Also avaiable via http://bit.ly/QoDxD and http://tinyurl.com/2xshqv

Joris Evers quoted me this week in his CNET article “Wake up to the ‘daylight-saving’ bug” on the changes in 2007 to daylight saving time (DST). I listen to his security webcasts and I enjoy his articles.

“There has been a great deal of speculation of what the impact could be,” said M3 Sweatt, chief of staff of Microsoft’s customer service team. “For most people, the most apparent issue is that meetings and reminders may appear to be off by one hour.”

I’m part of the Windows Core Operating System Division at Microsoft; my trusty cohort in DST at the office is Rich Kaplan, who leads our Customer Support and Services group. 

Joris then went on to say that “…Microsoft may be downplaying the risk. Some say those companies that don’t pay full attention to the issue are in for a rude awakening.”

Downplaying? I don’t think so. It’s an impact, and I think I’ve said as much: some companies may still be unaware of the impact and I appreciate the coverage in Joris’ article and others, and hope that it will help illuminate the issue.

With all apologies to Joris, this is not a bug in code as we saw in Y2K: the issue has to do with a government change to the DST entry and exit dates, and applications, services and clocks throughout the US and Canada (and many places around the world) will feel the impact.

Also, Outlook isn’t affected, but we do offer tools to rebase meetings that may be impacted (so no update or patch for Outlook is required). Windows Client and Server OS are, and the updates have been available for some time. For IT Professionals, we recommend that they deploy updates in a particular order as closely as possible, but the real advice is to ensure that IT administrators communicate with their customers (internal end users) on what’s happening. We’re doing this with our own staff at Microsoft, and shared the details in webcasts last week with MSIT. 

Tags: Microsoft, Windows Vista, Windows, Vista, Daylight Saving Time, Daylight Savings Time, DST. 434,345; 684,350; 896,087