[Doreen Hacker]

Hello,

we have BlackBerry 10.2.1 as a cluster and 500 BlackBerry Z10 handhelds. Our Exchange Team wants to migrate from Exchange 2007 to 2013. The migration will going on step by step - groups of users will be migrated week per week.

How can I support this migration on Blackberry? I can only configure one Exchange server.

My idea is to "open" the cluster and use one BlackBerry server for Exchange 2007 and the other for 2013 and after migration build the cluster again.

Is this possible or are there other possibilities?

Regards, Doreen

[martinjdub]

Hi Doreen,
Like you, we're also moving our BES10.2.2 (likely BES12 MR1 soon) from 2007 to 2013 but not until the summer of 2015, so your question is one that interests me and I've made a note to begin looking into this. If you like, add my PIN so we can exchange ideas and contact details offline. 2BDFCD46

[jpvj]

Hello,

we have BlackBerry 10.2.1 as a cluster and 500 BlackBerry Z10 handhelds. Our Exchange Team wants to migrate from Exchange 2007 to 2013. The migration will going on step by step - groups of users will be migrated week per week.

How can I support this migration on Blackberry? I can only configure one Exchange server.

My idea is to "open" the cluster and use one BlackBerry server for Exchange 2007 and the other for 2013 and after migration build the cluster again.

Is this possible or are there other possibilities?

Regards, Doreen

Hi Doreen,

First you need to pay attention to EAS versions.
I assume you are on Exchange 2007 SP1 which supports EAS versions up to 12.1.
Exchange Server 2013 supports EAS versions up to 14.1. This is actually the same version as Exchange Server 2010 SP1.

If you want to utilize the new features on EAS 14.1 you need to remove and reassign the mail profile on the devices. Even though you could have used a DNS alias (like casarray.consoso.local) and point it to the new servers, BlackBerry 10 would not pick up the new EAS version and start using the features.

So my suggestion is quite simple: Create a new mail profile and assign it to the users right after migration. This should update the mail profile, pick up the lates EAS version and initiate a sync.