Configuration settings not replicated by Neverfail for BlackBerry Enterprise Server V4.0 and V4.1

Follow

Summary

This Knowledgebase article describes a known behavior on Neverfail for BlackBerry Enterprise Server V4.0 and V4.1


More Information

Certain changes made on the active server when using Neverfail for Blackberry Enterprise Server are not replicated to the passive server.

Settings kept under Tools -> Option -> Environment sections of the BlackBerry Management Console are not protected. These settings include the General, Database, and Serial Port configurations.

Symptoms

Changes made within the BlackBerry Management Console, under Tools -> Option -> Environment section, on the active server of the Neverfail pair are not replicated to the passive server during normal operations.

  • for version 4.1 in the BlackBerry Manager console
  • for version 4.0 in the BlackBerry Handheld Configuration tool

Causes

This is expected behavior as Neverfail Heartbeat does not replicate settings stored under HKEY_CURRENT_USER registry location.

These settings are usually configured upon install of BlackBerry Enterprise Server and are rarely changed during normal operations. During initial install, Neverfail Heartbeat creates a clone of the production server and these settings are restored to the passive server at this point.

Resolution

If a configuration change is made post install of Neverfail Heartbeat, the settings will need to be modified on both servers within the pair in order to keep the settings consistent on both servers. For Example: Modify settings on the Primary (active), then perform a switchover, and modify settings on the Secondary (active). Please contact your Neverfail Support Representative for further details if required.

MAPI Profile Configuration settings for BlackBerry for Exchange are not protected.

Symptoms

Changes made to the MAPI Profile Configuration GUI, including the password option for keystore authentication, on the active server of the Neverfail pair are not replicated to the passive server during normal operations.

Causes

This is expected behavior as Neverfail Heartbeat does not replicate settings stored under HKEY_CURRENT_USER registry location.

Resolution

If a configuration change is made post install of Neverfail Heartbeat, the settings will have to be modified on both servers within the pair in order to keep the settings consistent on both servers. For Example: Modify settings on the Primary (active), then perform a switchover, and modify settings on the Secondary (active). Please contact your Neverfail Support Representative for further details if required.

Database Authentication Method, WLAN-only configuration, Secure Connection password, and Cacerts keystore password from the BlackBerry Server Configuration are not protected.

Symptoms

Changes made within the BlackBerry Server Configuration, under Database Connectivity, WLAN SRP info, Secure Connection, and Administration Service-Cacerts keystore on the active server of the Neverfail pair are not replicated to the passive server during normal operations.

Causes

This is an expected behavior as Neverfail Heartbeat does not replicate settings stored under the HKEY_CURRENT_USER registry location.

These settings are usually configured upon installation of BlackBerry Enterprise Server and are rarely changed during normal operations. During initial installation, Neverfail Heartbeat creates a clone of the production server and these settings are restored to the passive server at this point.

Resolution

If a configuration change is made post installation of Neverfail Heartbeat, the settings will have to be modified on both servers within the pair in order to keep the settings consistent on both servers and in the case of WLAN SRP info, change in order to start the BlackBerry Router service. For Example: Modify settings on the Primary (active), then perform a switchover, and modify settings on the Secondary (active). Please contact your Neverfail Support Representative for further details if required.


Applies To

Neverfail for BlackBerry Enterprise Server V4.0, 4.1, and V5.0


Related Information

None

KBID-893

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.