On March 11, 2007, Daylight Saving Time (DST) in the United States and Canada will begin three weeks earlier than last year. Microsoft Windows and most major software suites will need patches to properly record times between March 11 and April 1. Create checklists of systems to upgrade and act now to avoid scheduling mistakes that could result in regulatory non-compliance, user confusion, and supply conflicts.

DST Patches

Where software patches are not applied, timestamps on files, appointments, and computer-controlled automatic events will be one hour off for three weeks in March and one week in November. The importance of these mis-stamped files will vary between enterprises. Some possible scenarios include:

• The enterprise could encounter compliance difficulties with improperly time-stamped e-mails that are required for legal and regulatory purposes.
• Maladjusted shipping schedules could result in missed manufacturing deadlines and lost business.
• Call center schedules could be upset, resulting in smaller sales windows and reduced time available for revenue generation.
• Overtime calculations could be off, which could in turn drive higher labor costs.
• Control systems for automated equipment from sprinklers to robots to trash compactors could need updating to ensure efficient operations and worker safety.

Generally, patching the OS on both server and client will ensure smooth transition into the new DST, since the OS supplies the timestamp to most client software. However, there are at least two notable exceptions: Microsoft Exchange and Java Runtime Environment (JRE).

Microsoft Exchange relies on the server timestamp except for applications accessing the Collaborative Data Object (CDO), such as the Lotus Notes connector, Outlook Web Access, Blackberry Enterprise Server, and various Web applications. Microsoft offers free patches for all currently supported Exchange versions and has made special arrangements for enterprises to purchase a DST patch for Exchange 2000, which is no longer in mainstream support.

JRE underlies many applications, including Symantec NetBackup and the Linux and Mac versions of Novell GroupWise client. Recent releases of JRE already incorporate the new DST rules, starting with the following versions: Java SE 6, J2SE 5.0 Update, J2SE 1.4.2_11, and J2SE 1.3.1_18. Older versions will need Java DST patches.

As the new DST schedule approaches, IT leaders are asking nitty-gritty interoperability questions:

• How will an unpatched Windows 2000 system running Outlook 2000 interact with a patched Exchange 2003 server?
• How will Windows client systems running on patched OSes interact with unpatched Novell NetWare servers?

IT leaders should note that major vendors such as Microsoft, Novell, IBM, Sun, and Red Hat are not offering detailed interoperability advice, leaving it to enterprises to test their particular configurations.

Recommendations

1. Create DST software patch checklists. List all client PCs, notebook PCs, and servers that will need OS software patches. Include embedded systems, telephony equipment, and specialized computers dedicated to production and manufacturing processes. Remember handheld devices that synchronize with user PCs.
2. Apply patches now. Start by visiting vendor Web sites for the latest information and patch links. See Microsoft's comprehensive DST Web site. Patches for software from other major enterprise software vendors are available at these DST patch pages: Cisco, Hewlett-Packard, IBM, Novell, Red Hat, Research in Motion, and Sun Microsystems (including Java).
3. Implement workarounds to compensate for software that automatically adjusts for DST. If the enterprise cannot or will not apply client and server patches, override the now-obsolete DST settings with this process:
   • March 11 at 2:00 AM, adjust time ahead on all systems by 1 hour.
   • April 1 at 1:00 AM, roll time back on all systems by 1 hour.
   • April 1 at 2:00 AM, time will adjust ahead automatically by 1 hour due to original DST settings.
   • October 28 at 12:00 AM, adjust time ahead on all systems by 1 hour.
   • October 28 at 2:00 AM, time will adjust back automatically by 1 hour due to original DST settings.
   • November 4 at 2:00 AM, roll time back on all systems by 1 hour.
4. Test interoperability. Confirm system changes before implementing them. Build a test server and install the software to the state in which it will reside on March 11. Roll the clock forward. Assess the results and adjust DST 2007 strategy accordingly. Test systems that will not be patched as well.

Bottom Line

IT leaders must ensure enterprise software properly handles the new DST dates as well as prepare contingency workarounds for applications that will not or cannot be patched. Create checklists of systems to upgrade, and act now.