[afrazier5]

We are in the pilot phase of launching a new BES server. The server is tied to a dedicated SQL server with users on exchange. Once the pilot is complete, we need to start the move of 600+ users. We have found that if we ensure the device is disconnected from DM, delete the user from the old BES, add to the new BES and then have the user connect their device to the desktop, it will activate and start working within minutes. We have had a handful of users that report IT Policy errors on the BES and after digging further, find that their device never accepted the new policy and is still holding on to the old policy. We've tried resending the policy to no avail. Has anyone attempted this before or have any suggestions to help us out before we start our mass migration?

[x14]

1. What version of BES (Domino, Exchange, etc...)?
2. The other server is in the same or different domain?
3. Curious why you want to move to another server?

[afrazier5]

Originally Posted by x14

1. What version of BES (Domino, Exchange, etc...)?
2. The other server is in the same or different domain?
3. Curious why you want to move to another server?

We are on BES 4.1.2 for Exchange
Domains are the same but across the country (Australia)
The reason for this is that we have a massive user base located in Western Australia while the BES is located on the east coast. Due to limitations, the bandwidth between points is low causing up to 2 hour latency in receiving messages. Thus a new BES is being brought online in the same data center where the users exchange boxes are located.

As mentioned before, we've been able to successfully migrate the users however a handful are experiencing IT Policy errors. The devices themselves are working fine however are maintaining the policy from the old BES server. We need to find a way to make this as totally seamless for the end user as possible. Some of these users are top brass and cannot afford to be without their service for long.

Thanks!

[guppy413]

Hope this is not terrible news for you, but check it out.

I was given this article by RIM when I was inquiring about moving a couple of users to a test BES that doesn't share the same database as the production BES.

KB-03915

I'm not allowed to post the link because I'm too new but part of it says...


[...To move a BlackBerry user from one BlackBerry Enterprise Server to another - where the database is not shared - you must wipe the device. Wiping the device removes the IT Policy connections to the first BlackBerry Enterprise Server...]

[x14]

Originally Posted by afrazier5

We are on BES 4.1.2 for Exchange
Domains are the same but across the country (Australia)
The reason for this is that we have a massive user base located in Western Australia while the BES is located on the east coast. Due to limitations, the bandwidth between points is low causing up to 2 hour latency in receiving messages. Thus a new BES is being brought online in the same data center where the users exchange boxes are located.

As mentioned before, we've been able to successfully migrate the users however a handful are experiencing IT Policy errors. The devices themselves are working fine however are maintaining the policy from the old BES server. We need to find a way to make this as totally seamless for the end user as possible. Some of these users are top brass and cannot afford to be without their service for long.

Thanks!

I guess it all depends on how you are going to bring up the second server in Australia. If you bring it up identical to the first (same server name, SRP, and SQL) you should not see much problem.

[afrazier5]

The only main difference between the two servers is that the new one is being built on 4.1.2. The others were built on 3.6 and upgraded to the current level. Based on the KB article previously posted, it doesn't look like we'll have as much success as we had hoped. The servers also will have different names, sql servers, etc as we will have one on each coast of Australia. This is being done due to the extremely high latency between the BES and the Exchange servers our guys in WA are on...

[x14]

Originally Posted by afrazier5

The only main difference between the two servers is that the new one is being built on 4.1.2. The others were built on 3.6 and upgraded to the current level. Based on the KB article previously posted, it doesn't look like we'll have as much success as we had hoped. The servers also will have different names, sql servers, etc as we will have one on each coast of Australia. This is being done due to the extremely high latency between the BES and the Exchange servers our guys in WA are on...

I run Domino but the information should be similar. I've done hardware cutover where I've move BES from one piece of hardware to another but keeping same the same server, srp, and db. Never seen a problem. Our disaster scenario is base on failover between 2 servers.

I've seen when moving a BlackBerry from 1 BES to another (different server/srp) 1 of 2 things will happen. If the BlackBerry did not have a security policy all you have to do is Enterprise Activation.

If there was a security policy applied you have you wipe out. Otherwise the BlackBerry will reject the new policy.

[jibi]

As mentioned, the security mechanism in place for these devices locks the IT policy in place in a read-only mode on the device upon initial activation. The only way to open this up to be overwritten is to complete a security wipe. Kind of a pain in the butt for 600+ users.

...I'd recommend looking at your other alternatives, to be honest. Unless you just have a fairly relaxed device support group who has nothing better to do.

[MousePad]

So, if I understand correctly, if I have done nothing about policies, that is, install server, add users, activate, I should be able to delete the user from my old server, add him to the new, reactivate without wiping the BB and be good to go?

[greg2step]

Originally Posted by afrazier5

We are in the pilot phase of launching a new BES server. The server is tied to a dedicated SQL server with users on exchange. Once the pilot is complete, we need to start the move of 600+ users. We have found that if we ensure the device is disconnected from DM, delete the user from the old BES, add to the new BES and then have the user connect their device to the desktop, it will activate and start working within minutes. We have had a handful of users that report IT Policy errors on the BES and after digging further, find that their device never accepted the new policy and is still holding on to the old policy. We've tried resending the policy to no avail. Has anyone attempted this before or have any suggestions to help us out before we start our mass migration?

We are 95% complete a similar migration from a mix of 3.6 and 4.0 users on servers w/ local MSDE to a new group of 4.12 servers on a dedicated SQL server w/ 1 common database. Our userbase is roughly 2500.

What you propose will not work. You must security wipe every single device prior to activation on the new database. You will have service book, policy and other problems.

You are already running 4.12, very different situation from what we faced. If your database is local MSDE, start by moving the database to a separate sql server. then add 2nd server to that database, then move your users by drag and drop.