I'm sure that's the source of heartburn for IT Administrators all over the country right now. I just got done with some DST training as support engineers (from all product areas related or not) across MSFT are being asked to help with the call volumes right now and through the weekend. This is definitely an all support hands on deck event throughout the company.
Some media outlets are touting this as a Mini-Y2K, like this recent NY Times article:
I remember exactly where I was on December 31, 1999 at a previous company, all IT staff on board waiting for the change to the new millennium, but we had already done all of our homework and testing and... it was 12:01am and we were all still alive.
By now, everyone has visited http://Microsoft.com/dst2007 , but if you're the IT Admin and you don't want a 'Wizard' and just want all of the information in front of you, check out this link if you have not already: http://support.microsoft.com/gp/dst_topissues/#a3 Scroll down to Microsoft IT deployment guidance and use Office 2007 to open the XPS or PDF documents.
These documents should answer all of your toughest questions:
Here's the OS and Outlook/Exchange/Server patching order:
1. Patch Server OS
2. Patch Client OS
3. Patch Exchange CDO
Heavy OWA users:
1. Patch Server OS
2. Patch Client OS
4. Patch CDO
** The change in patching/rebasing order is ONLY relevant if OWA users create recurring appointments from within OWA. Which explains this new order.
- Customer-ready rebasing and direct booking videos here and here.
- Listing of all affected products here.
- For customers still deciding whether to patch calendars on the client or server side, see this Pro/Con link.
What to do before you run the Exchange tool
Before you run the Exchange tool, make sure that client and server computers are updated correctly with the following updates:
Install the Windows daylight saving time update on clients. For more information about how to update a computer that is running Windows operating system software, click the following article number to view the article in the Microsoft Knowledge Base:
What to do after you run the Exchange tool
After you finish updating all Exchange servers in your environment, install the following updates on the Exchange servers:
Then, Push OL tool to people who were missed, which you can determine from the errors.txt log which catches users without TZs, odds are these are people who’ve not organized meetings, but to be sure you can send the OL tool out to them, then push out the CDO. These skipped users would not be OWA users, otherwise their TZ would be known.
- We also have a new wizard available on Office Online article, "Prepare Outlook calendar items for daylight saving time changes in 2007" (launch the wizard by clicking on the "Play Demo" button on the article page, or by clicking on picture on the blog entry here).
- We also have a notes-from-the field, which is being used at large companies for help desk to provide a walk-through of calendar validation for anyone with “calendar confusion.” Customer-ready script is on the blog.
- The latest Windows Mobile updates for DST are posted
- Mail boxes without Tzone info: here. Many companies are filling in with AD or HR database to provide the missing data on time zone extraction.
- The Connect site includes the following for products in Extended Support:
- Windows 2000; Windows 2000 CRT Update; Exchange 2000; MSJVM Update for products in Extended Support
- Office 2000 and Office XP update for CDO Outlook 2000 and Outlook 2002 updates
- MSJVM documentation has been posted to Connect.
So will I remember exactly where I was on March 11, 2007 at 1:59am, no, probably not, because my mailboxes and calendars are already updated and I'm running Vista. 🙂