2. DST 2007 ██ Areas that observe daylight saving time ██ Areas that once observed daylight saving time ██ Areas that have never observed daylight saving time

3. Daylight Savings Time “DST 2007” Chuck Taylor Senior Technical Account Manager Chuck.Taylor@microsoft.com Microsoft Premier Support

4. Objective 1. To share information about DST 2007 for businesses 2. Discuss potential risks / impact 3. Look at some scenarios 4. Discuss Microsoft’s product approaches for dealing with DST 2007 5. Listen to your feedback and plans

5. United States’ Energy Policy Act of 2005 is a change to the rules setting when Daylight Saving Time starts and ends. The changes were implemented as part of a federal energy conservation effort, requires that beginning in 2007 Daylight Saving Time (“DST2007”) start 3 weeks earlier and end 1 week later than current rules.

6. Keeping Time on Computer Systems Internal clocks / calendar with timezone and DST tablesInternal clocks / calendar with timezone and DST tables Local time vs Coordinated Universal Time (UTC)Local time vs Coordinated Universal Time (UTC) May or may not be synchronized with a time service via NTP (Network Time Protocol)May or may not be synchronized with a time service via NTP (Network Time Protocol)

7. DST 2007 Changes What types of systems are impacted? Just calendar/ scheduling software or others? What are some potential risks? Are there scenarios where the risks are low? Are there example scenarios where the risks are moderate or high? Why this isn’t just a U.S. issue What are some implementation strategies for managing DST2007?

8. Potential Risks / Impacts Non-computer related DST impacts * These examples come from David Prerau’s book, “Seize the Daylight: The Curious and Contentious Story of Daylight Saving time” Computer-systems related DST impacts: Calendar / scheduling applications Date / time calculations (current & historical) Transaction logging (UTC vs Local Time) Tariff billing applications

9. What is Impacted by this Change?

10. Category: Consumer Devices

11. Category: Computer and Network Infrastructure

12. Category: Scheduling / Calendar Applications & Services

13. Category: Date Calculations

14. Category: Activity Tracking / Logging

15. Five Categories for System Impact

17. http://www.microsoft.com/dst2007

18. Categories

19. Servers and Tools

20. Operating Systems KB 931836. Downlevel versions of Windows can be manually updated with tzedit.exe or scripts via KB 914387. KB 931836. Also remember embedded versions of Windows. KB 923953. Delivery method will vary with OEM’s, Mobile Operators and Business customers. OTA, tethered or a PIE download are possibilities. KB 923027. Many of these systems are embedded or customized. You may need to work with the ISV for updates. Delivery mechanisms will vary

21. Schedule and Calendar KB 926666. Exchange Server update for CDOEX. Server calendar re-basing tool. KB931667. Desktop-based calendar re-basing tool for the Outlook Data Files. Downlevel compatible with multiple versions of Outlook Data Files. Update for Entourage 11.3.3. Apple plans on supporting OS 10.4. Q.v., http://www.entourage.mvps.org/articles/daylight.html (non Microsoft site) http://www.entourage.mvps.org/articles/daylight.html

22. Other Products SQL Server Notification Server Groove SharePoint BizTalk CRM Developer Tools

23. Microsoft Support Options Mainstream Support Windows Server 2003, Windows XP SP2, Exchange 2003, Exchange 2007 Premier customers receive remediation assistance at no charge from February 1 to March 1, 2007 Extended Support Windows 2000, Exchange 2000, Outlook 2000 Extended Support for all is $4,000 Custom Support Windows NT4, Exchange 5.5, Windows XPSP1 Custom Support Agreement Premier Customer Support Fee in Arrears Hotfix fee

24. User Communication is Key Users should be made aware of the calendar issues resulting from Daylight Saving Time changes. Only the users will know if their appointments are correct. Appointments scheduled during the delta period (March 11 th – April 1 st ) need to be reviewed and considered suspect. Users need to know that they will have to verify the meeting times themselves and with any other attendees. Using informal methods such as documenting the meeting time in the subject or body of the meeting request may be beneficial.

25. Suggested Deployment Sequence Servers Clients Devices Messaging / Calendar Servers Scheduling Client Software Software App Servers Applications Tools

26. Patch Distribution Windows Update, WSUS, SMS, others Windows hotfix will not require reboot so you can detect and script additional server updates GPO’s for distribution Windows Mobile will be via OEM, Operators, or Microsoft Download Windows CE will likely be via IHV

27. Call to Action Review your applications and serversReview your applications and servers Conduct a Risk Analysis on the impact to your businessConduct a Risk Analysis on the impact to your business Check with your suppliers, partners, vendors for update and have a distribution strategyCheck with your suppliers, partners, vendors for update and have a distribution strategy http://www.microsoft.com/dst2007

28. Microsoft IT Planning MSIT DST Assessment Checklist http://go.microsoft.com/fwlink/?LinkId=83000 MSIT DST Enterprise Response Plan Http://go.microsoft.com/fwlink/?LinkId=83002 MSIT DST Patching Overview http://go.microsoft.com/fwlink/?LinkId=83004 MSIT DST Exchange TZ Update Tool Guidance http://go.microsoft.com/fwlink/?LinkId=83005 MSIT DST Outlook TZ Update Package Guidance http://go.microsoft.com/fwlink/?LinkId=83006

29. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. 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 provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.