THE OFFICIAL BLOG OF THE SBS "DIVA"

Well I'm not quite as spiteful as Mr. Peeved is about the DST patches but yeah...the DST patches have been an utter and total disaster.  I've given up even caring to give feedback on the fact that when you go to the DST patch wizard, tell them you run a SBS box that it then asks if you run standard or Enterprise Exchange server... while yes it's technically possible to have an additional Exchange Server in a SBS enviornment, asking a DIY admin what version of Exchange he or she has is a bit... well.. dumb. 

Our latest is that the new Exchange rebasing tool needs to be run before 926666 in run on Exchange 2003

* Do not install KB926666 patch on Exchange servers prior to rebase.

Install the patch after the rebase.  Installing before the rebase will

cause OWA recurring meetings not to be updated.  If you already have

KB926666 installed on the Exchange servers, uninstall it and (re)run the

Exchange tool.

...uh..
Yes?
What?

You are like me and already installed that? 

Oh yes now you need to uninstall it and rerun it again.  Like how about like not, okay?

NOTE:  If you have already applied the patch, run the rebasing tool.

and are satisfied with the results there is no need to agonize over

whether to remove the CDO patch and re-base mailboxes for OWA users.

Proceed onward, guide your users, and prepare your help desk to handle

calls.

I vote for .. we're not patching anything more until March 12. I've done the servers, the workstations, the Exchange, the sharepoint, the phones.  We're just going to "deal" with whatever happens on the 12th.  I'm not running any more rebasing tools.

But for those of you into punishment..... for the record....

There's another Outlook rebasing tool expected

There's a CRM DST patch tool coming out

and.. there's another phone patch for some of you

Oh and Newfoundland folks are just going to have to deal with the fact that I'm not patching my server for their time zone.

To all those Microsoft employees on the support side and the bloggers that are doing their darnest to get us the information, thank you very much.  Your tireless dedication to this task is commendable.  This DST issue isn't your fault I know.  But it just seems like this could have been planned a little bit better is all.