[Sparkomatic]

Hello all,

Hoping for a little help here. Our company, which has a BES and Sm. Bus. Edition Exchange has just been acquired by a company with no BES and full Exchange server.

The plan is to abandon our Sm. Bus. Exchange and run off theirs and keep the BES. We want to start transitioning our users to their Exchange but the BES is going to stop working since it's tied to us.

Is there a way to tie it to both while we migrate to their Exchange? As I'm typing this, I'm kinda thinking there isn't.

I've got four users that I'm concerned the most about and thinking that I'll have to migrate them all at once, re-provision the BES (once I figure out how to do that), and then wipe and setup each BB again?

[knottyrope]

New domain means wipe and EA on new setup.

[crhoden]

Ours is somewhat similar...

We have set up and are using a new domain which will eventually entirely replace the old one. All of our users except for 5 or 6 (who didnt mind waiting until I got BB1 server moved to the new domain) have already been moved to BB2 server that's already working in the new domain.

All I'm trying to do, if possible, is point the BB1 server (currently empty of users) to the new domain's exchange server, who's BB service account has the same login/password as BB1's (did that intentionally so we wouldnt need to modify that in BB1 when it came time to do this).

Theoretically, it would appear that I need to have the server that BB1 is installed on join the new domain, reboot of course, modify BB1's mapi to point to the new domain's exchange server then reboot the BB1 server. Does that sound to you like it will work and/or is there more to it...?

Any input would be very much appreciated.
Thank you.