Post Feed
Comment Feed

About Me

My MP3 Player

Coldplay - X&Y Nine Inch Nails - Ghosts I Harry Potter and the Order of the Phoenix - (audio book) Tool - 10,000 Days

New Comments

2017 Archives

July All Archives...

Daylight Sucking Time

Sunday, March 11th, 2007

Daylight savings this year has been a major pain in my ass. Not just because the dates changed from April 1 to March 11 but because Microsoft really didn't handle the change very well. I've known about the change for a pretty long time and I assumed that Microsoft would release patches via windows update way in advance since they did know about it back in 2005. Not only did they not release updates way in advance, they only released them for the current versions of windows (XP and Server 2003). What about windows 2000 you ask? Well you can purchase an update from MS for $4000 (!!) or follow an MS knowledge base article that tells you how to create a couple scripts to patch your system. So if they released an article that tells you exactly how to fix it (which didn't work exactly), why couldn't they just create an update for it? Because they didn't consider this a "critical update."

The workstation updates weren't that bad, but some of the server updates were kind of a pain. We use Exchange server at work for our groupware, and it was a bit more complicated to patch. There was an update for the Server OS, there was an update for Exchange itself, and there was a tool to fix everyone's calendar items that fall in the change period (between the old and new DST times). Then we also have Blackberries to add to the mix. So each Blackberry device needed an update, the Blackberry Enterprise Server (which I'm running on 2000 Server) needed as OS update, a patch for the send-as permissions, the exchange update and probably something else I'm forgetting about. Confused yet? I didn't mention that all this stuff has to happen in a certain order and that order is different depending on who you're asking. MS had one order and Research In Motion (the Blackberry company) had a different order and some steps had prerequisites such as having to run from some third computer (a workstation) with only Office 2003 or 2007 installed (we use Office 2002 of course).

I read as much as I could about this and waited as long as I could to see what problems people had, but since the time changed this morning I guess I've either done it or not. We'll see how many people complain Monday morning if anything is screwed up.

Comments (8) Subscribe

#1 - Mar 11, 2007 at 12:05 PM
I hear your pain. On friday night our town IT guy had to come over and insert his flash drive into our computers that don't connect to the internet and update them with a patch. (Our computers on the desk run..what else...Win 2000 Pro.)And then he also had to do every computer in our police cars. Then the guy from the radio company came out yesterday and had to do the system that handles our phones and radios. Everything seems to be on time here.
#2 - Mar 12, 2007 at 4:58 AM
One of the best pieces of advice I've seen from Microsoft recently is to include the meeting time in the subject for the next 3 weeks. That way even if outlook puts it at the wrong time people have a chance of noticing that the two times don't match.
#3 - Mar 12, 2007 at 4:59 AM
That last comment was from me. By the way, are the captcha numbers supposed to be showing up as the background of the comments box? That feels new to me but I could be crazy. Eitherway, it's hard to read the numbers after you've typed your comment.
#4 - Mar 12, 2007 at 6:02 AM
That is pretty good advice. I still think they should have released patches a long time ago. I have some linux servers at work that have been installed and running for well over a year and they have the right dst dates with no update necessary.

As for the captcha, yes I moved it to the textbox background. I had never seen it done that way before and thought it might cool. I tried to make the script generate it so that you could still read it while leaving the text you write more dominant. Do you think it would be better to put the "enter the numbers" box above the comment box? That way you wouldn't have to look for the numbers after you already wrote your spiel.
#5 - Mar 13, 2007 at 8:56 AM
I am having problems with the numbers in the comment box also. Sometimes it is hard to read. I have gotten into the habit of typing them into the box below before writing my spiel.
#6 - Mar 13, 2007 at 1:46 PM
our new IT guy is the CFO's son and has never touched a computer apparently in his life (he was a Burger King manager before this) and he has broken every computer he's touched so far.

anyway, it took him like, 6 hours last week to put the daylight savings time patch on my computer and i am still an hour behind. i like to think he's really incompetent, though, and it's not the fault of Microsoft.
#7 - Mar 13, 2007 at 4:48 PM
Cheryl: Sometimes the numbers are hard to read, maybe I'll tweak the program to make it contrast most..

Betsy: I love hearing about completely incompetent IT guys. It should take all of about 30 seconds to update a single computer. If you have the rights, double click on the clock in the tray, hit the "time zone" tab and make sure the "Automatically adjust clock for daylight saving changes" checkbox is checked. I found a couple computers this week that were missing that.
#8 - Mar 14, 2007 at 9:45 AM
My old archenemy the palm pilot was bugging me today. All but one of our administrators have blackberries, but this one is still using a Sony Clie. There is no update for it. I got a call (like i do at least 2x a week) about it not syncing, but I couldn't get it to sync either. Finally I had to manually set the date an hour ahead and it synced just fine. I'll have to remember that the week of April 1 when it stops syncing because it updates itself for the old dst date.

Make a comment!

Numbers from below


Email Address

Website URL

Remember me