[LonghornKrackBerry]

i finished upgrading the DB to 4.1.5 this weekend and I left the 4.0.6 server alone (didn't upgrade it just yet). I am able to move a couple of users to the 4.1.5 instance just fine but I will not move the rest since the 4.1.5 server is geographically very very far away from the Exchange servers. The 4.0.6 server is in the same datacenter as my Exchange servers and as such i want my users on that server.

I wanted to know what I need to do in order to continue adding users to my 4.0.6 server. Will the BES mgr on 4.0.6 still work? I ask because the automated user add we performed via the 4.0.6 Resource kit stopped. We added them via the mgr on the actual server but it didn't seem to send the user the email for activation.

Am I missing something?

[penguin3107]

Are your 4.0.6 BES and your 4.1.5 BES sharing the same SQL configuration database?
If so... this is not a good idea. Don't mix BES versions on the same database. They should be the same exact version.

[LonghornKrackBerry]

I'm taking the Phased approach to move to 4.1.5. Asper the upgrade documentation this should work fine other than it stating I would need the Blackberry Manager Version 4.1 for MMC. Where is that?

[penguin3107]

What documentation are you following?
As of now, do you have two separate databases, or are both BES using the same database?

[LonghornKrackBerry]

Upgrade Guide. Blackberry Eneterprise Server for MS Exchange Version 4.1. SP5. pg. 45.
We have 2 separate BES servers a 4.0.6 and 4.1.5 (separate srp's). The use the same db called blackberry.

[shuman]

you should use the latest BM to administer your BES Domain.

[shuman]

Originally Posted by penguin3107

Are your 4.0.6 BES and your 4.1.5 BES sharing the same SQL configuration database?
If so... this is not a good idea. Don't mix BES versions on the same database. They should be the same exact version.

I am pretty sure the DB was upgraded when he installed 4.1 on the new server and pointed it to the current DB.

[penguin3107]

I've actually never done an upgrade like you're doing it.
Running two different versions of BES on the same config database doesn't sound like such a good idea to me... especially two different major releases. I wouldn't even try running 4.1.4 and 4.1.5 on the same database.

My advice to you is to move your users to the 4.1.5 BES... upgrade the 4.0.6 BES to 4.1.5, then move the users back if desired.

[penguin3107]

Originally Posted by shuman

I am pretty sure the DB was upgraded when he installed 4.1 on the new server and pointed it to the current DB.

Right... which is exactly why you shouldn't be running a 4.0 BES against the 4.1 database.

[LonghornKrackBerry]

I understand the reasoning and I really don't want to run the 4.0.6 but that server is in the same LAN as the exchange servers. If I were to move my BES users to the 4.1.5 system they would be going across the WAN.

It maybe the case that I will upgrade the 4.0.6 to 4.1.5, which i was trying to not do all at once. I'm just concerned on that after the upgrade, the servicebooks/policies are all resent. Don't know if i should be concerned about that, wouldn't want to inconvenience some vips using their BB.

I just don't understand why the upgrade guide would list that as an option if it was not supported. I am reporting one slight problem, my new activations are not going thru. The email with the activation information (can't remember the technical term) are not being sent to the user's mailbox.

Dumbfounded right now.

[hdawg]

Do NOT use the BES Manager on the 4.0 server. Only use the 4.1 one.

You've upgraded the database schema, therefore must only use an interface built for that schema.

Also, you must no longer use the User Administration Service from the 4.0 server and grab the BRK for 4.1 SP5.

In general it is a bad idea to keep servers like this for an extended period; it really is meant as a transition and when you've upgraded at least one server you should consider the other servers in a lesser state, where there only function is to keep current users operating, but more importantly should be used as a place to pull users from. Move those 4.0 users to your 4.1 server .... but from the sound of things, with the distance between Mail / BES you might have some problems there.

Don't go adding users to the 4.0 server.

[LonghornKrackBerry]

Yeah. I am going to start adding users to the 4.1.5 server. In the next weeks we will start moving all the exchange users to the datacenter where my 4.1.5 server is at. That is the only reason i have not moved them already. It maybe the case I will upgrade the 4.0.6 server to 4.1.5.

What impact is it on users after the upgrade? Servicbok/Policy being resent? Anything that i should do before that? I only say this because our VIP's are really sensitive about any single BB user losing access.

[hdawg]

Originally Posted by LonghornKrackBerry

Yeah. I am going to start adding users to the 4.1.5 server. In the next weeks we will start moving all the exchange users to the datacenter where my 4.1.5 server is at. That is the only reason i have not moved them already. It maybe the case I will upgrade the 4.0.6 server to 4.1.5.

What impact is it on users after the upgrade? Servicbok/Policy being resent? Anything that i should do before that? I only say this because our VIP's are really sensitive about any single BB user losing access.

4.0.6 to 4.1.5 will cause IT Policies to be sent and service book updates to occur for every device. How many users do you have on the BES? Average mailbox size?

[LonghornKrackBerry]

I have a small amount of BES users 800 or so but unfortunately the mailbox sizes are my problem. They range from 500mb to maybe 8 gigs (some even higher). I think that was my other reasoning because it does a rescan right.

We are working on putting a 500mb quota soon. You think that I could be opening the door for complaints from BB users if rescans are going on 8+ gig mailboxes?

[hdawg]

Originally Posted by LonghornKrackBerry

I have a small amount of BES users 800 or so but unfortunately the mailbox sizes are my problem. They range from 500mb to maybe 8 gigs (some even higher). I think that was my other reasoning because it does a rescan right.

We are working on putting a 500mb quota soon. You think that I could be opening the door for complaints from BB users if rescans are going on 8+ gig mailboxes?

The overall size isn't the issue; its the folders that BES monitors that are the issues. So if everyones inbox has 100 items, you're fine ... if you've got people with 5,000 items in their inbox ... then you'll have some trouble.

All set, you're probably going to have to reboot your BES a few times after the upgrade as threads as most likely going to get hung and not able to restart.

Typically in an environment like this I'd do the upgrade and reboot ... scan through the ALRT and CTRL log (and MAGT, but its usually too busy for me to bother with) ... and after an hour see how the MAPI worker threads are doing. If you've got a bunch hung, restart the BES.

You might look to creating additional agents / maxing out the # of mailboxes per agent too. Granted it'll add more load to the CPU / Memory on the BES, but it'll take some strain off the individual MAPI threads.