Channel Slams Microsoft For Daylight Savings Time Snafu

As the IT industry enters the last two days before daylight savings time, many solution providers are scrambling to help customers avert major impacts from computer hardware and software that have yet to be updated to reflect the U.S. government's change in the starting date for daylight savings time -- and they are directing much of their anger at Microsoft because of it. "Unlike Y2K, this is not a bust," said Marc Harrison, a professional engineer at Silicon East, a Manalapan, N.J.-based solution provider. Daylight savings time, or DST, traditionally started on the first Sunday in April, but starting this year it has been moved by the government to the second Sunday in March as an energy-saving measure.

Unfortunately, many computer systems and applications, which automatically update for DST based on the traditional timing, were not updated to reflect the new timing. Microsoft appears to be the main source of frustration because of the need to update the vast majority of its applications, with Windows Vista, Exchange Server 2007, and SharePoint Services 3.0 being the main exceptions. Rex Frank, CTO of Alvaka Networks, an Irvine, Calif.-based MSP, said that while DST is a serious issue, many customers were lulled into a false sense of security because of their Y2K experience.

View: The full story
News source: CRN

Report a problem with article
Previous Story

Verizon ruling could be hard on Vonage

Next Story

DFI to include AMD embedded solutions in lineup

26 Comments

Commenting is disabled on this article.

I think it's high time we struck daylight time entirely.

Ideally, we'd just switch to using the same time all around the world. Is it really so hard to deal with the concept that the clock says "4PM" when you head off to work instead of "8AM"?

YOU PEOPLE WHO THINK THIS DST EXTRAVAGANZA IS SIMPLY SILLY PEOPLE WHO CANT CHANGE THERE OWN COMPUTER CLOCK HAVE COMPLETELY MISSED THE POINT! IT HAS NOTHING TO DO WITH END USER SYSTEMS, IT HAS EVERYTHING TO DO WITH SERVERS, EMAIL CLIENTS, BLACKBERRY SERVERS AND ADMINISTRATION!!!!!!!!!!!!!!!!!!!!!

its the IT guys who have lost sleep and where up untill midnight friday getting the last of there clients patched that are having a discussion.

LOL how true...

We were up for weeks trying to get our servers and client machines patched on time and only finished last weekend.

It still amazes me how many people who read and post on Neowin think that all the MS news about updates and patches posted here are actually just a minor annoiance for a few minutes, while they install it on their little Windows box at home. I can't even begin to say how ****ed-off it gets me, when I think about all the work it took a team of 13 people to implement this update in a corporate environment, and people here make IT guys the big idiots for creating a major fuss about the issue, while they had no problem installing it on their machine at home....

Odom said,
LOL how true...

We were up for weeks trying to get our servers and client machines patched on time and only finished last weekend.

It still amazes me how many people who read and post on Neowin think that all the MS news about updates and patches posted here are actually just a minor annoiance for a few minutes, while they install it on their little Windows box at home. I can't even begin to say how ****ed-off it gets me, when I think about all the work it took a team of 13 people to implement this update in a corporate environment, and people here make IT guys the big idiots for creating a major fuss about the issue, while they had no problem installing it on their machine at home....

haha, we call those people job security

People used to change clocks manually. Decades ago, I seem to remember there were these clocks you actually had to wind up and turn an entire hour forward for DST.

Apparently, this new generation hasn't mastered the skill of doing **** for themselves.

Yes, well, neither did, Swatch, Camel, and lots of other major brands. Most of them you still have to adjust the time manually.

hahaha "but windows update fixed dst on my home computer"

fan friggin tastic. couple of my clients had to shell out an insane $4000 to get legal "hot fixes" for there windows 2K and server 2K systems.

updated end user system was cake. hell, even updates the server's was easy. it was going through MS's ridiculous run book on how to update exchange, mail boxes, and colanders that was just plain STUPID. black berry enterprise servers where harder then they should have been as well.

but alas. its only the most popular most sold and most used operating system in the world. who the hell am i to think they could muscle up a patch that i just have to run, instead of bill 6 hours per client for, making ME look like the ass.

I don't understand people shelling out money for the Win2K patches. First of all - don't complain about it, those products are 8+ years old. Sorry, they can't be supported forever. And the price is going to be high when only 5 people are purchasing the damn patch.

Second, why bother? Just change the damn clocks yourselves.

Brandon Live said,
I don't understand people shelling out money for the Win2K patches. First of all - don't complain about it, those products are 8+ years old. Sorry, they can't be supported forever. And the price is going to be high when only 5 people are purchasing the damn patch.

Second, why bother? Just change the damn clocks yourselves.

im not even going to respond to your comment specifically, simply because it lacks anything that could be considered a rational thought.


This whole situation was lame. Installing the patch was no big issue for a single machine. The fact that the change was a problem at all is an issue.

Ah well.

Would everyone who doesn't work in IT in some respect (as in corporate networks using MS Server OS's) kindly keep it to themselves if they feel the need to spout off about something they know nothing about? We're not talking about your home computer here.

The only patch that was kind of a pain to install was the one for my phone. I can see some novices having issues with that. But the rest... come on...

Um, when I started my machine this morning, it had adjusted to DST. I don't see how this has anything to do with MS. They issued a critical update via Windows Update. When they originally had Windows automatically update to DST, there was a different time set. Now the government has decided to play with time again. I don't think Bill Gates or Steve Balmer called Washington and told them to move DST up a month.

...because most businesses of any real size do not use MS's Windows Update service. They will use WSUS to push approved patches, but those take time to test. A committee of 7 people at the company I work for choose what patches are relevant to the business and announce those for testing. It takes 2 full days to get them all tested and ready to be pushed out to users. Then all production systems have to be patched manually. We are considered a mid sized company $5/billion+ annually and have over 30 systems that all have to be tested.

The problem that I/we have had with MS over this deal is that the patches don't fix everything and they were slow to get released. They never really came up with an Exchange/Outlook fix, and it shows how poorly some of their software in engineered that they put in DST as fixed dates and did not put in any flexibility.

oh noes. All* the clocks will be an hour out in ONE COUNTRY.


THE WORLD IS DOOOOOMEED!!!!!!1oneoeneoneeleventyone


*Not actually that many.

This might only be a US change, but if you're a global company and you have networks connected to the US, this change could messup things all over.

Try thinking a little more out of the box. If this only affects one country, why do you think the whole world is updating? Anyone that deals with the US will face this problem.
Just like GP007, we're also a global company and are having a hell of a time trying to test the update in time and get all the servers up-to-date.

M2Ys4U said,
the clocks will be an hour out in ONE COUNTRY

That affects a LOT of systems (in the US and elsewhere). Everything from timed safes/doors, elevators, medical equipment, investment/insurance/banking systems, transportation, etc., etc. Basically everything that we had to deal with 7+ years ago during the Y2K issues, plus it will be ongoing as they shift the DST dates around even more. So actually, it will affect VERY many.