I had spotted Bruce’s blog the other day but he pinged me tonight and he has a really good “from the trenches view” of the migration process.
First look for end users: http://www.bruceb.com/news/2008_12_01_archive.html#5511184836947346448
First look at admin console: http://www.bruceb.com/news/2008_12_01_archive.html#5060497621166402902
SSL certificates: http://www.bruceb.com/news/2008_12_01_archive.html#1262353038403246306
Details on glitches during migration: http://www.bruceb.com/news/2008_12_01_archive.html#300298468838479136
There's a couple of things I'm going to follow up on but some things in the migration process I wanted to point out:
"I expected the mailbox migration to be slow but was still surprised. The Exchange 2003 mailbox store was about 25Gb after I pruned and archived
as much as I could from the biggest mailboxes. The mailbox move took just about ten hours."
During a migration is a good time to tell a white lie about the Exchange server's ability to retain data. Say that the migration process
only will migrate a year's worth of email and archive off the rest if the really really need those old emails. Okay, okay so that's harsh and being too
sneaky but anything you can do to get people to clean out their mailboxes so that the migration time will be faster will be better for them.
I'm also going to recommend that Bruce see http://blogs.technet.com/sbs/archive/2008/08/26/known-post-installation-event-errors-in-sbs-2008-and-how-to-resolve-them.aspx
as I think that will fix his OneCare issue. The server does not have the security center running and thus it's normal to not have the server report in
But a good read of some of the potential stuff you might see. Thanks Bruce!