Installing Blackberry Enterprise Service 10 - Blackberry Device Service 6.2

I had a client who recently got his hands on a new Blackberry z10 device to test out and while he didn’t feel it was much of a priority to get a new BES 10 up, it quickly became one after his boss saw the device.  I’ve just completed the install and felt that it was pretty much the same as the old BES 5 which was quite easy to do but thought it would be a good idea to document and blog it to show what the step by step process looks like. I haven’t gotten to installing the Universal Device Server for iOS and Android phones but will do soon.  The following is what was required to get Blackberry Enterprise Service 10’s Blackberry Device Service 6.2 deployed in an environment that already has BES 5.

First off, the deployment guide I used can be found here:

Blackberry Device Service
http://docs.blackberry.com/en/admin/subcategories/?userType=2&category=BlackBerry+Device+Service

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Also note that I intend on installing Blackberry Device Service and Universal Device Service on the same server so I simply gave it a generic name.  More information about collocating the 2 services together can be found in the following KB:

Installing BlackBerry Device Service, Universal Device Service, and BlackBerry Management Studio on the same host server
http://btsc.webapps.blackberry.com/btsc/viewdocument.do;jsessionid=6BC84FE31517A1D15907D5ABED8981EC?externalId=KB32547&sliceId=2&cmd=displayKC&docType=kc&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

Setup BlackBerry Windows Server 2008 R2 Server

Begin by adding your BES service account to the local administrators group on the server:

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Continue by opening Start –> Administrative Tools –> Local Security Policy:

Image may be NSFW.
Clik here to view.

Navigate to Security Settings –> Local Policies –> User Rights Assignment:

Review the configuration for Allow log on locally to see whether the besadmin account already has these permissions as it usually does because the Administrators group usually in there but if not, add it in:

Image may be NSFW.
Clik here to view.

Continue by granting the besadmin account the Log on as a service permission:

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Setup Separate SQL Server

With the server permissions configured, proceed with opening SQL Server Management Studio and connect to the database instance you plan to use to host the Blackberry Device Service database (I’m not going to use a local SQL Express install but if you are, you can skip this step).  Navigate to Security –> Login then right click and select New Login…:

Image may be NSFW.
Clik here to view.

Select the domain besadmin account:

Image may be NSFW.
Clik here to view.

Click on the Server Roles and grant the account dbcreator permissions (this is temporary):

Image may be NSFW.
Clik here to view.

Install Blackberry Device Service

Log off of the BES 10 server and log back on as the besadmin service account and launch the installer:

Image may be NSFW.
Clik here to view.

Continue by clicking the Install button for Blackberry Device Service and confirm that you are using the correct account for the install:

Image may be NSFW.
Clik here to view.

Enter the appropriate user name, organization and select the country:

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Continue by selecting Create a Blackberry Configuration Database and Use an existing Microsoft SQL Server in your organization:

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

I’m installing all the components onto one server so all of the components will be selected:

Image may be NSFW.
Clik here to view.

Note the additional applications that will be installed:

Image may be NSFW.
Clik here to view.

Modify the Installation folder or Log-file folder locations if necessary:

Image may be NSFW.
Clik here to view.

I usually don’t change these locations because I believe that with proper monitoring put in place, we should be able to have the log files on the same installation folder drive rather than provision a new drive that doesn’t add any performance benefit in a virtualized environment because it’s probably going to be on the same LUN anyways.  Servers these days also don’t come to a grinding halt if the system drive fills up.

Review the summary and continue with the install:

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Proceed with entering the appropriate information for your SQL server and note that you can leave the default database name because the old BES 5 default database name is BESMgmt while the new BES 10 is BDSMgmt:

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

The installer will detect that the database does not exist and will ask whether one should be created:

Image may be NSFW.
Clik here to view.

Note the status for the creation of the database at the bottom:

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Provide a name for the BlackBerry Device Service:

Image may be NSFW.
Clik here to view.

Proceed by entering the required CAL and SRP keys:

Image may be NSFW.
Clik here to view.

I found the information I received from my free BES 10 trial email a bit confusing because there was no SRP key.  After doing a bit of searching, I realized that the:

