• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 688
  • Last Modified:

BES 4.1.6 and Exchange 2007

Hi Guys

I've read a lot in forums about calendaring issues etc when moving to Exch 2007, so I just wanted to check that everything was correct before we did.

So far, we have a bunch of Exchange 2003 SP2 servers and 2 BES 4.1.6 servers. We also have Exchange 2007 Hub Transport, CAS and one mailbox server. There are no mailboxes on the 2007 MBX yet apart from test ones.

I have read that Exchange 2007 no longer uses CDO.dll files, so there are no files we need to update when we move mailboxes to 2007? How about the BESAdmin account though - at what point does that need to be moved? First or last, or does it not really matter?

Any help appreciated!
  • 3
  • 2
1 Solution
Gary CutriCommented:
Hi, first you need to set the permissions on the Exchange 2007 server\s for the BESadmin account (step 3 in link below).  Then move your users to the Exchange 2007 server\s.  Once all the users have been moved stop the BlackBerry Services and move the BESadmin account over.  Then on the BES perform the following:

1. Go to "Start > Program Files > BlackBerry Enterprise Server > Edit MAPI Profile" and ensure it is set to BESadmin and the new Exchange server
2. Go to "Start > Program Files > BlackBerry Enterprise Server > BlackBerry Server Configuration > Blackberry Server Tab > Edit MAPI Profile" and ensure it is set to BESadmin and the new Exchange server

After you confirm everything is working and stable you need to do the following:

1. Log onto the BES as Administrator
2. Stop and disable the BlackBerry Services
3. Uninstall Exchange System Manager
4. Install Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 (details in step 1 in the link below)
5. Restart the BES
6. Double check the two "Edit MAPI Profile" settings again
7. Set all the BlackBerry Services back to Automatic and start them again

Exchange 2007 BES Install Guide:
kam_ukAuthor Commented:
Hi Gary,

Thanks for answering...

But we're going to be moving the users from Exch 2003 to Exch 2007 in stages, so not sure when to move the BESADmin account?

Also - we already have MAPI client/CDO 1.2.1 installed on the BES servers. So when we move users to Exch 2007 MBX servers, there is nothing to do?

Gary CutriCommented:
Technically you can move the BESadmin account first but I always leave it until last (This ensures all users on 2003 will continue to function as normal).  As you already have MAPI client/CDO 1.2.1 installed on the BES just make sure the Exchange 2007\BESadmin permissions are set and you are ready to start moving users.
kam_ukAuthor Commented:

Just out of curiosity, I notice that the following files are on my Exchange 2007 server


Do you know what these do? I assume they are not related to BES?
Gary CutriCommented:
These files are from Exchange 2007 (also present in 2000 and 2003) and are not related to the BES software.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now