Daylight Saving Time 2007 - What Does it Mean to the IT Community?
Watch the news in the coming weeks - you are likely to see at least a few articles and reports of expressed concern over the new daylight saving time date change which takes place in 2007. In case you are not aware, daylight saving time (DST) has changed to March 11 this year instead of the first weekend in April as has been previously observed. This change was caused by the enactment of the Energy Policy Act of 2005, which President George W. Bush signed on August 8, 2005.
Initially, my inclination is to think that it is no big deal; I’ll just have to set my clock ahead a few weeks earlier is all. You would think that an event like this would simply come and go, we would set our clocks, VCRs, and computers, then life would be good. But when you think about it, you realize that with our current level of technology dependence, we rely on computers and cell phones for everything these days. Meeting schedules in our computer calendar programs, certain database events, when an online bill payment transaction is posted, even what time we can call on our cell phones to get the off-peak calling cost breaks, are all tied very closely to the time on our automated systems. Computer, network, and other system time accuracies are more critical than you might think.
There is a considerable amount of buzz about the DST issue in the patch management discussion groups on the Internet right now, so this must be a somewhat serious issue for the IT community. Today, for example, I think I received on the order of 50 or so emails on the DST patch (for computers) issue alone. Believe it or not, your computer is not the only thing that will be affected by the change. It is possible that network devices (such as routers and phone system components), PDA's, cell phones, and the like will also be affected. Some are equating this to a Y2K kind of event - on a much, much smaller scale, of course, but significant nonetheless. One article I read from Gartner suggested that companies form project teams to deal with this, and even have people on call and present to watch time changes to make sure the event goes smoothly, and that all systems are operating normally.
Although it will indeed be on a much smaller scale, here are some possible consequences of the DST change that people in the IT world (and consumers as well) are concerned about:
- Bank transaction times - people worried about payments not being credited properly.
- Cell phone time syncs - people being charged for peak minute usage when they are really in a non-peak time (i.e. after 9:00pm).
- People in organizations where their computer and/or Internet access has access time restrictions, may not be able to log in and do their work - could that be someone you have to do business with?
- eBay and other online auction ending times being affected.
- Missed deadlines for time sensitive things - those folks who like to submit things online at the last minute might end up an hour late?
- Incorrect departure and arrival times for airlines or other transportation.
- There is not a patch for Windows 2000 and Windows NT servers – if you are still on these platforms, the patching process is going to be manual.
- Networking equipment (certain routers) may experience issues when the new DST time change occurs, and again when the previously recognized DST date occurs.
Applications that rely on Java Runtime Environment rules for time will report time incorrectly from March 11 – April 2 2007, and from October 29 – November 4, 2007. - Java Applications return incorrect time after using Microsoft timezone.exe tool to update Windows (IBM Article: http://www-1.ibm.com/support/docview.wss?rs=3068&context=SSNVBF&uid=swg21250503)
- Known DST bug in Palm Treo 700w devices: http://mytreo.net/archives/2006/04/treo-700w-daylight-savings-time-change-bug.html
There are a lot more possible outcomes being discussed. No need to freak out though – I just wanted you to be aware that if things seem a little strange when trying to conduct business on March 12 - now you know what might be causing problems.Kind of scary in a funny sort of way (or is that funny in a scary sort of way), but one of the network administrators in the patch management group I participate in had the following to say:
-----------------------------------------------------------------------
Just had a conversation with Verizon Wireless about DST and the Treos weare using. Very funny if a little scary.
According to the Tech I spoke with and the email I got all the Treo users need to do is turn off their Treo and turn it back on after the time change.
However they both said something to the affect of "You don't need to worry about that until April" (emphasis mine)
Apparently Verizon has not yet heard of the new DST changes.
---------------------------------------------------------------------
The patch to change your computer is available now on Windows Updates, but it is an optional software patch, so you won't get it automatically (yet). You have to visit the Windows Update site, select “Custom” instead of ”Express,” and select the Optional, Software series of patches. Be sure to install any Active-X controls when prompted to do so.
(click image to see full size view)
Next, look for the KB928388 patch as shown in the image below.
(click image to see full size view)
As of this writing, I am waiting to find out if Microsoft will make this Windows patch a critical update. Keep in mind, however, that if you are running systems with Windows 2000 or prior, a patch will not be available at all – you have to manually make the change in the registry settings and elsewhere that define when DST is changed on the computers. Either that or turn off DST altogether on those systems, and make the time change manually twice a year. If they do indeed move this up to critical, then those of you who have Windows Updates set to automatic download/automatic install will get it - well - automatically. They better do it soon, though - there is only one more "Patch Tuesday" (February 13, 2007 before the DST change in March. The March “Patch Tuesday” occurs the week following the Sunday that DST changes.
All in all, it is important not to panic. Watch the news, get the patch, and pay close attention to things that you do that require time synchronization to take place. Visit your cell phone company’s web site to find out what implications the DST event will cause for you.
Some sources you might find interesting:
- About.Com Article: http://geography.about.com/cs/daylightsavings/a/dst.htm
- EdgeBlog Article: http://www.edgeblog.net/2007/daylight-saving-time-the-year-2007-problem/
- Microsoft: http://support.microsoft.com/kb/914387
Addendums:
This article will change as new updated information is received. Check back often.
No comments:
Post a Comment