ISAslot
Platinum Member
- Jan 22, 2001
- 2,891
- 108
- 106
Originally posted by: Milkman95
We are having a few(5 out of 100+) PCs (XP) that have the patch installed, but didn't switch over. Manual adjustments are getting reset to an hour back every so often so they have the wrong time again. Still trying to figure out whats causing that.
Phone system didn't switch automatically (although was patched by vendor).
Exchange seems to have randomly picked who's calenders would be correct... Although that might have something to do with our 5.5 server still in the organization.
Other than those annoyances... nothing blew up.
If anyone has suggestions on the stubborn time changing XP boxes let me know!
http://blogs.technet.com/dst2007/archiv...s-2003-windows-xp-or-windows-2000.aspx
Demon-Xanth
Lifer
- Feb 15, 2000
- 20,551
- 2
- 81
So far so good but I haven't gone back to the office yet to see how the rest of my clients are doing. The one I'm currently at is running smoothly.
ultimatebob
Lifer
- Jul 1, 2001
- 25,134
- 2,450
- 126
Yeah, you gotta install the patch. NTP (Network Time Protocol) returns UTC time to your computer, which your computer converts to your time zone using the (wrong if not patched) time zone rules on your computer. So, if you manually change the clock by moving it forward, NTP will "correct" it and change it back for you the next time it runs.
ultimatebob
Lifer
- Jul 1, 2001
- 25,134
- 2,450
- 126
I used an earlier version of the Intelliadmin patch, which had a bug and didn't install right.
Microsoft isn't alone with this, though... Some of RedHat's tzdata updates for daylight saving time didn't work on some systems as well.
Originally posted by: ISAslot
Originally posted by: Milkman95
We are having a few(5 out of 100+) PCs (XP) that have the patch installed, but didn't switch over. Manual adjustments are getting reset to an hour back every so often so they have the wrong time again. Still trying to figure out whats causing that.
Phone system didn't switch automatically (although was patched by vendor).
Exchange seems to have randomly picked who's calenders would be correct... Although that might have something to do with our 5.5 server still in the organization.
Other than those annoyances... nothing blew up.
If anyone has suggestions on the stubborn time changing XP boxes let me know!
http://blogs.technet.com/dst2007/archiv...s-2003-windows-xp-or-windows-2000.aspx
Woot!
Thanks!
so...when you all woke up this morning, was it still dark?
it was for me so I had to turn on the lights, there goes that theory about saving more energy
anyways, to comment on the BES server and send as post...no admin should logon to their PC with domain admin rights anyways. That's the whole deal about that and yes, we had to correct that problem as well
Exchange calendars, I don't think anyone got that right because most people have complex mail infrastructures nowadays so getting this just right isn't going to happen. You have to deal with mailrelays, exchange backend servers, frontend (webmail) servers, and blackberry ent. server. Even using tzmove correctly will not fix all the problems, the best thing to do is to inform the users to recreate/modify their own entries.
only thing that was down for me was webmail and that was quickly fixed by re-registering cdo.dll file. weird that the 92666 patch didn't do this, but it makes some sense since I had to do it for the BES server.
other than that we had a major power failure at the office today so I can blame everything that's wrong on that
it was for me so I had to turn on the lights, there goes that theory about saving more energy
anyways, to comment on the BES server and send as post...no admin should logon to their PC with domain admin rights anyways. That's the whole deal about that and yes, we had to correct that problem as well
Exchange calendars, I don't think anyone got that right because most people have complex mail infrastructures nowadays so getting this just right isn't going to happen. You have to deal with mailrelays, exchange backend servers, frontend (webmail) servers, and blackberry ent. server. Even using tzmove correctly will not fix all the problems, the best thing to do is to inform the users to recreate/modify their own entries.
only thing that was down for me was webmail and that was quickly fixed by re-registering cdo.dll file. weird that the 92666 patch didn't do this, but it makes some sense since I had to do it for the BES server.
other than that we had a major power failure at the office today so I can blame everything that's wrong on that
Whats funny is only 1/8 the people have the appointment not shifted.... thats 4 people had recurring appointment remain the same while everyone else shifted correctly for the next 3 weeks...
good job for changing dst.. it cost more money than saved.
It's been pretty uneventful here. I had one guy who had for some reason removed BigFix from his computer and didn't get the push of the DST patch, so his time was off. Just had to install the DST patch and reinstall BigFix. The IT engineers predicted all hell would break loose with all the Blackberries we have here, but it really hasn't happened.
Forgot to update our phoneserver, so everyone thought we were closed for an hour this morning...oops!
Couple clients' workstation patches didn't take for whatever reason. Exchange tool seems to have worked on the couple dozen Exchange servers we updated. Not bad...keeping fingers crossed for the next couple weeks.
Boss got caught in the sendas BES situation. He was pissed all day yesterday trying to figure it out. :laugh:
Couple clients' workstation patches didn't take for whatever reason. Exchange tool seems to have worked on the couple dozen Exchange servers we updated. Not bad...keeping fingers crossed for the next couple weeks.
Boss got caught in the sendas BES situation. He was pissed all day yesterday trying to figure it out. :laugh:
Microsoft totally screwed everyone. Their exchange solutions to DST blow.
The Microsoft chat looks like sony chat when an EQ server goes down.
The Microsoft chat looks like sony chat when an EQ server goes down.
Lots of problems where I work. We use lots of Winterms, and some of the models that we use do not have a new image available for them, so the wrong DST info is coded in them screwing up the Citrix session.
Also, appointments in Outlook are all screwed up. People with recurring meetings are having all sorts of problems.
Also, appointments in Outlook are all screwed up. People with recurring meetings are having all sorts of problems.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter