Install BES 4.1.3 or higher in an Exchange 2007 Environment
By Gary Cutri (BlackBerry Forums - Asia Pacific)
Version 1.0

Note: In an Exchange 2007 environment BlackBerry Enterprise Server cannot be installed on the mail server as the BES software is not 64BIT compatible.

1. On the server you have selected to load BlackBerry Enterprise Server download and install “Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1” which is available from the Microsoft Download site (a.k.a ExchangeMapiCdo.EXE). This will install the CDO and MAPI DLLs which are no longer available in Exchange 2007. This replaces the previous requirement to have Exchange System Manager installed as in Exchange 2000 or 2003 environments. The current download link is as follows:
Download details: Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

2. Log onto your Exchange Server using an account which has permissions to create an account. Open the Exchange Management Console and create a service account called BESadmin.

3. From the Exchange 2007 server open the “Exchange Management Shell” which can be found in the Exchange program group. From EMS run the following two scripts to set the delegate control and required permissions:

get-mailboxserver <mail_server_name> | add-exchangeadministrator BESAdmin –role ViewOnlyAdmin

get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights GenericRead, GenericWrite, ExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

4. Open Active Directory and from the View menu select "Advanced Features". Then go to each user that will be added to the BES and open their properties, go to the security tab and add the user BESadmin and add the security permission "Send As". (This will overcome some MS patches that prevent BES sending emails). Methods are available to add BESadmin "Send As" rights to all users if required but this method ensures only the required users have permissions added.

5. Make BESadmin a local Administrator of the server where you will be installing the BES software. This is done by right mouse clicking my computer and selecting “Manage”. From Computer Management expand “Local Users & Groups” and select Groups. From Groups double click “Administrators” and add BESadmin.

6. On the BES server go to “Administrative Tools” and open "Local Security Policy" and then expand the "Local Policies" and "User Right Assignment". You need to add BESadmin to "Log on Locally" and log on as Service".

7. Log onto the server where you will be installing the BES using the BESadmin account. Extract the install files and run the install file. Normally you select "BlackBerry Enterprise Server" as the install option once prompted as most sites don't use the MDS services for custom applications (MDS is a much heavier install). Follow the prompts of the install and the server will be required to restart half way through the install. Restart the server and log back on as BESadmin and the install will continue. (Make sure the Connect Test works and the SRP ID etc is validated during the install)

8. After the install is finished open BlackBerry Manager, an error will appear about MAPI client which you can just hit OK. The MAPI setting windows will appear so just add the server name back in and select "Check Name", if it resolves just hit OK and the manager will start.

9. Within Blackberry Manager click on Blackberry Domain in the left column and then the users SERVERS tab in the centre section, select your server within this tab and view the properties below. Ensure that "SRP Status:" is Connected (This can take a few minutes the first time so refresh the screen a few times). Once your status is connected you can start adding users.

10. Within Blackberry Manager click on your server name (The blue server) in the left column and then the users TAB in the centre section, just add a user and the click on that user. You will see all the users’ properties and a drop down menu called "Service Access” and select “Set Activation Password” and set a password of “a” for example.

11. Turn on you BlackBerry device and ensure Wireless is enabled. Go into “Options/Settings” and “Time & Date” and set the correct zone and time etc. Then from the home screen go to enterprise activation and enter the users email address and enter the password that was set in step 10. Press the track wheel and select Activate. Within a minute you should get data returned which indicates the process is functioning correct.


Extra Details:

Send As Permissions
http://www.blackberryforums.com.au/f...t-message.html

Download and install the MAPI and CDO Clients that are missing when updating to Microsoft Exchange 2007
http://www.blackberryforums.com.au/f...ge-2007-a.html

Assigning permissions for the BlackBerry Enterprise Server administration account

-----

Updated 12/18/2007 - hdawg calendar one-way sync problem / fix

Thanks for the great guide Gary...
What about an existing 4.1.3 install..is it possible to get that to work with 2007?
How much different is that compared to your new install?
Or is new the preferred way to go?
thanks

In an existing environment you need to do the following:

1. Install & setup exchange 2007

2. Migrate users to your Exchange 2007 server

3. Ensure you are running BES 4.1.3 or higher

