hyunelan2
03-12-2007, 02:08 PM
Normally, I don't complain about changing the clocks. Yeah, it sucks that it's dark in the morning, but that will fix itself as the weeks go by. What is killing me now, is the goddamned 2007DST changes / updates for computers.
I thought I had everything set. All my servers were patched. Workstations were ready. I patched Exchange Server (email and calendar server for my organization) and was ready for the big clock jump. I came into work this morning: success! Everyone's clocks on their computers were correct, no system time conflicts. Good to go... or so I thought.
Opened my calendar... hmm. Thinks appear to be one hour later than they should be. Pull out my blackberry (work issued & synchronized)... hmm... one hour earlier than things should be (so 2 hours different from the computer). That's where the fun started about 4 hours ago. So, I re-run the TZMOVE application from microsoft on my desktop. Voila, appointments are good... or so it appears. Now things are 2 hours earlier on my blackberry. Appointments I had made with others are all F'ed up now too. I made the same appointment (for 1:30) 3x and got 3 different results.
I side-stepped the blackberry problem by changing my timezone. Then I installed the blackberry server patch (that one was forgotten by me, whoops). The nice thing about that one is, that it may take up to 24 hours to take effect. Then the device must be reset. So, that's a nice quick fix (not)... a-holes - I hate Research in Motion, their system sucks.
What a friggin nightmare. Luckily, problems will all go away in 3 weeks - when the old DST takes effect. However, if I don't get all this straigtened out before then, I might not be working here then (j/k, but people will still be pissed).
The thing that makes me angry - these DST changes were planned since 2005. Almost all of the software I'm running has been designed after 2005, yet still has the old DST code in it, requiring these endless patches and updates. This is lame.
I thought I had everything set. All my servers were patched. Workstations were ready. I patched Exchange Server (email and calendar server for my organization) and was ready for the big clock jump. I came into work this morning: success! Everyone's clocks on their computers were correct, no system time conflicts. Good to go... or so I thought.
Opened my calendar... hmm. Thinks appear to be one hour later than they should be. Pull out my blackberry (work issued & synchronized)... hmm... one hour earlier than things should be (so 2 hours different from the computer). That's where the fun started about 4 hours ago. So, I re-run the TZMOVE application from microsoft on my desktop. Voila, appointments are good... or so it appears. Now things are 2 hours earlier on my blackberry. Appointments I had made with others are all F'ed up now too. I made the same appointment (for 1:30) 3x and got 3 different results.
I side-stepped the blackberry problem by changing my timezone. Then I installed the blackberry server patch (that one was forgotten by me, whoops). The nice thing about that one is, that it may take up to 24 hours to take effect. Then the device must be reset. So, that's a nice quick fix (not)... a-holes - I hate Research in Motion, their system sucks.
What a friggin nightmare. Luckily, problems will all go away in 3 weeks - when the old DST takes effect. However, if I don't get all this straigtened out before then, I might not be working here then (j/k, but people will still be pissed).
The thing that makes me angry - these DST changes were planned since 2005. Almost all of the software I'm running has been designed after 2005, yet still has the old DST code in it, requiring these endless patches and updates. This is lame.