BlackBerry® Professional Software and BlackBerry® Enterprise Server Express

[knottyrope]

There are no direct inplace upgrade options for BES Express 5.0.

You do have some options though, but transporter is unsupported ( do at your own risk)

Your current SRP and CALs will no longer be needed after upgrade.

BES/SBE/BPS 4.x is installed on Exchange server:

A. You can uninstall old BES/BPS version and install BES Express 5.0 with a new database.

This most likely will require a wipe of the device to activate on BES Express 5.0 or possibly remove all desktop service books before trying.

B. You can knife edge cutover to different hardware/VM, uninstall old BES/BPS version thats on the Exchange server, install BES Express 5.0 with a new database and possibly use transporter to move users over. Dont forget to decommission old BlackBerry server KB on bottom.

C. Install BES Express 5.0 with a new database onto new hardware/VM and possibly use transporter to move users. Dont forget to decommission old BlackBerry server KB on bottom..

If installed on separate hardware/VM (not installed on exchange server) you can still choose the same above options. Just substitute installed on exchange location to where you want it to end up on.

After moving a user from BlackBerry Enterprise Server Express version 5.0 SP1 using Enterprise trans...

Transporter:

KB17538 - What is the BlackBerry Enterprise Transporter

About BES Express 5:

http://na.blackberry.com/eng/services/business/server/express/

BlackBerry Enterprise Server Express Support.

Frequently Asked Questions
View system requirements (PDF)

Watch the BlackBerry Enterprise Server Express demo

Free SRP
Free 2000 CALs
BIS or BES dataplan will work on it.
MAX 75 users when installed on the exchange server.
only 35 IT policies (remote wipe included)
Exchange 2003, 2007, 2010 suppoted

Knife Edge Cutover Notes:

Keep in mind that the netbios name of the server usually is the BlackBerry Domain Name/instance (not the actual domain name) This name needs to stay the same. The windows name can change with out issue.

If going to SQL Express:

Download and install MS SQL Server 2005 Express if needed.

Download and install MS SQL Server Management Studio Express

Enable named pipes and TCP/IP in SQL express.

 KB12247 - Move from a Microsoft SQL Server Desktop Engine database to a Microsoft SQL Server databas...

Perform a Knife-edge cutover

KB10278 - How to perform a knife-edge cutover for BlackBerry Enterprise Server software

If users can not surf the internet then do this 

KB13618 - How to update the MDSConfig table referencing a server other then the one it should be map...

Extra permissions info for BESAdmin account for reference.

KB02276 - Assigning permissions for a BlackBerry Enterprise Server service account

If you are on 2007 just install the CDO 1.2.1 from here instead of ESM 2003 tools.

http://www.microsoft.com/downloads/details.aspx?FamilyID=94274318-27c4-4d8d-9bc5-3e6484286b1f&Displa...

My knife edge notes here when I did it. I keep a old server loaded and ready but powered off now.

http://supportforums.blackberry.com/t5/BlackBerry-Enterprise-Solution/I-was-bored-so-might-as-well-p...

in case you make a new BlackBerry domain

KB12429 - Removing the BlackBerry Enterprise Server or BlackBerry components for a decommissioned Bl...

---

Top 6 install issues to share with you:

Mixed windows domain.
http://www.blackberry.com/btsc/KB18186

LDAP setup
http://www.blackberry.com/btsc/KB18197

No records were found that match the specified search criteria
http://www.blackberry.com/btsc/KB19451

Send As revoked beacuse install on DC and no local admin
http://support.microsoft.com/kb/907434

Send As

http://na.blackberry.com/eng/support/software/send as.jsp
http://na.blackberry.com/eng/support/software/send asfaq.jsp
https://www.blackberry.com/blackberrytraining/web/ SendAs/Source/video/sendAs.html

BlackBerry Messaging Agent log shows "Failed to read 001e6602 reg value from the BlackBerry MAPI profile"
Also messaging agent failed to start error code 5305

http://www.blackberry.com/btsc/KB19074

New content added

[Doug81]

In scenerio A what causes the need of a device wipe? Is it that the device is already activated?

Does removal of the service books work for sure as a workaround or are there any other workarounds?

I've got some users that can do this but I'd like to keep it as simple as possible overall for all users.

Thanks,

Doug

[knottyrope]

if not wiped you will get OTAKEYGEN in your logs since the encryption key will knot mtach. A device security wipe removes them.

KB18726 Old OTAKEYGEN packet is cancelled is displayed in the Event Log Viewer application logs afte...

[dhouk]

Is it possible to run the old BES 4.1 SBS edition in the same environment as BES Express 5, given that they are installed on separate machines (neither of which is the exchange server) and use seperate databases?

Instead of doing a massive conversion of all our blackberry users, it would be nice to be able to run both servers simultaneously and move people over to BES Express 5 gradually.  From the documentation, it appears that this is possible, but wanted to check here first to confirm and see if there are any "gotchas" to watch out for.  Thanks!

[knottyrope]

Yes follow C option.

[oscarpapa88]

Hi there,

currently running BES version 4.1.4.17 ( free one delivered with the new BB ), no chance to update to higher version of BES. My question : is there any reason to switch to the BESX ? Is that an improvement ?

THX for an answer ... 

[knottyrope]

---

oscarpapa88 wrote:

Hi there,

currently running BES version 4.1.4.17 ( free one delivered with the new BB ), no chance to update to higher version of BES. My question : is there any reason to switch to the BESX ? Is that an improvement ?

THX for an answer ... 

---

There are lots of improvements.

feature-comparison-BPS-BESX

[mvarre]

First off great post!

I was wondering if anyone knows what _exactly_ would cause the contacts to not be there after running the transporter successfully? Under what circumstances does this actually occur? The KB article says it happens because it's not supported but doesn't give any idea as to the actualy reason, so it leads one to believe it will happen for each and every user - in whcih case would make the entire process a waste.