Important: The information contained in this document has been collected from multiple sources, and is likely to change as software vendors change their information. Please check back often to assure you are recieving the most up to date information.

Abstract: Section 110 of The Energy Policy Act of 2005 extends Daylight Savings Time in the US by 4 weeks beginning in 2007. DST 2007 has widespread impact for IT at Rutgers University as most if not all operating systems and applications are affected.

Year	DST Begins 2 A.M. (Second Sunday in March)	DST Ends 2 A.M. (First Sunday in November)
2007	March 11	November 4
2008	March 9	November 2
Year	Affected Spring Dates	Affected Fall Dates
2007	March 11 - April 1	October 28 - November 4
2008	March 9 - April 6	October 26 - November 2

"Systems and applications that process dates and times using the U.S. DST rules will be affected by this change. Date and time processing functions in systems and applications in countries implementing the new DST rules (U.S., Canada, and Bermuda) are affected. Systems and applications in countries not implementing the DST changes could be affected if they support users, transactions, or applications involving countries that are implementing the new DST rules.” [1]

Unfortunately, it's simply not enough to just change the date and time zone of affected systems. Systems may have the time zone information hard-coded or embedded in multiple locations, and some applications may not rely on the system time for transaction processing. Kerberos is based on time; authentication will fail if the time between the two systems is off by more than 5 minutes. Even systems that rely on NTP should be patched as NTP will most likely give the correct time, but the time zone information will likely be wrong.

"Don't forget firewalls, routers, switches, NTP appliances, time clocks, PBX systems, IVR/ACD systems, cell phones, PDAs, photo copiers, fax machines, and all the other devices on your network that recognize or require time/date to operate properly."[2]

Microsoft: All Microsoft OS's and applications that are under original support are covered and patches are available or will be available soon. However, this is deemed a non-security hot fix and therefore there is a fee for systems and applications under Extended Support. For Microsoft OS's no longer supported, a patch will not be made available; a manual registry edit is the only option. For Microsoft applications out of support, a workaround may not be provided.

Operating System/ Application	Update?	Method
Windows Vista	No update needed	Shipping with Vista
Windows XP (SP2), Windows Server 2003/ 2003 (SP1)	Update available	Patch from MS Update.
Windows 2000	Update available - (under Extended Hotfix Support)	(1) Manual MS Patch (see below) (2) Manual edit
Windows XP SP1, Windows NT 4	Not supported	(1) XP SP1 must be upgraded to SP2. (2) NT4 is no longer supported - manual edit
Outlook 2007	Update not needed, but recommended	Outlook Time Zone Data tool – MS Update / tzmove
Outlook 2003, 2002, 2000	Update available	Outlook Time Zone Data tool – MS Update / tzmove
Exchange 2007	Update not needed
Exchange 2003 SP2	Update available	Detailed install – check Microsoft.com
Exchange 2003 SP1	Update coming soon	Detailed install – check Microsoft.com
Exchange 2000	Update available - (under Extended Hotfix Support)	Manual MS Patch (see below)
Exchange 5.5	Update available - (under Custom Support) not the same as Extended Support	Fee based patch for CSA – Recommend moving off of Exchange 5.5
Windows Mobile	Update available	Detailed install: Check Windows Mobile Update

Table 1 DST 2007 and Microsoft operating systems and applications matrix

 

According to Microsoft.com, "All versions of Windows can be manually updated using the tzedit.exe utility or other techniques documented in Knowledge Base article 914387 and similar articles for other countries, which is the preferred method of remediation for any product outside of Mainstream Support. (The tzedit.exe tool allows you to create and edit time zone entries for the Date/Time settings in the Control Panel, especially for daylight-saving time)."

File Information for DST 2007 Fix

The cumulative time zone patch for DST 2007 for supported Windows platforms was made available via Microsoft Update on February 13, 2007. All machines running Scarlet Page (a locally run WSUS server for Rutgers University) as well as scheduled Automatic Updates will have downloaded, and depending on the local machine policy, installed the time zone patch.

For Windows XP, you can verify installation:

• Either 'Update for Windows XP (KB928388)' in Add/Remove Programs (patched prior to FEB 2007)
  OR
• 'Update for Windows XP (KB931836)' in Add/Remove Programs (patched on or after FEB 2007)

• with the following File name and Version Information
  • File name: Tzchange.exe | Version: 5.1.2600.3037 or later

Similar information is available for Server products:

• February 2007 cumulative time zone update for Microsoft Windows operating systems

Microsoft Office Outlook Time Zone Data Tool: TZ Data Update Tool for MS Outlook
This tool (tzmove.exe) adjusts Microsoft Office Outlook calendar items when there has been a change in time zone definitions (saved in Microsoft Windows) or if the user is making a permanent move to another time zone. Before installing this tool, please read the Microsoft instructions for detailed information regarding Supported Operating Systems and Office versions prior to installation.

Microsoft Patch (Extended Support Software): The Office of Information Technology is pleased to announce that as of February 16, 2007, the Extended Support Hot Fix for Daylight Savings Time 2007 for Windows 2000 and Exchange 2000 have been released to Rutgers University. These patches are now available from the University Software Portal. As with all patches, it is highly recommended to perform a backup of your system prior to installing these patches.

• Microsoft Windows 2000 DST2007 Hotfix Package - v2
• Microsoft Exchange Server 2000 DST2007 Hotfix Package

