UPDATE: We have now released the hotfix that corrects this issue for Exchange 2003 SP2. The article is: 930241 The Exchange 2003 database does not mount, and event IDs 9518 and 9519 are logge...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hello. I have patched the OS for DST on all of our W2k3 Exch2k3 machines. One FE v7638.20, 3 BE 2x7650.28, 2x7638.20. It’s a mess I know. About 300 Win client OSs have been patched also. Didn’t realize everything needed to happen in the same time frame when I started this thing, was just following the order I thought was correct. Server OS, client OS, Exchange patch, mailbox tool.
So now users are seeing incorrect times on their appointments.
Should I go ahead and run the kb926666, then the just released kb930241 if my stores don’t mount, and then run the exchange tool (Msextmzcfg.exe) on all mailboxes, and if so just for just recurring appointments?
Or leave as is and let the damage be done?
So now users are seeing incorrect times on their appointments.
Should I go ahead and run the kb926666, then the just released kb930241 if my stores don’t mount, and then run the exchange tool (Msextmzcfg.exe) on all mailboxes, and if so just for just recurring appointments?
Or leave as is and let the damage be done?