Activating users on a new BES server

[geezup]

Ok so here is the deal ,

We have an old server for simplicity sake lets call it nycbes01 , we have created and installed a new one called nycbes03. We want to move everyone to the new server , so we take their blackberries , wipe them, and then remove the from the old server and readd them on the new server 4.1.6.9 version BES

Now when we try to do enterprise activation we get very strande results.

1) the blackberry will hang for a very long time before it starts activation , it will then hang on "waiting for services" , Sometime it will complete in an hour or 2 , sometimes it will crap out at say "65 %" and come back with an error "please contact your system adminstrator".

2) Sometimes it will say complete but , when we go to the device and open " options - advance options - enterprise activation" its still showing its syncing up and shows alot of the databases are yet to be synced. Weird !!!

3) we have removed the account many times off the bes , we have wiped the device many times and reloaded the user many times but to no avail. On the phone with RIM for over an hour and they dont know whats up.

4) We have cingular and T-Mobile devices.

Ok I have access to all the log files and event viewer on the machine. here is the event viwer error I have been seeing upon activation



This a event viewer error




Another error

[SYNC-DSession] Invalid packet from device, abort the current session. (Username =1901177076, CLID=5, ECLID=2)112


This is the SYNC log tyhat matches with the Event viwer screenshot above.

eceived 72 bytes from device. [Username:204, SID=1908107016, SEQ=1/1]
[46052] (09/17 15:13:47.195):{0x19E4} [SYNC-DSession] Contain 0 record(s) and 2 command(s) from Backup.Secure Email Decision Maker [Jester, James:204]
[46047] (09/17 15:13:47.195):{0x19E4} [SYNC-DSession] Received "Initialize" for Backup's Secure Email Decision Maker. [Username:204, SID=1908107016, CLID=19, ECLID=5, PR=1275, ST=2W, CF=ServerWins, SF=65, HT=2]
[46031] (09/17 15:13:47.320):{0x19E4} [SYNC-DSession] Submit XML request to Backup connector. [Username :204]
[46059] (09/17 15:13:47.351):{0x1710} [SYNC-DSession] Start processing initialize XML request for Backup's Secure Email Decision Maker. [Username:204]
[46108] (09/17 15:13:47.460):{0x1710} [SYNC-DSession] Finish processing initialize XML request for Backup's Secure Email Decision Maker. [Username:204, RN=0]
[46074] (09/17 15:13:47.460):{0x1710} [SYNC-DSession] Server doesn't have any record, will send GET_ALL to the device. [Username:204]
[46008] (09/17 15:13:47.460):{0x1710} [SYNC-DSession] Send 1 packet(s) with 16 bytes to the device. [Usernamemes:204, SID=1908107016, CLID=19, ECLID=5, TAG=11847, ST=20]
[40000] (09/17 15:13:47.460):{0x1910} [BIPP] Send data, Tag=11847
[40000] (09/17 15:13:48.226):{0x6FC} [BIPP] Received status DELIVERED, Tag=11847
[46076] (09/17 15:13:48.351):{0x1FD4} [SYNC-DSession] Send config update XML to Backup connector. [Username:204]
[46019] (09/17 15:13:48.351):{0x1FD4} [SYNC-DSession] DSession is finished. [Jester, James:204, SID=1908107016, CLID=19, ECLID=5]
[46008] (09/17 15:13:48.398):{0xFB8} [SYNC-SSession] Send 1 packet(s) with 572 bytes to the device. [Username:204, SID=559472796, CLID=5, ECLID=20, TAG=11848, ST=40]
[40000] (09/17 15:13:48.398):{0x1910} [BIPP] Send data, Tag=11848
[46052] (09/17 15:13:48.398):{0xFB8} [SYNC-SSession] Contain 0 record(s) and 44 command(s) from Backup.Browser Folders/AutoText/Options/Secure Email Decision Maker/Service Book/Recipient Cache/Phone Options/Memory Cleaner Options/Key Store Options/File Explorer Options/Browser Options/Bluetooth Options/Attachment Options/Alarm Options... [Username:204]
[40000] (09/17 15:13:48.929):{0x6FC} [BIPP] Received status DELIVERED, Tag=11848
[40000] (09/17 15:13:55.554):{0x6FC} [BIPP] Received datagram, Tag=3771375
[46042] (09/17 15:13:55.554):{0x1FC0} [SYNC-SSession] Received 27 bytes from device. [Username :204, SID=559472796, SEQ=1/1]
[46096] (09/17 15:13:55.554):{0x1FC0} [SYNC-SSession] Received error status from device. [Username:204, SID=559472796, CLID=5, ECLID=20]
[16082] (09/17 15:13:55.554):{0x1FC0} [SYNC-SSession] Device responded DATABASE_NOT_FOUND against USE command. No record for this database will be synced. [Username:204, SID=559472796, DS=Backup, DB=Options]
[16082] (09/17 15:13:55.585):{0x1FC0} [SYNC-SSession] Device responded DATABASE_NOT_FOUND against USE command. No record for this database will be synced. [Username:204, SID=559472796, DS=Backup, DB=Recipient Cache]
[46025] (09/17 15:13:55.710):{0x1FC0} [SYNC-SSession] Drop GET command because the response from device is DATABASE_NOT_FOUND. [Username:204, DS=Backup, DB=Options, GUID=-78, UID=0]
[46025] (09/17 15:13:55.820):{0x1FC0} [SYNC-SSession] Drop GET command because the response from device is DATABASE_NOT_FOUND. [Username:204, DS=Backup, DB=Recipient Cache, GUID=-82, UID=0]
[46019] (09/17 15:13:56.507):{0x1FC0} [SYNC-SSession] SSession is finished. [Jester, James:204, SID=559472796, CLID=5, ECLID=20]
[46032] (09/17 15:13:58.679):{0x1A3C} [SYNC-UserControl] Send XML response to Exchange connector. [Rogers, Grant:115]

