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
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
THE WORLD IS DOOOOOMEED!!!!!!1oneoeneoneeleventyone
*Not actually that many.
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.
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.
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.
Only an idiot, who reads the news, then don't update
Ah well.
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.
Second, why bother? Just change the damn clocks yourselves.
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.
Apparently, this new generation hasn't mastered the skill of doing **** for themselves.
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.
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....
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
If this DST change wasn't so stupid, it'd be funny.
If this DST change wasn't so stupid, it'd be funny.
QFT
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"?
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.