4. From the Exchange 2007 server open the “Exchange Management Shell” which can be found in the Exchange program group. From EMS run the following two scripts to set the delegate control and required permissions:

get-mailboxserver <mail_server_name> | add-exchangeadministrator BESAdmin –role ViewOnlyAdmin

get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights ExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

5. Stop all the Blackberry services and remove ESM for Exchange 2003 from your BES server. Or unregister mapi32.dll and cdo.dll if the files had just been registered manually without installing ESM.

Note: This is for standalone BES servers ONLY, do not try this on installations running on existing Exchange servers)

6. Download and install Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 on your BES server.

7. Restart your BES server.

does this mean you can't support 2003 and 2007 with the same BES server?
Confused by the "standalone" comment.

standalone = A BlackBerry server installed on its own server. As many people install BES on a mail server I needed to point out they shouldn't delete the mapi & cdo files (It was a “pointing out the obvious” comment).

Re: "does this mean you can't support 2003 and 2007 with the same BES server"

If you have Exchange Systems Manager 2003 installed on the BES server it will fully support Exchange 2003 but won't fully sync with Exchange 2007 (e.g. Calendar sync doesn't work). If you remove Exchange System Manager and install "MAPI Client and Collaboration Data Objects 1.2.1" it will fully support Exchange 2007 but will have sync issues with Exchange 2003 (e.g. Calendar sync doesn't work).

Ouch. So migrating to 2007 is an all or nothing deal....

kind of a deal breaker. Oh well. Maybe soon.

I install the BES express for my exchange 2007. After I add a new user. The status of user is always initializing. Please tell me what else should I do.
And there is no wireless in my company. Does it necessarily for BES? Thanks.

The status of "initializing" is just a default message that is displayed when a user is added to a BES. Just consider that message to mean "Ready to be activated".
So if you want to activate a user/device you have two options which are "Wireless" and "Cabled" activations.

To perform a wireless activation right mouse click the username in BlackBerry Manager and select "Set Activation Password", then set the password and select OK to continue. Then from the Blackberry handheld go to the Enterprise Activation icon (if you can’t see it go to OPTIONS>Advanced Options>Enterprise Activation) and enter the users email address and the activation password you just set on the server. Once you enter the info just press the track wheel/ball and select activate from the menu.

To perform a cabled activation just connect your Blackberry device to the Blackberry server via the supplied USB cable. Once connected open Blackberry Manager and right mouse click on the user and select "Assign Device", then select the device on the list and press OK. To view the progress of the activation on the device go to OPTIONS>Advanced Options>Enterprise Activation and you will see the % complete with details. Do not disconnect the device until you see the “Activation Complete” message.

Thanks for the great info!!!
Will give this a shot in afew weeks!!

awesome post Gary.

Great post Gary.

Question on 64-Bit stuff --
Does this apply to the installed OS only?
in other words, if I have 64bit XEON processors but install Server 2003 32 bit OS, will this work?

BES support confused me - once they told me I could install BES on my 2007 server (which doesn't work), another time they told me the processors had to be 32 bit, so now I need help..

I assign a blackberry to a user. But it comes a error message(attachment). Anyone who can help me. Thanks.

On our system we had initially Exchange 2003, then we installed Exchange 2007, and our BES install was working fine with calendar sync. Migrated users were running it fine, users staying on Exchange 2003 were fine. The BES server was running with ESM. Can you elaborate on why calendar sync was not supposed to work for Exchange 2007 users?

This issue is related to the BESadmin permissions not being set correctly.

To run Exchange 2007 it has to be installed on Microsoft 2003 Server 64-Bit. Also BES DOES NOT run on 64-Bit platforms.

The issue was caused by a variation (i.e. different file version) in the cdo.dll file.

If this is the reason, then how would you explain our system working fine?

Send a calendar invite to a BlackBerry user on the Exchange 2003 server and Exchange 2007 and tell me if they both get the invite on their handheld.

It turns out our Exchange 2003 box is shutdown as of last week. :(, so I can't test it right now. But when we first started the migration, I remember doing lots of tests, including calendar, as there were reported issues by RIM (this was before 4.1.3, we were running 4.1.2). And everything was fine.

I tested the calendar request to a user on Exchange 2007 and it is fine, the request came in to the handheld, I accepted it on the handheld and on the handheld and desktop I can see the meeting in the Calendar. And like I said on BES we are running ESM 2003, not CDO & MAPI clients for 2007. I wonder with a fix/patch the CDO and MAPI dll versions changed. CDO.dll is 6.5.7638.2 and MAPI.dll is 1.0.2536.0.

I reset the send as permissions for BESadmin. Now I can assign a device to the user. And the status of user is running. But there are two errors.
1.IT Policy status is Error. I tried to resend IT policy. Useless.
2.Last Result: Failed forwarding message. And here is the error infomation in the log file.
"Forwarding internal data to device, contentType=CMIME, routing=S23380945, device=23D54BBF, size=624, cmd=0x3, ack=0, TransactionId=-966305987, intTag=214, Tag=211, Submit=1
Packet returned as FAILED - could not be delivered to device, Tag=211"

It sounds like a database issue. Try the simple fix first which is doing a handheld wipe, remove the user from the BES and then add them again and reactivate. Please let me know how you go and depending on the result will determine what we need to do next.

It sounds like someone may have installed the updated files without notifying you. Please do a full scan for every file called cdo.dll on the BES server, you may possibly find an updated version that is registered.

I reactivated the blackberry. The IT Policy status is ok now. But all the mail and calendar are recieved when the blackberry is activated. After that. blackberry can't recieve any new email and calendar. The last result if forwarded messages in the BES is "failed forwarding message"

Here is the error message in the log file
[30085] (06/08 14:30:01.636):{0x884} {test@test.com} New mail has arrived, EntryId=3179
[40287] (06/08 14:30:01.667):{0x884} {test@test.com} Queuing message, RefId=-1805572858, EntryId=3179, Posted=06/08 14:31:00, Delivered=06/08 14:30:00
[30066] (06/08 14:30:01.667):{0x884} Total Msgs Pending 1
[30081] (06/08 14:30:01.698):{0x884} {test@test.com} Sending message to device, size=782, EntryId=3179, RefId=-1805572858, TransactionId=-966201329, Tag=985
[40279] (06/08 14:30:01.698):{0x884} {test@test.com} SubmitToRelaySendQ, Tag=985
[40000] (06/08 14:30:01.698):{0x634} [BIPP] Send data, Tag=985
[40000] (06/08 14:30:01.995):{0xFC0} [BIPP] Received status FAILED, Tag=985
[30105] (06/08 14:30:01.995):{0x884} {test@test.com} Message returned as FAILED - could not be delivered to device, Tag=985, EntryId=3179
[30066] (06/08 14:30:02.027):{0x884} Total Msgs Pending 0

Please contact your service provider and ensure the device's SIM card has BES services applied. It sounds like you have BIS or even no blackberry codes applied.

Ouch -

I'm already stuck at step 2!

How do I "create a service account called BESAdmin" in the Exchange Management Shell?

Please help!

Thanks!

I try to create a new user with that name, make them an Exchange Administrator, but when I run the first command in step 3 I get:


Add-ExchangeAdministrator : The input object cannot be bound to any parameters
for the command either because the command does not take pipeline input or the
input and its properties do not match any of the parameters that take pipeline
input.
At line:1 char:55
+ get-mailboxserver server04 | add-exchangeadministrator <<<< BESadmin -role V
iewOnlyAdmin

Is this a full version of Exchange or are you using an old RC version? Also can you post back the exact line you are inputting into the shell?

Hello

8. After the install is finished open BlackBerry Manager, an error will appear about MAPI client which you can just hit OK. The MAPI setting windows will appear so just add the server name back in and select "Check Name", if it resolves just hit OK and the manager will start.

I have pure exchange2007 environment. I followed every instruction but when starting BES manager i always get error about MAPI no matter what i try.
Nobody seems to have any solution to this problem.

garycutri :

4. From the Exchange 2007 server open the “Exchange Management Shell” which can be found in the Exchange program group. From EMS run the following two scripts to set the delegate control and required permissions:

get-mailboxserver <mail_server_name> | add-exchangeadministrator BESAdmin –role ViewOnlyAdmin

get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights ExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin


Are you sure that is get and no set dans get-mailboxserver ???

The commands above are correct.

Its possible that you may have a registry issue as it isn't correctly recording the MAPI config. Install BES 4.1 Service Pack 4 over the top and it should correct the issue.


Service Pack 4

• Filename: besx_upgrader_4.1.4.exe
• Filesize: 244 MB
• Date posted: 20-Jun-07

• Download Software
• View Related Documentation
• View Related Documentation (Japanese)

Perhaps you could give some advice, since we're in a worse situation. I have a 2000 box that BES was working with using a W2k3 box and 2003 Exch console (not sure of any missing functions but mail works fine). I added a 2007 server (to get all 2000 user over in a few weeks), and set up a second BES box on a clean W2k3 server, installed the new CDO - followed all instructions and it worked great for those on 2007.

Unfortunately I used the same SRP key and the next day the old BES got disconnected. Then the new box the same. Called BB had them reset it and now the new box is up.

Can you advise on the best direction to take here:
- delay moving users to 2007 until all BB users can go at once, and bring that box up
- get a temp SRP key (sorry haven't researched that yet) so both can run at the same time

I'm kind of screwed now since the users are on the new BES box and I'm not sure I can move them to the other one without it running the service to get them to the other box. I suppose I could uninstall the 07 CDO and install the 2003 Exch objects on the new box to tide it all over until they are migrated.
Any advice is much appreciated, since we already look bad enough to the users at this point.
PS thanks for the write up - it was very helpful.

Update - I found the post on IEMTest.exe and it showed we were missing rights on one mail store. All is working fine on the new BES with 2007 CDO. I also tested what you said about the Appointments, and it does send to the mailbox on 2000 and shows correctly in teh calendar - at least until the next DST change.

Thanks for the great post. I followed your howto (ignoring one line) and installed BES Express 4.1.4 directly on a brand new Win2K3 64 / Exchange 2007 and had no problems running it in the 64bit environment. As far as I can tell, everything is functioning perfectly.

Thanks again for your post.

I got the BES 4.1.4 setup with my Exchange 2007 but I can't get the wireless activation to work, everytime I try to activate the phone wirelessly, I recevied the server not responding message. However, I could activate the BB via wired connection and the BB can sync with the Exchange without any problem, anyone here has similar experience or know how to fix this?

Thanks

Have you assisgned a BlackBerry enterprise plan to your mobile service? Please contact your service provider and confirm that your are on a BES plan and NOT a BIS plan.

I upgraded our bes according to the instructions, but no email is coming in or going out now...
Many errors in the event log about BB controller stopping

An update..I was getting nervous and ready to reimage back to ex2003 bes...but I figured I had nothing to lose...so I reapplied 4.1.4
Bingo....we are back up and working!!

After days of trying to make this garbage work, i'm giving up

MAPI error shows up as usual. iemtest failing. I;ve checked registry. those profiles include links to files like EMSMDB.DLL which are no longer part of exchange 2007 nor cdomapi is intalling it. Re-applying SP4 for BES does nothing. anyways my rant is finished

Hi Gary

I think i found out what the problem is

when adding permission you use the following line
get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights ExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

the line that works for me is
get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights Genericread, GenericWriteExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

only after adding Genericread and genericwrite my MAPI errors went away

thank you

A few (stupid) questions:

Stand alone BB user in a small company that has MS Exchange 2007 and I am not the mail administrator.

1) I am assuming that I have to be the mail admin to set up BES Express (or buy a really nice present for my IT guy)?
2) I have BIS, so I'd have to pony up the extra $10/month for BES to get BES Express to work?
3) Going to BES, do I lose my POP accounts (Comcast)?
4) BES doesn't have to be on the MS Exchange server, can it be a remote (meaning different office)?

Thanks.

1) Yes, buy present
2) If you don't have an enterprise bb data plan, yes.
3) No, you can still use the BIS (unless of course your IT Guy says no with BES IT Policy)
4) BES should NOT be installed on the Exchange server, but should be on the same LAN. Worst case, if it can't be, make sure ping times are consistently below 75ms.

5) this really should have been posted elsewhere.