Let me know what else I can provide , we been having these issues with almost every blackberry re-activation on the new server.

[GaryCutri]

Hi,

Your first error "MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed" simply means that you don't have the "Send As" permissions set correctly for the BlackBerry Service Account (e.g. BESadmin). Can you please confirm that the account used to install the new BES was the same BlackBerry Service Account that was used on the old BES? (Check the "Log On As" setting beside the BlackBerry services snd the BES MAPI account on both servers) Also have any changes been made to Exchange (e.g. DST patches) or have any new mail servers been added? Just to give you an overview on how to easily move an entire BES to a new server please review my guide below (let me know if you need a full SQL version):

Moving BlackBerry Enterprise Server for Exchange to a New Server

MSDE\SQL 2005 Express Version

By Gary Cutri
Draft Version 1

Before You Begin

1.Ensure you have a copy of the full BES install package that is the same version of your current installation (e.g. besx_4.1.4.exe).

2.Ensure you have allowed Port 3101 TCP Outbound on your firewall from the IP Address of the new BES server.

3.If a new BES service pack is available please download it prior to starting this process.

4.It is preferred that you new BES has Server 2003 w/SP1 or higher installed.

Preparation Stage

Note: You should use your normal Domain Admin account (e.g. Administrator) to perform the following tasks.

1.Install Exchange System Manager on you new server that you plan to install the BES. Ensure you install all the same service packs and updates that are running on your mail server (e.g. SP2 and Microsoft Exchange DST patches). To confirm this stage is complete compare the versions of cdo.dll and mapi32.dll on the mail server to the BES.

Note: If you go to “Control Panel > Add\Remove Programs > Select Show Updates” you can see all the service packs installed on your Exchange Server.

2.On the new server set the permissions for your Blackberry service account (e.g. BESadmin).
-Make BESadmin a local Administrator of the server.
-Go to Admin Tools on open "Local Security Policy" and expand the "Local Policies" and "User Right Assignment". You need to add BESadmin to "Log on Locally" and "log on as Service".

3.Install MSDE on your new BES. If you are not using “MDSE Services” (i.e. RIMs application development environment) you can install SQL 2005 Express (During the 2005 Express install uncheck “Hide Advanced Options” and then choose to install a default instance). Once either version is installed download and install SQL Server Management Studio Express. If you are missing any prerequisite applications they can be found HERE.

4.Copy the BlackBerry Install package to the new BES and extract the files without running the setup.

5.On the new BES go to the command prompt and navigate to the Database directory in the extracted install files. (e.g. Default Extraction Path = c:\Research In Motion\BlackBerry Enterprise Server 4.1.x\Database). From the Database directory run CreateDB.exe BESMgmt.cfg to create a new blank BESMgmt database (This method also ensures the correct SQL schema is in place).

6.On the new BES open SQL Server Management Studio Express and expand the Security folder and right mouse click Logins and select New Login. From the Login – New window select Search and when the next window appears change your Location to Entire Directory and then enter the name of your BlackBerry Service Account (e.g. BESadmin) and then select OK once you have successfully checked the name.

Note: This long method is used to ensure the correct Domain and account name is selected.

7.Once you have successfully selected the Login Name you will be returned to the Login – New window. Now select Server Roles in the left column and choose dbcreator and sysadmin.

Move the Database

1.Log onto your old BES and stop and disable all of the BlackBerry services

2.Go to the command prompt and run the following commands to backup the database.

-osql –E
-backup database BESMgmt to disk = “c:\BESMgmt.bak”
-go
-exit

3.Copy the BESMgmt.bak file to your new Blackberry Server

4.On your new BES open SQL Server Management Studio Express and expand the Database folder. Now right mouse click BESMgmt and select “Tasks > Restore > Database”. From the restore window select From Device and then select File from Backup Media and now add the backup file.

5.Once you have added to path to the BESMgmt.bak restore file select the Restore checkbox in the lower window. Now select Options in the left column and check Overwrite the existing Database. Now select OK to restore the database.

Prepare the Migrated Database

1.Now that the database has been restored within SQL Server Management Studio Express you need to expand the BESMgmt database and select Tables. In the centre window right mouse click ServerConfig and select Open Table. Now edit the columns below and update them to display the new server name.

