BES during a 2003 to 2007 migration 1

[ShackDaddy]

So what's the experience like with BES? It's existed during migrations I've done and I've never noticed it having a problem, but I'm getting involved with a new project in which the local sysadmins are saying that there are going to be all sorts of issues, having read about them.

Since BES essentially makes a MAPI connection to the Exchange server when it sends, if I have both E2003 and E2007 servers and I'm moving mailboxes between them, what sort of BES-side disruption should I be expecting? Since the BESAdmin permissions are granted on the org level, there shouldn't be an issue there....

Anything else?

Dave Shackelford
ThirdTier.net

 

[Zelandakh]

Hey Dave,
I've heard lots of people say that they had troubles where the devices stopped working after the migration to 2007 of the user mailbox.

These PS scripts may resolve this issue:

get-mailboxserver Exchange2007 | add-exchangeadministrator BES_Admin –role ViewOnlyAdmin

get-mailboxserver Exchange2007 | add-adpermission –user BES_Admin –accessrights ExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

get-mailboxserver Exchange2007 | add-adpermission -user BES_Admin -accessrights GenericRead, GenericWrite -extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

Certainly it worked for me anyway...

 

[Davetoo]

Aside from the rights, I believe you also have to stop and restart the BES services after the mailbox is moved to 2007.

I'm migrating from 2000 to 2007 with a BES and that's the only thing I've run into so far.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!

 

[Zelandakh]

That would make sense - it is a MAPI client and would still be hooked to the old server.