Don't let Daylight Savings ruin your longer day

For some reason that has escaped most of us, the United States Congress decided to change the starting date for Daylight Savings Time in 2007. DST starts on March 11, 2007, which is three weeks earlier than in previous years. While that may not present a problem for many people, it could cause problems for computer users and the professional manning help desks.

The seemingly innocuous change means that many operating systems and applications will have to be updated to reflect that change. While the worldwide information system is not likely to crash if all the systems are not updated in time, it could mean appointments and other time-sensitive events could be an hour off for a few weeks. If nothing else, DST could lead to some frustrated users and help desks.

TechRepublic has published several articles and downloads on the topic, all of which make good resources for getting systems updated and everyone on the same time frame. Here are some links to get you started:


Mark Kaelin is a CBS Interactive Senior Editor for TechRepublic. He is the host for the Microsoft Windows and Office blog, the Google in the Enterprise blog, the Five Apps blog and the Big Data Analytics blog.


It seems Daylight Savings Time just causes trouble. Even without technical issues everyone has to set their clocks forward and back. If DST is so great, why not do it all year? I'd gladly trade my clock time being an hour off of natural local time in exchange for never having to spring forward and back any more.

Editor's Picks