Exch2003/BES 4.1.7 -> Exch2010/BES 5.0.2
 

So currently we are amidst moving from Exch2003/BES 4.1.7 -> Exch2010/BES 5.0.2. Both Exchange 2010 and BES 5.0.2 are up and running, but not really in use yet.

I just setup the new BES server and the old one is still handling all blackberry email functions. Everything seems to be ok, but we ran into an issue when I migrated an initial test user. The migration using the transporter tool worked flawlessly. However, mail does not flow on the new device. Why? Well, basically here is what we encountered.

BES 4.1.7's blackberry admin account is different then the new installation's admin account. Therefore, I needed to go into exchange system manager for 2003 and give the new Bes service account permissions to exchange 2003, which I did. However, mail is still not flowing properly, and I assume it is because of MAPI CDO versions not matching. I installed the latest one on the new server since it would be connecting to exchange 2010 eventually, but since it doesn't match that of the 2003 exchange server, i assume that is why we are experiencing issues. Do I need to uninstall the mapicdo from the new BES server and install the same one as the old 2003 server, or could I safely just install the new one on the old exchange 2003 server?

Thoughts? We were trying to avoid downtime, but I am not sure a 100% seamless cut over is going to be possible when moving from both old BES and Exchange versions.

Thanks in advance.

-Rob

no one?

what version CDO did you use?

did you run IEMSTest.exe tool on the new BES server for the moved user account?

CDO on the new BES is the latest, 6.5.8190.0

CDO on exchange 2003 server and the old BES is 6.5.7654.12

I have not run IEMSTest.exe on the moved user account. I moved it back, but I'll run it the next time I try to move it.

Is it going to break anything if I install the latest CDO on the exchange 2003 and old BES servers?

Dont install it on the exchange server, that can break things.

It should work on the OLD bes server, but you wont be gaining anything by doing it. I still use ESM on mine with out issue.

I setup a blackberry on an account we had migrated to exchange 2010 already. I can send to the account/blackberry fine. However, I can't send from the exch2010 enabled blackberry to an exchange2003 account, but I can send from OWA to an exch2003 mail account. Getting the following bounceback when trying to send from the blackberry to exch2003:

Diagnostic information for administrators:
Generating server: test.domain.com

#< #5.2.1> #SMTP#

521 means <domain> does not accept mail, do you have the correct send as permissions?

I can send from exch2010 to another exch2010 account, so I assume I do. The problem is occuring when trying to send from an exch2010 blackberry to an exch2003 email account.

The new BES 5.0.2 is using a new service account that differs from the one the original BES was installed with, but I thought we got the permissions sorted out for the new account on exch2003 Friday. Maybe not.

Should I just run the setsendaspermission.exe on the 4.1.7 BES but reference the new service account to make sure it has the appropriate permissions for the old servers?

Update on our blackberry issue with not being able to send from Exch2010 to 2003...

Apparently it was only one information store having the problem. Everything works fine except for one mailbox store. We moved my account today to a new store and mail flow is 100% functional. Moving all of the mailboxes in this store isn't really an option, but more of a last resort. Aside going back through the permissions (that look to be correct as it is), any other ideas? Other stores in the same storage group are completely fine and recieve/send mail from 2010 blackberry devices with no problems.

Doesn't really make sense, but at least we now know its an issue specific to a single mailbox store.

have you tried stopping and starting the store?

Any exchange issues in the logs?

several times, and nothing of note.

it's telling me that besadmin doesn't have send as permissions for any users still on 2003. I've gone on and verified that send as is checked for these users, yet IEMStest.exe when run from the 5.0 BES still says besadmin doesn't have the send as for that user.

I can manually set it using the send as permission tool from the old 4.1.7 BES, but i'd prefer not to have to do that to every single user before i transport them. Is there any way I can re-assign that permission for BESadmin for ALL users?