I meant to blog this yesterday but I was busy with my MiniCooper group last night. This morning I’m eating a bagel and creme cheese with tea on an Amtrak heading towards Sacramento and the next stop on the SMBMVPtour (see www.smbmvptour.com ) .
By now hopefully you’ve already read these two blog posts on the SBSblog (http://blogs.technet.com/sbs ) I’m about to blog about, but if you haven’t, go do so now….
Read them? Okay now I’ll flesh them out a bit more. This first one is about how there’s now an update for the migration tool. You know how I jump up and down and tell you guys never ever ever ever say yes to updates during the install because not only does it add time to your migration, but it adds potential for change and patches and this is the time you want to limit change and patching? Okay so there’s one time of the migration process I DO want you to install updates and it’s right here at this point of the migration tool. When you install the tool on your sbs 2003 there’s a box there to say yes to go check for updates. PLEASE PLEASE PLEASE get updates on this ONE spot. Because they’ve added new rules to ensure that Exchange won’t barf as much.
Why does Exchange barf?
This update adds the following rule to check whether the Allow inheritable permissions option is enabled for the mailbox store and for the public folder in Active Directory:
I’ve seen quite a few Exchange barfages due to this one issue.
When Exchange barfs while one can manually install, end up with an eval version of Exchange and then find the kb to make it not eval, I’m still more comfy in telling folks to do a system state restore on the sbs 2003 and start the migration process over.
Also be aware of a known issue you might hit Sub Rule 5 from the update (KB 2578426) if your _MSDCS zone is not a forward lookup zone delegated from your primary domain zone as documented in the blog:
Bottom line, you want updates right here at this one spot.