-ServiceName
-MachineName
-RPCEndPoint (only edit the name after “\pipe\BESMonitor” )

2.Still within the ServerConfig table scroll to the MDSAGConfigId column and ensure it is set to NULL. Now close the ServerConfig table and reselect the Tables fold in the left column and locate the MDSAGConfig table in the centre section. Once again right mouse click and select Open Table and ensure you can only see one row containing all NULL values. If a row containing server settings appears select that entire row and delete it. You can now close the MDSAGConfig table and we can now be assure no old MDS Service settings are migrated and they can be installed fresh on this new server.

3.Now select the Tables folder in the left column again. In the centre window right mouse click MDSConfig and select Open Table. Now edit the columns below and update them to display the new server name.

-MDSHost
-MachineName
-ServerName (only edit the name before “_MDS-CS_X”)

Installing the New BES

1.Log onto the new BlackBerry Server using your BlackBerry Service Account (e.g. BESadmin)

2.Run setup.exe from the install files we extracted earlier and enter your company details and select next

3.Select the BES installation type that you require (Note: BlackBerry Professional users don’t have these options). Please be aware that the first option “BlackBerry Enterprise Server” includes standard MDS to allow internet\intranet browsing via the BES. The second option “BlackBerry Enterprise Server with MDS Services” is only require if you plan on developing your own BlackBerry applications (note: you can’t select this option if you use SQL 2005 Express).

4.Now just step through the installer until you are prompted to restart. Once the server has restarted logon again as your BlackBerry Service Account and the installer will automatically start again after a few minutes (if it doesn’t just run the setup.exe file again to resume). You will now will be prompted for your database location and settings which should be correct by default. Once the settings are correct just select Next and shortly (if the installer is a newer version you will be prompted to upgrade) you should see your BES CAL on the next screen.

5.Now just continue through the remaining screens and changed any setting if required. Once you get to the last screen uncheck the “Start Services” (i.e. DO NOT START THE SERVICES) and finish the install.

6.Now open BlackBerry Manager (a MAPI error may appear) and ensure your server name is correct and all your users appear. Once you confirm the data is valid go to windows services and start the Blackberry Services in the following order:

-BlackBerry Router.
-BlackBerry Dispatcher.
-BlackBerry Controller.
-All remaining BlackBerry services.

7.Open Blackberry Manager and select the Servers tab and then select Exchange and in the properties window below ensure the server is Running and the SRP is Connected

8.Now from the BlackBerry Manager sort your users by Last Contact Time (latest first) and you should see your users being contacted and updated. (Please note delays in communication may occur as it performs mailbox rescans so wait up to 30 minutes for the service to fully resume).

9.Once you confirm your BES is functioning correctly wait 24 hours and install the latest services packs. Once again ensure you logon as the BlackBerry Service Account when installing any updates.

Note: Ensure all other technicians are aware that the BES has been moved and they MUST NOT start the BlackBerry Services on the old BES

Cleanup Stage

1.Once your new BES has been functioning for correctly for a few days please uninstall your old BES.

2.The extracted setup files can be removed if required

[Abhishek]

Thanks for this guide Gary.

[mcmackin]

Gary,
Will this same process work for Moving users to a different domain? in our current setup we have exchange at exchange.domain-corp.com. ( this is its own separate AD tree and in no way tied to our login domain. ) and bes at bes.exchange.domain-corp.com. Our new Exchange and BES are tied to our login domain. bes.domain.com and exchange.domain.com. is this going to cause issues? is there a different procedure we need to follow? we have moved users using the wipe and re-activate method.

Up until now this worked fine. However our COO and President do not want to lose their 3rd party apps or local settings ( on their handhelds ). the users we already cut over have no problem with having to be re-installed again if this will allow the COO and President to keep there settings / data.

[GaryCutri]

Originally Posted by mcmackin

Gary,
Will this same process work for Moving users to a different domain? in our current setup we have exchange at exchange.domain-corp.com. ( this is its own separate AD tree and in no way tied to our login domain. ) and bes at bes.exchange.domain-corp.com. Our new Exchange and BES are tied to our login domain. bes.domain.com and exchange.domain.com. is this going to cause issues? is there a different procedure we need to follow? we have moved users using the wipe and re-activate method.

Up until now this worked fine. However our COO and President do not want to lose their 3rd party apps or local settings ( on their handhelds ). the users we already cut over have no problem with having to be re-installed again if this will allow the COO and President to keep there settings / data.

Hi,

If you have already moved users to the new BES using this process will overwrite the current users. With regards to your COO and President's device just perform the following steps:

1. Delete the user from the old Blackberry server
2. Backup the device using BlackBerry Desktop Manager
3. Go to Options > Security Options > General Settings > Press Menu and select Wipe Handheld (Don't select the option to remove third party apps if prompted)
4. Connect the device to Desktop Manager and select Advanced from the Backup\Restore menu
5. From Advanced restore the following back to the device

• Content Store
• Profiles
• Options
• Messages
• SMS

6. Add the user to the new BES and reactivate the device.