[GregSlater]

Guys,

Currently have 2 BES (v4.0.7.8). Using Exchange 2003 and a common SQL 2000 BESmgmt.

We definitely need to go to v4.1 soon, but we need a 3rd BES spun up sooner.

Should I stay with v4.0 until I am ready to upgrade all 3 server to v4.1, or is spinning the new box with v4.1 still a workable idea? And I guess even if "workable" would any of you still do it this way? I know the schema for the BESMgmt will be modified for this, but I read some previous posts that it would still work with caveats. The RIM docs I found related to this just indicate that you could then only manage with v4.1:

BlackBerry Search Results - KB11887

BlackBerry Search Results - KB04847

That isn't a problem... if it really is still the only issue. Anyone seen any new issues with this setup? We would only run with it for another 3 weeks or so.

[mischief007]

Stick with 4.0. I've seen weird problems when having a mixed environment like that with a shared SQL database.

[amukhey]

I concur, stick with 4.0. Only when you move to 4.1 , then upgrade all three servers.

How many users you have or what kind of architecture you have that requires 3 bes? Diff locations?

[GregSlater]

Originally Posted by amukhey

I concur, stick with 4.0. Only when you move to 4.1 , then upgrade all three servers.

How many users you have or what kind of architecture you have that requires 3 bes? Diff locations?

1600 users, 62 new on avg per month since Oct 2007. The two existing servers are enemic older servers that where put in place back when the site moved to v3.6 and was on the low end then. Already in place when I got here. They are getting replaced but bogged down in change management.

[amukhey]

1600 users 3 servers. What you can do is instead of a 3rd BES, why not do a knife edge cut over to a new server for BES #1 and do the same for bes#2. This way you dont have to purchase a whole new 3rd server..

[GregSlater]

Originally Posted by amukhey

1600 users 3 servers. What you can do is instead of a 3rd BES, why not do a knife edge cut over to a new server for BES #1 and do the same for bes#2. This way you dont have to purchase a whole new 3rd server..

You are missing the point. I have 3 existing servers... 2 are already BES servers. I need to spin up the 3rd (we have a couple SRPs from recent M&As) to cover us until the new servers make it through the red tape approval process at my company.

Anyway none of that concerned my question.

I am sticking to v4.0 on the servers until I get the new HW.

[bertiebassett]

Originally Posted by GregSlater

You are missing the point. I have 3 existing servers... 2 are already BES servers. I need to spin up the 3rd (we have a couple SRPs from recent M&As) to cover us until the new servers make it through the red tape approval process at my company.

Anyway none of that concerned my question.

I am sticking to v4.0 on the servers until I get the new HW.

Good Plan - the 4.0 and 4.1 BES relelases have differing database tables - as part of the upgrade process the changes get made to the DB schema - so god knows what happens to the db if you try and mix version levels - I'd suggest it would just break at somepoint in time...

One thing to watch for "patch support" for 4.0 stops at the end of this month..check the sticky thread at the top of the forum for more info.

[amukhey]

Ok I see, i guess that confused me for a bit there-thanks for clarifying.

Yes 4.0 for the moment and then migrate afterwards with the new HW