Upgrading BlackBerry Enterprise Server when Neverfail Heartbeat V5.2.[n] or Earlier is Already Installed

Follow

Summary

This Knowledgebase article provides information about how to upgrade BlackBerry Enterprise Server when Neverfail Heartbeat is already installed.


More Information

ASSUMPTIONS: This procedure assumes that the Primary server is active, and the Secondary server is passive. If the Secondary server is active, please omit step 2 below.

Note: When upgrading BlackBerry Enterprise Server with Neverfail Heartbeat installed, the user must either be physically present at the console of the server or use an ILO board or Management IP address to ensure access to the server after performing step 8 on the Secondary server.

Note: If a Service Pack for BlackBerry Enterprise Server modifies the BESMgmt database schema, Neverfail for SQL Server will replicate all changes to the passive SQL Server.

A. Upgrading BlackBerry Enterprise Server when Neverfail Heartbeat is already installed

  1. On both servers, check the Exchange start.bat script for any BlackBerry services; if they are present, delete them.
  2. On the active server, or a remote client, open the Neverfail Heartbeat Management Client.
  3. Perform a switchover and wait for the Secondary server to become active.
  4. Add the BlackBerry administrator account as a trusted client for Neverfail Heartbeat - for details see Section E.
  5. Backup your Neverfail file filters and configuration using the SQL Server Preserve Settings Utility (which can be used with any Neverfail Application Module or AM(X) before starting the procedure. This tool can be found on the Neverfail Extranet, under Products / Downloads -> Utilities etc.
  6. Shutdown Neverfail Heartbeat and select the option 'Exit Neverfail Heartbeat and stop all protected applications'.

On the Secondary Server

  1. Uninstall the BlackBerry Application Module (AM) (see Section B).

    NOTE: at this point the Secondary/active server will become Primary/active.
  2. Launch the Neverfail Heartbeat Server Configuration wizard and change the server's identity and role back to Secondary/active.
  3. Open the Windows Service Control Manager (SCM) and check that the status of the Neverfail Server R2 service is 'Stopped'. Set the Startup Type to 'Manual'.
  4. Close the SCM.
  5. Upgrade the Blackberry Enterprise Server and/or apply the required service packs for your current version of BES (see Section C).
  6. Launch the Neverfail Heartbeat Server Configuration wizard and change the Secondary server's role to passive.
  7. Stop the BlackBerry Enterprise Server, together with any other applications protected by Neverfail Heartbeat:
    1. Manually stop the Blackberry services using the SCM
    2. To stop SQL Server, open a Windows Command Prompt and do the following:

      Type c$>cd <Neverfail_installation_path>\R2\bin and then press Enter .

      Type c$>..\Scripts\SQLServer\Stop.bat and press Enter .
    3. Repeat step (b) for all other protected applications that reside on your server, by launching all the Stop Scripts located under each ..\Neverfail\R2\<ProtectedAppName> folder.
  8. Open the SCM and start the Neverfail Server R2 service to enable the Neverfail Packet Filter. Stop the service and set its Startup Type back to 'Automatic'.

On the Primary Server

  1. Launch the Neverfail Heartbeat Server Configuration wizard and change the Primary server's role to active.
  2. Using the SCM, set the Neverfail Server R2 Startup Type to 'Manual' and start the Neverfail Server R2 service to disable the Neverfail Packet Filter.
  3. Open a local copy of the Neverfail Heartbeat Management Client, and use this client to shut down Neverfail Heartbeat, selecting the option to 'Exit Neverfail Heartbeat and stop all protected applications'.
  4. Uninstall the BlackBerry AM (see Section B).
  5. Upgrade the Blackberry Enterprise Server and/or apply the required service packs for your current version of BES (see Section C).
  6. Open the SCM and set the Startup Type for Neverfail Server R2 service back to 'Automatic'.

On Both Servers

  1. If you wish to upgrade Neverfail Heartbeat, please do so now using the appropriate upgrade Knowledgebase article; if not, skip this step. Please see Knowledgebase article #435 - 'Upgrading Neverfail Heartbeat (All Versions)' for further details. Note that if you do choose to upgrade, a reboot will be required, after which you will have to stop Neverfail Heartbeat leaving the protected applications running.
  2. Install the BlackBerry Enterprise Server Application Module (see Section D).
  3. Start Neverfail Heartbeat on the Secondary/passive sever.
  4. Start Neverfail Heartbeat on the Primary/active server.
  5. On the active server, or a remote client, open the Neverfail Heartbeat Management Client, and use the System -> Status & Control screen to verify that the Full System Check completes successfully.
  6. Using the Data -> Configuration screen of the Management Client, check the list of file filters against the list in NFFileFilters.txt, which is located in the root of your Windows drive on the Primary server. Manually add any filters which are present in NFFileFilters.txt but absent from the current file filter listing in the Management Client.
  7. Restore the Neverfail configuration using the SQL Server Preserve Settings Utility; by running doLoadSettings.bat (make sure that NFSettings.xml is present on the root system drive).

B. Uninstalling the BlackBerry Enterprise Server AM

  1. From the folder <Neverfail_installation_path>\R2\bin under the Neverfail program directory, launch Setup.exe.
  2. Select 'Uninstall Selected Components' and then press Next .
  3. Select the BlackBerryEnterpriseServer component.

    Note: If the BlackBerryEnterpriseServer component was originally installed before the LotusDomino/Exchange component, you will be forced to uninstall both Application Modules. This will not affect the upgrade.
  4. Press Next ; click Next and then Next again.
  5. Review the Report section for errors or warnings.
  6. Press Next and then Finish to complete the uninstall.

C. Upgrading the BlackBerry Enterprise Server

Note 1: When upgrading BlackBerry Enterprise Server on your Neverfail Heartbeat server pair, please ensure you use exactly the same BlackBerry configuration settings on both servers. If you need to apply a certain HotFix or Service Packs to get to the desired version, you will have to follow the same exact steps on both servers, in the same order.

Note 2: At this point, Heartbeat should be set to 'Manual', and you will be able to reboot the server as many times as required by the installation process. Please note, as Heartbeat will be stopped following each reboot, you will have to start the required protected applications manually on this server pair: If your BlackBerry Enterprise Server is installed with a local MSDE or SQL Server instance, start the SQL Server services:

  1. Open a Windows Command Prompt.
  2. Type c$>cd <Neverfail_installation_path>\R2\bin and then press Enter .
  3. Type c$>..\Scripts\SQLServer\Start.bat and then press Enter .
  1. Before upgrading BES, please review all the upgrading pre-requisites as per RIM's documentation and make sure they are met (for example, you may need to apply a SQL Server service pack).
  2. Locate the BESN self-extracting archive on your server and run it. After the files are unzipped, the setup program should start automatically. If it doesn't, locate the unzipped folder and run Setup.exe.
  3. Complete the instructions on the screen.
  4. If prompted to restart the computer, click Yes .
  5. Log in using the same account that you used for the setup program. BlackBerry Installation Setup may launch automatically.

    Please review the Note 2 from this section. If you are running a local SQL Server or MSDE for BES, follow the instructions above.
  6. Complete the instructions on the screen. If, after entering the CAL Access License key you get 'Failed to write into the database', you will need to exit the BlackBerry Installation Setup and launch it again.

    Notes when upgrading to BES 4.1.0: At the SRP Setting BES installation phase, you will need to validate the MAPI profile; to do this, you need to start the Exchange services (if they reside locally on the same server as the BES).
  7. If there are several hotfixes to be installed, to get to the desired version, please apply them following recursively steps 1 through 7.
  8. At the end of the install, choose the option to 'Start Services'.
  9. Make sure that all the Neverfail protected applications are started by launching the start script located in each ..\Neverfail\R2\<ProtectedAppName> folder (as a reference you can check Note 2 from this section).
  10. Verify BlackBerry Enterprise Server is operational. It may be necessary to reconfigure the MAPI profile, if using BES for Exchange, after upgrading BES.
  11. Confirm the version to which you have upgraded, as follows:
    1. On the taskbar, select Start -> Settings -> Control Panel .
    2. Select 'Add/Remove Programs'.
    3. In the list of currently installed programs, select 'BlackBerry Enterprise Server'.
    4. Select 'Support Information'.
    5. Retrieve the version number

D. Installing the BlackBerry Enterprise Server AM

  1. Check that the right .AMX scripts are downloaded onto the local drives on both servers in your Neverfail server pair.
  2. From the folder <Neverfail_installation_path>\R2\bin under the Neverfail program directory, launch Setup.exe
  3. Select 'Install AM(X)' and select Next .
  4. Select Add and then select Browse to select the path to the BlackBerry Enterprise Server Application Module script. Select the '.amx' script and press OK .
    Note: If the Lotus Domino/Exchange Server Application Module was removed along with the BlackBerry Enterprise Server Application Module at step 3 of Section B above, you should also select the '.amx' script for the Lotus Domino/Exchange Application Module.
  5. Select Next .
  6. Review the 'Installation Summary' report and select Next .
  7. Review the 'Pre-Install Check Report'. If there are any failures or warnings, resolve these and then select Back , and then select Next to run the pre-install checks again.
  8. If there are no errors, the Next button will be enabled.
  9. Select Next and then select Finish to complete the installation.

E. Adding the BlackBerry Administrator Account as a Trusted Client for Neverfail Heartbeat

  1. Launch <Neverfail_installation_path>\R2\bin\nfclient.exe.
  2. Provide the username under which you are logged in (the account needs to have local or domain administrator rights) and password.
  3. Run the following command: addTrustedClient 127.0.0.1 [username] administrator - in brackets enter the account under which you are logged in.
  4. Run the following command: bye.


Applies To

Neverfail Heartbeat Version 5.2[n] and Earlier


Related Information

Knowledgebase article #1549 : Upgrading BlackBerry Enterprise Server when Neverfail Heartbeat V5.3.[n] or Later is Already Installed.

KBID-1268

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.