January 11, 2007
This March, Daylight Saving Time (DST) changes for the United States, starting the time change 4 weeks early. Congress in its infinite wisdom changed DST in the Energy Policy Act of 2005. Other countries such as Australia have followed suit. For most people, this will come as an early relief from winter doldrums, but for IT, the DST change is a major headache. After Year 2000, IT vendors were smart enough to start using 4-digit date codes, but DST changes are still hard-coded for the 1st Sunday of April and the last Sunday of October.
To accommodate the DST change, most IT systems must be patched. Otherwise, timestamps will be off, and some applications my fail to work. For instance, if you synchronize your Windows Smartphone with Microsoft Exchange, and you want your calendar reminders to work, plan on applying patches or fixes to Windows XP, Windows 2003, Exchange 2003 & Windows Mobile. Otherwise, you may be late for that all-important TPS meeting.
Unfortunately, this change has not received the attention it deserves, so many IT shops have not yet started, and there are only 60 days to getÂ patches testedÂ and deployed. Also, it is not enough to assume that if your servers have the correct time, your applications and databases will work. Some applications are “system time aware,” yet others require their own unique patches.
To simplify matters, I have compiled the following list of major IT vendor links to their 2007 DST fixes:
- Microsoft Overview – microsoft.com
- Microsoft Windows Registry Hack – microsoft.com
- Microsoft Windows Mobile Hack – microsoft.com
- Microsoft Windows XP & 2003 – microsoft.com
- Microsoft Exchange – microsoft.com
- Microsoft Dynamics CRM – microsoft.com
- Sun Solaris – sun.com
- Sun Java – sun.com
- IBM – ibm.com
- IBM iSeriesV5R3 PTF SI24906 – ibm.com
- IBM Lotus Notes & Domino – ibm.com
- Novell Netware – novell.com
- Novell Groupwise – novell.com
- Apple OSX – apple.com
- Cisco IOS Workaround â€“ â€śclock summer-time PDT recurring 2 Sun Mar 2:00 1 Sun Nov 2:00â€ť
- Cisco IOS Release 12.4(11)XJ – cisco.com
- RedHat RHEL 4 – redhat.com
- Ubuntu tzdata – ubuntu.com
- Fortinet – forticare.com
- Juniper – juniper.net
- Oracle 11i – oracle.com
- MySQL – mysql.com
- PostgreSQL – postgresql.org
- WordPress Plugin – suominen.com
Finally, 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. All of these will likely need either patches or manual fixes to facilitate the change.
If you haven’t started yet, don’t wait. Compile a list of your time-dependant systems, applications, databases and devices. Prioritize the list based upon importance and impact if the device isn’t patched. Check the vendor’s website for fixing the problem. If you use outsourcers, such as hosting companies, application service providers (ASP), or payroll vendors, contact them and ask them to certify their readiness for the change. Create a plan and get it done. Hint: The fastest way to find vendor patches is with our old friend Google. Try this query: (site:vendorsite.com daylight saving time 2007).
If you find any other vendor patches, please feel free to post them here in the comments section.