[ashworth]

I just got Exchange 2007 running in my test lab and I just created my service account BESAdmin.

I gave the service account the Send As permission within AD applied onto the users objects.

I then give my service account a mailbox in Exchange 2007.

I was able to give the service account Exchange View only Admin with the following command in the power shell:

add-exchangeadministrator BESAdmin -role ViewOnlyAdmin

I was then able to give it Send As, Receive As and Administer Information Store with the following command in the power shell:

Get-mailboxserver JED-DC | add-adpermission –user BESAdmin -accessrights GenericRead, GenericWrite -extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

Where JED-DC is the Exchange/DC server.

I will be installing the 4.1.2 BES tomorrow night. I will update the post when I get it setup.

Ok I got my BES Installed and I added my frist user.

EA'ed the users -> No issues

Sending a message from the Handheld:

[40700] (02/01 00:12:26.428):{0x4A0} {test@myDomain.com} Receiving packet from device, size=131, TransactionId=720661315, Tag=30, content type=CMIME, cmd=0x3
[40292] (02/01 00:12:26.509):{0x4A0} {test@myDomain.com} Email message sent for device, Tag=30
[40279] (02/01 00:12:26.509):{0x4A0} {test@myDomain.com} SubmitToRelaySendQ, Tag=30
[40000] (02/01 00:12:26.509):{0x1164} [BIPP] Send status DATA_ACCEPTED, Tag=30

Success

Mail coming into the handheld:
[30081] (02/01 00:12:28.261):{0x4A0} {test@myDomain.com} Sending message to device, size=166, EntryId=79, RefId=-806894533, TransactionId=-977177364, Tag=34
[30097] (02/01 00:12:28.422):{0x4A0} {test@myDomain.com} Message has been delivered to device, Tag=34, EntryId=79

It looks like mail flow is working both ways.

I will be doing some more testing later.

[bradhs]

Thanks Ashworth! I was waiting for someone to try that out.

[Dookie]

This is cool post. Thanks for that!

[shllshck]

It took me about a week and a half to finally resolve our Exchange 2007 and BES issues. Thanks ashworth. Your tip did the trick.

[RipThorn]

Hello

How exactly did you install the BES 4.1.2 with Exchange 2007? BES 4.1.2 is not compatible with exchange 2007. Unless you've got the patch that rim is about to release soon

Thank you

[rkneeshaw]

Its not "officially" compatible, it does work fine. In fact we're still using BES 4.0.5 during our Exchange 2007 migration and its working fine.

The trick is to install the Exchange MAPI Client 1.2.1 on the BES server instead of installing System Manager (usually called the admin tools for Exchange 2000 or 2003). In addition to the steps in the original post.

[Bikejunkie]

Ashworth,

This is great! One question, when granting the Send As rights to user objects, I am assuming you did this through a delegation in Active Directory Users and Computers, is that right? Let me know if it was done another way.

Thanks!

[RipThorn]

Hello Again
I still get an error when trying to open BES Manager telling me Failed to open default message store, result=0x8004011d

I made the changes to my besadmin account. DO i need to wait 15 minutes?

thank you

[BBAdmin]

Just as a point of interest RIM have now confirmed that 4.1.3 will work with Exchange but support is on a case by cases basis, 4.1.4 will offer full technical support and 100% compatibility with Ex 2K7

We know what works because Ashworth has it all humming, but I know some of you like to know the official support line from RIM!!!

[RipThorn]

I just wanted to know if he managed to get MAPI profile working for bes account when you log in to BES manager. I got my exchange 2007 up and running fine. I can add remove users. The only broken thing is this MAPI profile creation. I can"t seem to find any info about that.

thank you

[carrmic]

I'm curious if anyone has tried this with their existing enterprise server. In other words, I want to deploy my new Exchange 2007 server move a mailbox and continue to use the same Blackberry server to service that mailbox. It seems that the few attempts so far have been with a new BES install.

Anyone had any luck using the Exchange 2007 MAPI / CDO package installed on their existing BES server?

[TChachra]

I have tried the new MAPI on our Bes 4.1.3 and it works perfectly without the exchange management tools installed.

I have introduced a Exchange 2007 server into our organization, moved my mailbox to it, and continued to check BES. Bes picks up the location of my mailbox but cannot open the mailbox...it gets Mapi errors.

I tried ASHWORTH's security settings above and it just does not work at all.

My feeling is that the security being used is from the Exchange 2003 org via the connector and it wont allow BesAdmin to open the mailbox.....

Thats where I am for now...

[carrmic]

Thanks for the feedback. It seems like this upgrade could be a bit more problematic than I was hoping. I just purchased a one-time upgrade to get our Blackberry server to 4.1.3 from 4.0.6 but we currently don't have T-Support. That would make getting these type of issues solved somewhat expensive on a case by case basis.

[TChachra]

Lately I am wondering if tsupport is worth it... After BBF who needs anything else.

[CaptMorgan]

Just so you guys know. We are in the process of moving users to our 2007 servers from exchange 2003. We uninstalled exchange 2003 system manager from the BES and installed the microsft mapi32 and cdo install (sorry dont have the link). Once we did this the new dll's (version 6.5.7888) we had created an issue with our 2003 exchange users. They only had one way synchs with their calender. I spent a couple days troubleshooting with RIM and they eventually said we need to reinstall exchange system manager 2003 and the older DLL's. Well this didn't help our 2007 users because it would break them totally. So instead we just told our 2003 users to wait until they were moved to the 2007 servers which calender synch worked properly on.

We are running 4.1.3 BTW.

Also, no other issues have come up from our 2007 users... BB related anyways LOL.

[TChachra]

Capt.Morgan

We have one exch2003 server and one exch2007 server in the same domain.
I have one bes server which uses the besadmin account on our exchange2003 server.

I installed version 1.21 that you mention...for the new cdo.

However, my beserver is not able to open mailboxes on the 2007 side...comes up with a mapi error. I have done the security changes as recommended in the beginning of this thread.

HELP!

[CaptMorgan]

Tchachra,
What version of BES are you using?
Double check that your cdo.dll and mapi32.dll are version 6.5.7888.
You might want to try registering the cdo.dll if you havent already. (regsvr32 C:\windows\system32\cdo.dll). That about all i can think of right now.

[srm22]

I had the same issue. I grabbed the cdo from my exchange 2003 server and registered it in the system32 directory and the calendar seems to be syncing properly now.

[mattf]

I ran these commands in the shell and was able to get the BES talking with Exchange:


add-exchangeadministrator “BESAdmin” –role ViewOnlyAdmin (then press enter)
2. get-mailboxserver (Exchange Server Name) | add-adpermission –user “BESAdmin” –accessrights GenericRead –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin (then press enter)

Also, I did NOT uninstall System Manager 2003, or install a new MAPI.

I upgraded from 4.1 to 4.1.3, transitioned from Exchanged 2003 to 2007 and everything works great.

[karupspc]

I haven't been as lucky as you guys. A fresh installation of Windows/Exchange 2007 and BES 4.1.3. I followed the instructions on how to give the Besadmin account proper permissions but when launching Blackberry Manager, I get the error message that the Mapi profile for Blackberry Manager failed to open.

I have the Mapi Client 1.2.1 installed and configured it for the Besadmin account but no luck.