Quote:
Originally Posted by jamex
Here's the environment. NT4 domain, with Exchange 5.5 has a bes server in it. Migrating to Exchange 2003 a new AD 2003 domain has been created, trusts between the 2 domains exist, and Exchange 2003 and 5.5 are talking mixed mode quite nicely.
I know that mapi.dll and possible cdo.dll need to be updated on the BES server in order to talk to Exchange 2003. However what I've read from RIM says you have to install the 2003 ESM on the BES. It already has 5.5 ESM, and of course I can't install ESM on a server thats not in the AD domain. Can I get away with leaving the old ESM on, and just updating the mapi.dll or do I have to move the BES server into the AD domain (which is going to involve much more approval process)?
Any advice would be greatly appreciated. Cheers.
|
It isn't just the mapi32.dll you need to update. You also need to update the emsmdb32.dll, the emsabp32.dll and the cdo.dll among others. All of these come with ESM, and hence why it is so important to install when it comes to BES.
I believe you will need to add the BES to the new AD domain you will be setting up. BES needs to do lookups to the global catalog server through Exchange. If it is not a member server within AD, I definitely see issues with locating the Exchange 2003 based mailboxes and resolving the recipients primary SMTP addresses.
Would definitely appreciate someone correcting me if I am mistaken, though.