Migrating to BES 5.0 – Part 2 – In-Place Upgrade

So, in Part 1 – I guess I lied to you a – but just a little bit.  We're actually going to upgrade to BES 5.0 in two stages

  • Stage 1 – We're going to do an in-place upgrade of our existing BES 4.x setup
  • Stage 2 – We're going to install and migrate/cutover our BES 5.0 setup from the old server (LC-SQL1) to the new server (APPS02)

If you followed along in the previous post re: prep work for BES 5.0, you know we've already met the prerequisite installs of IIS and MAPI / CDO and those things.  We already have a "besadmin" account with any appropriate permissions inside Active Directory and Exchange 2007.  So, let's move forward.

Installation
Okey dokey.  Let's start by logging onto the existing BES server as "besadmin" and launching setup.exe from the BES 5.0 media.

Picture 39

This just verifies we're logged into the server with an account with the appropriate privileges.  We are.  Click Continue Installation.

Picture 40

Accept the EULA.  Click Next.

Picture 41

Database update/information – Fill it out appropriately.  click Next.

Picture 42

Compatibility check/Database Information.  Click OK.

Picture 44

Are you SURE you want to upgrade the database?  Yes we are.

Picture 45

Off it goes.  Please wait.

Picture 46

Hooray!  Good news!  Click OK.

Picture 47

Advanced Database options.  We're not using DB mirroring.  We're using the "normal" static SQL port of 1433.  Click Next.

Picture 48

Choose options to install.  Don't forget to include the Blackberry Administration Console.  Click Next.

Picture 49

Accept the Apache EULA.  Click Next.

Picture 50

Accept the Common Public License.  Click Next.

Picture 51

We got this error.  It has to do with "Send As" – but our BES and besadmin have been working properly for years.  I made a note and will investigate later if needed.  Click OK.

Picture 52

Preinstallation checklist.  All appears good.  Click Next.

Picture 53

Verify accounts and installation location information.  Click Next.

Picture 55

Installation summary.  Finally.  Click Install.

Hmmm… the process ran for a while and then presented this error…

Picture 56

Which is strange, because when I open services.msc, the Blackberry Enterprise Server services isn't there.  Weird.  But, OK.  I click OK to restart.  We'll see what happens.  Restart done.  Log back on as besadmin.  Launch setup.exe again to continue the process.

Walk back through all the setup / installation options to get back to where we just were.

Picture 57

Hooray, much better.  Weird.  Wonder what that was?  Anyway, installation is happening.  Wait.

Picture 58

This is a good sign.  About 5-6 minutes later, all seems to be well.  We're prompted to reboot to continue.  Click Yes.  Wait for reboot.  Log back in as "besadmin" and setup will automatically relaunch

Picture 59

This is cool – the BES / Exchange configuration automatically launched and finished without me having to intercede.  That's nice too.  Anyway, let's look at the setup screen

Picture 60

Yes, this is partially cutoff – no need to expose all the information.  Verify your CAL + SRP information.  Click Next.

Picture 61

Verify the Exchange stuff that was configured automagically for you.  Click OK.

Picture 62

Verify how you want to handle the Application Extensibility.  Enter Administrator/Publisher passwords.  Click Next.

Picture 63

What's that now?  I have to change my computer name?  I don't think so. Making another note to look at that later if needed. Let's move forward.

Picture 64

Yes, I'm sure.

Picture 65

Great.  We don't do load balancing.  Click OK.

Picture 66

Yes, we're running LCS 2005 – we haven't finished the OCS 2007 R2 migration yet.  Enter the necessary info.  Click Next.  **UPDATE** – we have completed this migration now, and in Step 3, you'll notice that we're integrating with OCS on the new server as compared to LCS on this old server.

Picture 68

Administration settings.  Click Next.

Picture 69

LDAP settings – for binding with Active Directory for administrative delegation.  Enter appropriate information.  You can Query/Verify to make sure it's all right.  Click Next.

Picture 70

Now, how are we gonna handle the admin on this thing?  Common username (admin) or Windows/Active Directory authentication.  The latter.  The besadmin account is a perfect account to use for this binding.  Choose "current account credentials" and click Next.

Picture 71

OK.  Here we are.  The moment of truth.  I hope this works.  Click Start Services.

Picture 72

Awesome!  This is great news!  All services started successfully.  Click Next.

As an aside.  Even better news.  About a minute after this happened, my blackberry data-arrows started going crazy.   All the new service books and policies and whatever else started synchronizing/activating/flowing wirelessly without me having to touch a thing.  When it was done, about 3 minutes later, all my backed-up-in-queue-email from the upgrade process jumped in my Blackberry Inbox.  Great!

Anyway, back to the blog.

Picture 74

The adminstration service pops up and then gives me the addresses I need to manage BES, MDS and WDM.  Good information to keep.  Click Close.

That's that!  Things appear to be working.  I hope everyone's BB is working 🙂

Stay tuned for Part 3 when we do the magic cutover from old server (LC-SQL1) that's now upgraded to 5.0 and move to the new server (APPS02) and install BES 5.0 there and migrate the users.

4 thoughts on “Migrating to BES 5.0 – Part 2 – In-Place Upgrade

  1. Thanks for the post! I’m going to to an in-place upgrade and this will be a huge help!

  2. You rock!! I am doing in-place in the next few weeks and this was a great help in visualizing the process.

    Thank you again.

Comments are closed.