CAL key = CAL Authentication Key

SRP Identifier = Serial Number

SRP authentication key = License Key

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Ensure you use the Verify button to verify that the BES 10 server can get out via port 3101 (SRP):

Image may be NSFW.
Clik here to view.

… and that the keys used for the install are valid: 

Image may be NSFW.
Clik here to view.

Unless there is a reason to change the port numbers, leave them as defaults:

Image may be NSFW.
Clik here to view.

Enter the service account credentials:

Image may be NSFW.
Clik here to view.

Choose the authentication method and/or account you would like to log into the BlackBerry Device Service:

Image may be NSFW.
Clik here to view.

Click Next to start the service:

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Note the BlackBerry Administration Service address and the BlackBerry Web Desktop Manager address and close the install wizard:

Image may be NSFW.
Clik here to view.

Verify BlackBerry Device Service SQL Database

Refreshing the database list on the SQL server should show the new BDSMgmt database created:

Image may be NSFW.
Clik here to view.

Note the database files created in the folder:

BDSMgmt.ldf – 25,600 KB

BDSMgmt.mdf – 102,400 KB

Image may be NSFW.
Clik here to view.

One of the items suggested after the install is to verify that the collation setting for the BlackBerry Configuration Database is default case-insensitive:

Image may be NSFW.
Clik here to view.

For those who aren’t familiar with SQL collation, a list can be found here:

http://msdn.microsoft.com/en-us/library/ms144250(v=sql.105).aspx

Image may be NSFW.
Clik here to view.

Note the collation settings for the BDSMgmt database:

SQL_Latin1_General_CP1_CI_AS

Image may be NSFW.
Clik here to view.

Verify Health of BlackBerry Device Service

Ensure that all the services have been started:

Image may be NSFW.
Clik here to view.

Review the Application and System logs to ensure there aren’t any unexpected errors or warnings:

Image may be NSFW.
Clik here to view.

Open up a browser and navigate to: http://<besServerName>:8080 to test the BlackBerry MDS Connection Service service:

Image may be NSFW.
Clik here to view.

If you’ve tested the SRP connection during the install and nothing on the firewall has been changed, you can skip this SRP test step but if you want to ensure the server is able to get out 3101, navigate to the following folder via the command prompt:

C:\Research In Motion\BlackBerry Enterprise Service 10.0.0\bundle0030\Modules\BDS\tools

… and execute the following:

bbsrptest.exe -host bm.srp.blackberry.com 3101

An output similar to the following will be displayed:

C:\Research In Motion\BlackBerry Enterprise Service 10.0.0\bundle0030\Modules\BDS\tools>

bbsrptest.exe -host bm.srp.blackberry.com 3101

Attempting to connect to bm.srp.blackberry.com (216.9.242.32), port 3101

Sending test packet

Waiting for response

Receiving response

Checking response

Successful

C:\Research In Motion\BlackBerry Enterprise Service 10.0.0\bundle0030\Modules\BDS\tools>

Image may be NSFW.
Clik here to view.

Log into the BlackBerry Administration Service via the URL: https://<BlackBerryServerName>/webconsole/login:

Image may be NSFW.
Clik here to view.

Note how the interface hasn’t changed much:

Image may be NSFW.
Clik here to view.

Remove Unneeded Permissions for Besadmin

Remove the dbcreator role from the besadmin account:

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Note that on page 41 under the heading:

Configure minimum database permissions for theservice account or Microsoft SQL Server account

… the guide instructs us to remove db_owner and grant only public and rim_db_bes_server role membership to the BDSMgmt database:

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

I tried this but received the error:

Drop member failed for DatabaseRole ‘db_owner’.

Image may be NSFW.
Clik here to view.

I don’t think it’s a big deal to leave the permissions as long as it is no longer a dbcreator on the database server.

------------------------------------------------------------------------------------------------------------------------------------------------------------------

Finish off the install by creating a new user on the server to verify that the server can communicate to the SQL database and then activate the user:

Image may be NSFW.
Clik here to view.

I hope this post gives anyone who is looking for something that shows what the process of install Blackberry Device Service looks like.