Blackberry 5.0.1 MR2 running in Exchange 2010 / 2003 environment impact of moving BESAdmin

I'm in the middle of an Exchange 2003 to Exchange 2010 transition.  Just upgraded our BES to 5.0.1 MR2 so it will be compatible.  I've found the articles on what scripts to run to prepare Exchange 2010.  My question is that once I move the BESAdmin account mailbox from 2003 to 2010, will my BES users still on 2003 still work or will I need to migrate them at the same time to avoid an outage?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Once you've migrated your BESAdmin account, run the handheldcleanup.exe tool with a -u switch on the BES (the tool can be found in program files\research in motion\blackberry enterprise server\utility) to double-check the consistency of the BESAdmin mailbox.
jpletcher1Author Commented:
Thanks, so I will do that, but technically should my BES mailboxes still on Exchange 2003 still work then?  I assume this was implied with your answer, but just checking.
Yes that's correct - your mailboxes on Exchange 2003 will continue to work.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

jpletcher1Author Commented:
So I called in to BB support.  I was on the phone for 5 hours and this is what I found.

You cannot (or should not) move the BES mailbox from Exchange 2003 to Exchange 2010.   You should delete it and recreate it on Exchange 2010 isntead because if you move it then you don't get some attributes that an Exchange 2010 native mailbox gets.

We had to install Exchange 2010 Rollup Package 1 and the MAPI/CDO package for Exchange 2010 on the Exchange 2010 server.  Then we had to uninstall Exchange System Manager 2003 from the BES server and install a similar MAPI/CDO package so that the BES and Exchange 2010 server had matching mapi and cdo file versions.

Then none of the BES users still on Exchange 2003 worked until we moved them to Exchange 2010, ran the handheldcleanup -u, and restarted the BB Controller service.  Only after all that did devices start to sync up.  

After all was said and done, the BB support tech said the correct way to do this is with the BB Migration Kit, and you would setup a second BES server in addition to the original one.  The new one would work with Exchange 2010 and the old one would continue to work with Exchange 2003.  Then you'd migrate people from the old BES to the new BES as needed, and you can coexist that way.

Whether or not this was the only solution, the best solution, or the right solution..  I don't know.  It was just what BB support had me do to get our BES users up and working.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
That's good to know! I had no idea an Exchange 2010 native account had different attributes from a migrated 2003 account.

I was reading this link:

and in this paragraph it outlines mixed mode coexistance:
"Exchange Server 2003 uses Administrative Groups to organize Exchange objects for the purposes of delegating permission to manage those objects. Exchange 2010 does not use Administrative Groups as a logical management unit for administrative delegation. However, to support coexistence between Exchange Server 2003 and Exchange 2010, all Exchange 2010 servers are automatically put in a single Administrative Group when Exchange 2010 is installed. This Administrative Group is recognized in the Exchange System Manager of earlier versions of Exchange as Exchange Administrative Group (FYDIBOHF23SPDLT)."

Whether the differences are in AD or within Exchange is unknown, but either way I'm glad it is resolved for you.
jpletcher1Author Commented:
Yes, that Admin Group was also present in Exchange 2007 for compatibility with earlier versions of Exchange as well.  Glad it is up and going but I found little documentation on the subject overall and there was nothing on BB website stating that the correct way to do a 2003 to 2010 migration was how the tech told me.  There just seemed to be into on how to set BES up on Exchange 2010 from scratch and not migrating, which I guess is how they want you to do it to begin with.  Would have been nice to see something saying DON'T try to migrate the BES account.  Kind of frustrating.  

Thanks for your input jonny.
I was told by RIM this morning that there is no way for coexistence having users on exchange 2003 and exchange 2010 at the same time. Has anyone figured out a way for coexistence? I can't manually reactivate all my devices because they're connecting to a new BES Sql config if I have to bring up another BES environment to integrate just for Exchange 2010.

This article makes it seem like this would support coexistence as a migration plan but RIM says coexistence isn't supported.

To me it seems like it should work. It seems like the only supported coexistence is to make a new blackberry environment side by side with our existing one and to use the RIM Transport tool to move a blackberry user from blackberry organization 1 to blackberry organization 2 that we would have to create to connect to the Exchange 2010 systems.

This seems ridiculous to me... If anyone has a better suggestion i'm open. I made another post here at experts-exchnage under my own account before I found this thread.

p.s. RIM told me to migrate all my users at once to not experience an outage. I told them I had over 5,000 bes users. What a day.

Joe S.
jpletcher1Author Commented:
Hi Joe,

This sounds like what my experience was like.  All the documentation made it sound like you could have coexistence, but I found out the hard way.  They told me that I should use a trial install on the new environment and have a side-by-side, yet completely separate BES install.  Then move all uses from one to the other and get it done before the trial ends.  

You would think for something as common as this scenario, there would be both a better way and more standout documentation on it...
The documentation really does make it seem like coexistence is possible if you have the updated MAPI/CDO on all the bes servers that match the version of mapi/cdo on your exchange 2010 servers.

Since the current service account is already permissioned in AD from the domain down technically in our two cases you shouldn't have to reapply ad permissions but even if you did it should work.

I've received in email from RIM that coexistence is supported. However, I'm a little worried to even try it.

I have a new bes server license that I can use to create a new blackberry organization in the environment and I could export all the settings from the current org to the new blackberry org and then use the transport tool to migrate users to the new org at the same time when I move their mailbox from Exchange 2003 to Exchange 2010. This to me seems like the only way to ensure that there is not a service outage to blackberry devices but I've never used the transport tool before and I'm not sure how effective it is or if people have experienced problems waiting for the handhelds to activate to the new environment.

This is why I was hoping I could support coexistence exchange 2003 mailboxes and exchange 2010 mailboxes with one blackberry organization (one sql config db).

***This is what the email reply says that I received from RIM***

Thank you for contacting BlackBerry Customer Support.

Here is a link to an article in our BlackBerry Technical Solution Center that contains a description of the issue we discussed.

Article Title: How to migrate the BlackBerry Enterprise Server 5.0 from Microsoft Exchange Server 2003 or 2007 to Microsoft Exchange Server 2010

Article Number: KB22601


Following the Instructions on this article to migrate from Exchange 2003 to Exchange 2010 should not see any problems with messaging for users that stay on Exchange 2003.  This is also in making sure that both Exchange servers are communicating to each other.  I have also included the following article in relation to this.

Article Title: BlackBerry Enterprise Server support for multiple Exchange environments

Article Number: KB10394

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.