For detailed information regarding MS products and Extended Suppport, please see Microsoft's Daylight Saving Time Help and Support Center

Other Vendors:
Most vendors have information relating to DST 2007 and their associated products. This is a partial list of software and the fixes for DST. It is highly recommended UCS/UCM's inventory their equipment to determine all required DST fixes and the order in which to apply them.

Apple OS X:
http://docs.info.apple.com/article.html?artnum=305056

Apple is providing software updates for Mac OS X 10.3, 10.4 and later based on worldwide time zone information available as of January 8, 2007.

Blackberry:
http://www.blackberry.com/select/dst2007/index.shtml

When the DST dates change in March 2007, BlackBerry devices will not update their clocks for the affected time zones if no patches for impacted BlackBerry software and third party software are applied. As a result, your BlackBerry device might not display correct time zone information for certain time periods during the year.

Cisco:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00807ca437.shtml

Cisco is proactive in its approach to comply with the new Daylight Saving Time (DST) changes and wants to ensure that Cisco products in our customer's networks continue to operate without impact through the DST date transition. As such, Cisco has undertaken a company-wide initiative to supply documentation that describes how to update each product.

Java (Sun Java):
http://java.sun.com/developer/technicalArticles/Intl/USDST/

The Java Runtime Environment (JRE) stores rules about DST observance all around the globe. Older JREs will have outdated rules that will be superseded by the Energy Policy Act of 2005. As a result, applications running on an older JRE may report incorrect time from March 11, 2007 through April 2, 2007 and from October 29, 2007 through November 4, 2007.

Novell:
http://www.novell.com/support/search.do?cmd=displayKC&sliceId=SAL_Public&externalId=3397648

Daylight Saving Time Adjustment Tool for Netware Servers - Novell is providing a tool that can be used to facilitate and automate this change on NetWare servers in the affected time zones called DSTSHIFT. This tool is a standard NLM and can be used on any server running NetWare 4.x, 5.x, or 6.x, including OES/NetWare 6.5.

Novell JRE / Novell JVM:
http://www.novell.com/support/search.do?cmd=displayKC&sliceId=SAL_Public&externalId=3980430

Novell has made changes to the JAVA Virtual Machine (JVM) on Novell NetWare to reflect the changes to Daylight Savings Time in North America and Canada. Novell has verified that the following versions of NetWare and JVM either already have or can easily be modified to accept Daylight Savings Time changes:

Palm:
http://www.palm.com/us/support/downloads/dst.html

Palm devices, both smartphones and handhelds, need to be updated so that they reflect the correct time when the new DST changes take effect. Without the Daylight Saving Time Updates, calendar events and email messages will indicate an hour off the actual time in locations that observe DST. Downloads are available for both the Palm OS (Treo 700p, Tungsten, Lifedrive, etc.) and the Windows Mobile devices (Treo 750, 750w, 700wx).

Sun:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102775-1

Red Hat:
http://rhn.redhat.com/errata/RHEA-2005-656.html

Additional Information for Exchange Administrators:
MSSG recommend's that all Exchange Administrator's take a look through the Microsoft Messaging Presentation slides as well as the presentation offered by Microsoft. Numerous topics were covered; some of the highlights are below:

• A new wizard is available at http://www.microsoft.com/dst2007 to guide IT and end users to ease deployment.
• Microsoft has made available Virtual PC images (only work on MS VM's) containing all the recommended software to provide an easy patching solution for Exchange. However, the Exchange tool was recently updated (to V2) and it is recommended to wait a few more days-week until the new images are made available. http://support.microsoft.com/kb/933185/en-us#
  • For under 25 users, the Outlook Tool will suffice.
  • For 25-50, either the Outlook Tool or the Exchange Tool can be used.
  • For more than 50 users, the recommendation is to use the Exchange Tool as opposed to the Outlook tool.
• The order of patching the Exchange server, the underlying OS, and the Windows clients that connect is important. It is recommended to run either the Exchange tool or the Outlook Tool ASAP after patching the OS. The reasoning is that once the OS is patched, new calendar appointments will be using the updated TZ information, and you don't want this number of new appointments to grow before running the update tool. However, MS has announced they are aware of this issue, and are working on a solution for this, which will most likely mean a new patch, or an update of the Outlook and/or the Exchange tool. I would recommend waiting to patch your Exchange servers until after this tool has been updated, which is due before the end of February. http://support.microsoft.com/gp/dst_topissues
  • Overall, it seemed the update tools are ready, but will improve prior to March 11.
• Don't forget to patch any ESM servers that are running the console for management reasons.
  • Make sure these management consoles are at SP2 of ESM - Service Pack 2 for Exchange 2003
• There have been cases where the Information Store will not mount after applying the DST patch to Exchange 2003 SP2 - http://support.microsoft.com/kb/930241/en-us
• Calendar rebasing options
  • Exchange Calendar Update Tool
    • Take notice of public folder rebasing information.
  • Outlook Time Zone Data Update Tool
• Make sure you prepare and contact vendors for applications that tie into Exchange. BlackBerry server from RIM being the prime example. http://www.blackberry.com/select/dst2007/index.shtml
• MS recommends that users include the time in the subject when planning new meetings as a possible error correction. This is a good idea to pass on to your respective departments; as new meetings are placed include the meeting time in the subject, as it could help avoid issues during the 3 week window.