DST proves to be a non-event.

I’m sure Congress didn’t fully consider the potential ramifications a change to DST could have on my personal computer, but as Dst-Day (March 11, 2007) approached you could see a heightened level of activity on the part of the IT division. How will the change effect email? Will the updates require a system restart? How will Blackboard react to the change? Should the desktop systems be updated prior to the servers or does it matter? Those questions and more were the common topics of discussion during the last few weeks leading up to the time change.

Looking back, it was less an issue than we had anticipated – much like Y2K turned out to be. But was the issue tame by nature or was it the proactive approach of the technicians? I’d like to think it was a combination of the two. The updates provided by the vendors worked better than we thought they would, which was the worst case scenario – and the hours of research and hard work on the part of the technologists proved to be the perfect combination.

Great job to all involved!