[vincez]

Hi all,

I am currently facing an issue with my entreprise.
We are currently in the midst of migraition from Exchange 5.5 to E2K3. We are currently using Quest tools for migration.
We have a total of approx 3000 users and have about 500+ BES users.
We are currently on BES 4.0. Here come the issue.
We cant do a one time migration for user mailboxes due to the large number of mailboxes involved.
Is there a workaround on the BES 4.0 server to allow the mapi connection to 2 diifferent exchange servers namely Exchange 5.5 and Exchange 2K3 at teh same time to ensure undisrupted usage for the users.
Can anyone help
Thanks in advanced

[dev]

Did you set up ADC between the Exchange 5.5 and Exchange 2003?
Exchange 5.5 has it's own directory service and Exchange 2003 uses AD. I'm assuming the BES service acct is located on the Exchange 5.5, together with the BES users. There isn't much you can do on the BES server, since it depends on where the BES service acct mailbox is located. If ADC isn't setup then you'll not be able "see" the Exchange 2003 users (new BES users).

[exiled]

We are in the midst of a migration too. As long as you have ADC up it shouldnt matter, what side the bes service account is on. Ours was on 5.5 in the begining, now its on 2003.

One thing i will state though is after you migrate boxes with bes accounts, run the dbclean util.

[T-Roy]

When running ADC and using the Move Mailbox utility built into Exchange it should not be necessary to run dbclean. If your running some 3rd party app to move the mailboxes you might.

[anna]

We are having a similar issue but we will migrate to a different domain. The BES user already registered with the new mail address. But the exchnage 5.5 is still in the old domain and the Exchange 2003 will be installed in a new domain.

Is it possible that the BES 4.0.3.7 server works with exchange 5.5 and 2003 users at the same time with 2 different domains?

Or do we need to install another BES server for the new exchange 2003 domain?