Microsoft DST Patch is a POS. * BE CAREFUL!!!*

We've begun running windows updates on my company machines so that XP can handle the daylight savings time changes. After installing the initial updates on the machines, everyone's calendar items started to jump forward an hour. Meetings that were scheuled for 8:30 appeared as 9:30. All day events (12am-12am) were rescheduled as two day events (1am-1am) and people were freaking out because of missed calls and appointments.

So, we tried to fix it by running the exchange patch immediately after, rather than waiting for the weekend like we had planned. This led to major corruptions of calendar entries and in some cases, entire profiles needed to be removed from the mailbox stores, then recreated, and all data imported from a backup .pst.

As for Microsoft's support on the issue, they've been absolutely no help, and just told us that it may be wiser to fix appointments manually rather than use their tool.

So, to all system admins out there

*BE CAREFUL*

Rasobasi420

I had absolutely zero troubles with the patch. There have been no missed appointments and no missed calls. The Exchange Server updated correctly, The 2003 Server updated correctly, The 2000 server updated correctly. Our Unix serve updated correctly. The registry backup was easy and the registry over-write was quick. The problems OP might have occurred are not on his end but the clients' ends. Today we learned that most companies did not pay attention to the updates. Yesterday I had to change about 50 PC's due to the fact that an intern built and image of the machines and turned "Automatically Adjust for DST" off. Other than that, the patch was simple. It changed 5 Hexidecimal identifiers which stated when DST starts and ends. Sorry if OP had any troubles...check your clients out...maybe you did everything correctly and they were the incorrect party.

the problem is with the RIM blackberries. The blackberry patch was almost never applied successfully, and the calendar items in the blackberries were propagating to the desktops with inaccurate times.

Still dealing with it.