68
BlackBerry Enterprise Server for Microsoft Exchange Version 4.0 Maintenance Guide

Maintenance Guide

Embed Size (px)

Citation preview

Page 1: Maintenance Guide

BlackBerry Enterprise Server for Microsoft ExchangeVersion 4.0

Maintenance Guide

Page 2: Maintenance Guide

BlackBerry Enterprise Server Version 4.0 for Microsoft Exchange Maintenance Guide

Last modified: 10 November 2006

Part number: 10606659 Version 2

At the time of publication, this documentation is based on BlackBerry Enterprise Server Version 4.0.6 for Microsoft Exchange.

©2006 Research In Motion Limited. All Rights Reserved. The BlackBerry and RIM families of related marks, images, and symbols are the exclusive properties of Research In Motion Limited. RIM, Research In Motion, “Always On, Always Connected”, the “envelope in motion” symbol, BlackBerry, and BlackBerry Enterprise Server are registered with the U.S. Patent and Trademark Office and may be pending or registered in other countries.

Java and all trademarks and logos that contain Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Microsoft, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other brands, product names, company names, trademarks, and service marks are the properties of their respective owners.

The BlackBerry device and/or associated software are protected by copyright, international treaties and various patents, including one or more of the following U.S. patents: 6,278,442; 6,271,605; 6,219,694; 6,075,470; 6,073,318; D445,428; D433,460; D416,256. Other patents are registered or pending in various countries around the world. Visit www.rim.com/patents.shtml for a list of RIM [as hereinafter defined] patents.

This document is provided “as is” and Research In Motion Limited and its affiliated companies (“RIM”) assume no responsibility for any typographical, technical or other inaccuracies in this document. RIM reserves the right to periodically change information that is contained in this document; however, RIM makes no commitment to provide any such changes, updates, enhancements or other additions to this document to you in a timely manner or at all. RIM MAKES NO REPRESENTATIONS, WARRANTIES, CONDITIONS OR COVENANTS, EITHER EXPRESS OR IMPLIED (INCLUDING WITHOUT LIMITATION, ANY EXPRESS OR IMPLIED WARRANTIES OR CONDITIONS OF FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, MERCHANTABILITY, DURABILITY, TITLE, OR RELATED TO THE PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE REFERENCED HEREIN OR PERFORMANCE OF ANY SERVICES REFERENCED HEREIN). IN CONNECTION WITH YOUR USE OF THIS DOCUMENTATION, NEITHER RIM NOR ITS RESPECTIVE DIRECTORS, OFFICERS, EMPLOYEES OR CONSULTANTS SHALL BE LIABLE TO YOU FOR ANY DAMAGES WHATSOEVER BE THEY DIRECT, ECONOMIC, COMMERCIAL, SPECIAL, CONSEQUENTIAL, INCIDENTAL, EXEMPLARY OR INDIRECT DAMAGES, EVEN IF RIM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, INCLUDING WITHOUT LIMITATION, LOSS OF BUSINESS REVENUE OR EARNINGS, LOST DATA, DAMAGES CAUSED BY DELAYS, LOST PROFITS, OR A FAILURE TO REALIZE EXPECTED SAVINGS.

This document might contain references to third party sources of information, hardware or software, products or services and/or third party web sites (collectively the “Third-Party Information”). RIM does not control, and is not responsible for, any Third-Party Information, including, without limitation the content, accuracy, copyright compliance, compatibility, performance, trustworthiness, legality, decency, links, or any other aspect of Third-Party Information. The inclusion of Third-Party Information in this document does not imply endorsement by RIM of the Third Party Information or the third party in any way. Installation and use of Third Party Information with RIM's products and services may require one or more patent, trademark or copyright licenses in order to avoid infringement of the intellectual property rights of others. Any dealings with Third Party Information, including, without limitation, compliance with applicable licenses and terms and conditions, are solely between you and the third party. You are solely responsible for determining whether such third party licenses are required and are responsible for acquiring any such licenses relating to Third Party Information. To the extent that such intellectual property licenses may be required, RIM expressly recommends that you do not install or use Third Party Information until all such applicable licenses have been acquired by you or on your behalf. Your use of Third Party Information shall be governed by and subject to you agreeing to the terms of the Third Party Information licenses. Any Third Party Information that is provided with RIM's products and services is provided "as is". RIM makes no representation, warranty or guarantee whatsoever in relation to the Third Party Information and RIM assumes no liability whatsoever in relation to the Third Party Information even if RIM has been advised of the possibility of such damages or can anticipate such damages.

Certain features outlined in this document require a minimum version of BlackBerry Enterprise Server Software, BlackBerry Desktop Software, and/or BlackBerry Handheld Software and may require additional development or third-party products and/or services for access to corporate applications. Prior to subscribing to or implementing any third-party products and services, it is your responsibility to ensure that the airtime service provider you are working with has agreed to support all of the features of the third-party products and services. Installation and use of third-party products and services with RIM's products and services may require one or more patent, trademark, or copyright licenses in order to avoid infringement of the intellectual property rights of others. You are solely responsible for acquiring any such licenses. To the extent that such intellectual property licenses may be required, RIM expressly recommends that you do not install or use these products until all such applicable licenses have been acquired by you or on your behalf. Your use of third-party software shall be governed by and subject to you agreeing to the terms of separate software licenses, if any, for those products or services. Any third-party products and services that are provided with RIM's products and services are provided "as is." RIM makes no representation, warranty, or guarantee whatsoever in relation to the third-party products or services and RIM assumes no liability whatsoever in relation to the third-party products and services even if RIM has been advised of the possibility of such damages or can anticipate such damages.

Page 3: Maintenance Guide

This product includes software developed by the Apache Software Foundation (http://www.apache.org/) and/or licensed pursuant to Apache License, Version 2.0 (http://www.apache.org/licenses/). For more information, see the NOTICE.txt file included with the software.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Published in Canada

Research In Motion Limited295 Phillip StreetWaterloo, ON N2L 3W8Canada

Research In Motion UK LimitedCentrum House, 36 Station RoadEgham, Surrey TW20 9LFUnited Kingdom

Page 4: Maintenance Guide
Page 5: Maintenance Guide

Contents1 Customizing the BlackBerry environment................................................................................................. 9

Customizing the BlackBerry Controller configuration ..........................................................................................9Modify default settings using the Registry Editor .........................................................................................9

Customizing the database configuration............................................................................................................... 11Assign the BlackBerry Enterprise Server to another database ............................................................... 11Change how the BlackBerry Enterprise Server connects to the configuration database............... 12Use database roles ................................................................................................................................................ 12

Customizing logging configuration ......................................................................................................................... 12Change global logging settings........................................................................................................................ 12Change component logging settings.............................................................................................................. 13Configure BlackBerry Mobile Data Service logging ................................................................................... 13

Customize Mobile Data Service statistics .............................................................................................................. 15Customize the interval for resending pending messages................................................................................. 16Customize access to BlackBerry Manager functionality.................................................................................... 16

2 Daily monitoring...........................................................................................................................................17Interpreting statistics and settings........................................................................................................................... 17

Interpret BlackBerry Enterprise Server statistics .......................................................................................... 17Interpret user statistics......................................................................................................................................... 18Interpret Mobile Data Service statistics ......................................................................................................... 19Set the viewing options for Mobile Data Service statistics...................................................................... 21Track MAPI calls to the Microsoft Exchange Server ................................................................................... 21Export BlackBerry Enterprise Server statistics to a text file...................................................................... 22Export user statistics to a text file .................................................................................................................... 22Clear statistics ......................................................................................................................................................... 23

Configure notifications using BES Alert ................................................................................................................. 23Monitor components using system logging.......................................................................................................... 24

System logging for the Mobile Data Service ................................................................................................ 24Viewing logs .................................................................................................................................................................... 25

File names ................................................................................................................................................................ 25Default log levels................................................................................................................................................... 25

Monitoring system performance............................................................................................................................... 26Setting performance monitoring counters .................................................................................................... 26Viewing statistics using SNMP.......................................................................................................................... 27

3 Preventive maintenance..............................................................................................................................31Documenting the environment ................................................................................................................................. 31Best practices .................................................................................................................................................................. 32

Manage log file storage....................................................................................................................................... 32Perform BlackBerry Enterprise Server and user cleanup ........................................................................... 32Check MAPI subsystem........................................................................................................................................ 32Design a disaster recovery program ................................................................................................................ 32

Backing up data ............................................................................................................................................................. 33

Page 6: Maintenance Guide

Backing up the BlackBerry Enterprise Server................................................................................................ 33Backing up the configuration database......................................................................................................... 34

Preparing to use alternate BlackBerry Enterprise Servers................................................................................. 34Create a standby BlackBerry Enterprise Server ............................................................................................ 34

4 Restoring data and functionality..............................................................................................................37Moving users to another BlackBerry Enterprise Server...................................................................................... 37

Perform a sourceless move ................................................................................................................................. 37Restoring the BlackBerry Enterprise Server ........................................................................................................... 38

Switch to a standby BlackBerry Enterprise Server....................................................................................... 38Restore the BlackBerry Enterprise Server from backup on a new server ............................................. 38Restore BlackBerry Enterprise Server Microsoft Exchange components.............................................. 39

Restoring the configuration database .................................................................................................................... 39Restore the database using the BlackBerry Database Restore tool...................................................... 40Restore the database using SQL Restore ....................................................................................................... 40

Restoring remote components .................................................................................................................................. 40Change the connection to the BlackBerry Router ...................................................................................... 40Change the connection to the BlackBerry Attachment Service ............................................................. 41

Restoring functionality to handhelds...................................................................................................................... 41Re-enable an unavailable handheld................................................................................................................ 41Re-enable a handheld when the password is unknown ........................................................................... 41Return a handheld to the factory default state........................................................................................... 42

Appendix A: Required third-party permissions ......................................................................................43Microsoft Exchange permissions and privileges .................................................................................................. 43Create SQL permissions and privileges................................................................................................................... 44

Appendix B: Default ports .........................................................................................................................45

Appendix C: SNMP values...........................................................................................................................47Version 1........................................................................................................................................................................... 47Configuration .................................................................................................................................................................. 48System health.................................................................................................................................................................. 49Messaging server health.............................................................................................................................................. 51User health....................................................................................................................................................................... 51BlackBerry Enterprise Server events ......................................................................................................................... 53

Appendix D: Command prompt tools.......................................................................................................55Backing up the configuration database using the BlackBerry Database Backup tool ........................... 55

Run the BlackBerry Database Backup tool ................................................................................................... 55Restoring the configuration database using the BlackBerry Database Restore tool .............................. 56

Run the BlackBerry Database Restore tool ................................................................................................... 56Backing up and restoring BlackBerry data using the BlackBerry Backup and Restore tool ................. 57

Run the BlackBerryBackup tool......................................................................................................................... 57Creating the configuration database using the CreateDB tool...................................................................... 58

Configure the database using the BESMgmt.cfg file................................................................................. 58Run the CreateDB tool......................................................................................................................................... 59

Page 7: Maintenance Guide

Migrating users using the BESMigration tool ...................................................................................................... 60Run the BESMigration tool................................................................................................................................. 60

Retrieving and updating configuration information using the HandheldCleanup tool ........................ 60Running the HandheldCleanup tool............................................................................................................... 61

Verifying that the MAPI subsystem is initialized using the Fixmapisvc tool.............................................. 61Run the Fixmapisvc tool ...................................................................................................................................... 61

Verifying BlackBerry Enterprise Server permissions using the IEMSTest tool ............................................ 62Run the IEMSTest tool ......................................................................................................................................... 62

Testing the BlackBerry Enterprise Server SRP connection using the BBSRPTest tool ............................. 62Run the BBSRPTest tool....................................................................................................................................... 62

Repairing the registration of the performance monitor file using the BBPerfmoninstall tool............. 63Run the BBPerfmoninstall tool.......................................................................................................................... 63

Verifying Mobile Data Service data consistency using the DBConsistency tool ...................................... 63Run the DBConsistency tool .............................................................................................................................. 63Start or stop the BlackBerry Database Consistency Service .................................................................... 64

Controlling access to administration functions using the SetAdminKey tool ........................................... 64SetAdminKey tool requirements....................................................................................................................... 64Install the SetAdminKey tool ............................................................................................................................. 65Change the access mode using the SetAdminKey tool ............................................................................ 65

Page 8: Maintenance Guide
Page 9: Maintenance Guide

1

Customizing the BlackBerry environment

Customizing the BlackBerry Controller configuration

The BlackBerry® Controller monitors the BlackBerry Messaging Agents and the BlackBerry Dispatcher components. In the case of a failed operation, the BlackBerry Controller detects and restarts the appropriate processes, which enables the BlackBerry Enterprise Server® to continue to function in the event of non-responsive threads or inactive services.

The BlackBerry Controller does not attempt to restart these components when they are stopped manually by an administrator.

Modify default settings using the Registry Editor

1. Open regedit.exe.

2. In the left pane, browse to HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server.

3. Right-click Controller, and then click New > DWORD Value.

4. Add the desired values.

• Customizing the BlackBerry Controller configuration• Customizing the database configuration• Customizing logging configuration• Customize Mobile Data Service statistics• Customize the interval for resending pending messages• Customize access to BlackBerry Manager functionality

Warning: The BlackBerry Controller should not be restarted manually. If it must be restarted manually, restart it only if the other BlackBerry services are suspended.

Warning: Use the Registry Editor with caution. Failure to do so might cause damage to computer programs or the Microsoft® Windows® operating system.

Value Default Description

MaxAgentRestartPerDay 10 This value defines the maximum number of times that the BlackBerry Controller can restart the BlackBerry Messaging Agents on a daily basis.

Page 10: Maintenance Guide

10

Maintenance Guide

MaxUserDumpPerDay 3 This value defines the maximum number of .dmp files generated for each BlackBerry Enterprise Server on a daily basis, before the BlackBerry Controller restarts the BlackBerry Messaging Agents.

Note: To use this data collection option, download and install the User Mode Process Dump application included in the Microsoft Original Equipment Manufacturer (OEM) Support Tools. Visit http://support.microsoft.com/default.aspx?scid=kb;en-us;253066 for more information.

RestartAgentsOnCrash 1 This value defines whether the BlackBerry Controller should restart the BlackBerry Messaging Agents if they stop responding.

• 1: Restart the BlackBerry Messaging Agents.• 0: Do not restart the BlackBerry Messaging Agents.

RestartAgentOnHung 1 This value allows the BlackBerry Controller to generate a .dmp file when non-responsive threads are detected without restarting the BlackBerry Messaging Agents.

• 1: Create a .dmp file and do not restart the BlackBerry Messaging Agents.

• 0: Do not create a .dmp file and restart the BlackBerry Messaging Agents.

Notes: The WaitToRestartAgentOnHung value takes precedence over this value.

To use this data collection option, download and install the User Mode Process Dump application included in the Microsoft OEM Support Tools. Visit http://support.microsoft.com/default.aspx?scid=kb;en-us;253066 for more information.

RestartAgentOnHungBlackoutFrom — This value defines the lower boundary of the time range in which the BlackBerry Messaging Agents must not be restarted when a non-responsive thread is detected. The values range from 0 to 23, where 0 is 12:00 AM and 23 is 11:00 PM.

Notes: The value must be entered in decimal value, not in hexidecimal value.

Set the RestartAgentOnHungBlackoutFrom value to define the lower boundary of the time range in which the BlackBerry Messaging Agents must not be restarted. For example, if the RestartAgentOnHungBlackoutFrom value is set to 8 and the RestartAgentOnHungBlackoutTo value is set to 17, then the BlackBerry Controller does not restart the BlackBerry Messaging Agents between 8:00 AM and 5:00 PM.

Set the RestartAgentOnHungBlackoutFrom and RestartAgentOnHungBlackoutTo keys to 0 to turn off the agent restart blackout period functionality.

Value Default Description

Page 11: Maintenance Guide

11

1: Customizing the BlackBerry environment

Customizing the database configurationYou can change the configuration database settings that were defined during the installation process.

Assign the BlackBerry Enterprise Server to another database

1. On the taskbar, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Server Configuration.

RestartAgentOnHungBlackoutTo — This value defines the upper boundary of the time range in which the BlackBerry Messaging Agents must not be restarted when a non-responsive thread is detected. The values range from 0 to 23, where 0 is 12:00 AM and 23 is 11:00 PM.

Notes: The value must be entered in decimal value, not in hexidecimal value.

Set the RestartAgentOnHungBlackoutTo value to define the upper boundary of the time range in which the BlackBerry Messaging Agents must not be restarted. For example, if the RestartAgentOnHungBlackoutFrom value is set to 8 and the RestartAgentOnHungBlackoutTo value is set to 17, then the BlackBerry Controller does not restart the BlackBerry Messaging Agents between 8:00 AM and 5:00 PM.

Set the RestartAgentOnHungBlackoutFrom and RestartAgentOnHungBlackoutTo keys to 0 to turn off the agent restart blackout period functionality.

RestartDispatcherOnCrash 1 This value defines whether the BlackBerry Controller restarts the BlackBerry Dispatcher if it stops responding.

• 1: Restart the BlackBerry Dispatcher.• 0: Do not restart the BlackBerry Dispatcher.

WaitToRestartAgentOnHung 6 This value defines the number of missed health checks that occur before the BlackBerry Controller restarts the BlackBerry Messaging Agents.

Health checks occur every 10 minutes. If the health check does not receive a response from the thread being monitored, this missed health check is tracked in the log file as the wait count.

[20148] (05/12 12:21:00):{0xC28} Thread: *** No Response *** Thread Id=0xB00, Handle=0x558, WaitCount=2,When the wait count value reaches the WaitToRestartOnHung value, the BlackBerry Controller restarts the BlackBerry Messaging Agents.

A value of 0 means that the BlackBerry Messaging Agents are not restarted because of non-responsive threads.

Warning: If you enable this feature, set the value to 5 or higher so that the BlackBerry Controller has sufficient time to monitor thread health checks.

Value Default Description

Note: You must use the same administrator account that was used during the installation process.

Warning: When you change the configuration database you cannot apply any IT Policy changes until you make the handhelds affected by the configuration database change unavailable and delete stored information from them. See the BlackBerry Enterprise Server Handheld Managment Guide for more information.

Page 12: Maintenance Guide

12

Maintenance Guide

2. On the Database Connectivity tab, click Change Database.

3. Click Yes to proceed with the database change and to stop the BlackBerry Services.

4. Complete the configuration wizard, providing new database information.

5. If applicable, update the remote BlackBerry Managers with new database information. See the BlackBerry Enterprise Server Administration Guide for more information.

Change how the BlackBerry Enterprise Server connects to the configuration database

1. On the taskbar, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Server Configuration.

2. On the Database Connectivity tab, in the Authentication section, perform one of the following actions:

3. Click OK.

Use database rolesUse predefined database roles to limit the access of remote and local BlackBerry Manager installations.

Members of the rim_db_bes_server role can read and write to the database but cannot make any changes to the database schema.

Customizing logging configurationYou can change logging settings at either a global level (all log files on the BlackBerry Enterprise Server) or at a component level.

Change global logging settings1. On the taskbar, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Server

Configuration.

2. On the Logging tab, modify the desired values.

Note: You must use the same administrator account that was used during the installation process.

Action Procedure

Switch to Windows authentication. Select the Windows (Trusted) option.

Switch to SQL authentication. 1. Select the SQL Authentication option.

2. In the User Name field, type a name.

3. In the Password field, type a password.

Option Description

Log Root This value defines the root folder in which all logs associated with BlackBerry Enterprise Server operations are stored.

Note: This folder must be on a local drive.

Page 13: Maintenance Guide

13

1: Customizing the BlackBerry environment

3. Click OK.

Change component logging settings1. On the taskbar, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Server

Configuration.

2. On the Logging tab, click a BlackBerry Enterprise Server component or service.

3. Modify the desired values.

4. Click OK.

5. Restart the component or service for the changes to take effect.

Configure BlackBerry Mobile Data Service loggingBy default, the Mobile Data Service logs are stored in the same location as other component logs. See “Change global logging settings” on page 12 for more information.

1. In the BlackBerry Manager, right-click a server, and then click Mobile Data Service Properties.

Log file prefix This value specifies a custom prefix to add to all log file names.

Create daily log folder

This value specifies whether daily folders are created for logs. If cleared, all logs are stored in the root folder.

Option Description

Option Default Description

Debug log identifier — This value defines the default four-letter identifier of the component. See “File names” on page 25 for more information.

Note: The identifier can be customized up to 16 letters.

Debug daily log file Yes This value specifies whether a new log file is created every day. If set to No, the log files created do not contain the date as part of the name.

Debug log level — This value defines the level of logging written to the log file.

• 1: Error• 2: Warning• 3: Information• 4: Debug• 5: Verbose

Debug log size 0 This value defines the maximum log file size in MB. When set to 0, there is no limit enforced.

If Auto Log Rolling is enabled, a new file is created. If Auto Log Rolling is turned off, the existing file is overwritten.

Debug log auto-roll No This value specifies whether or not a new log file is created when a component is restarted or the maximum file size is reached. If set to Yes, a new log file is created and the log number is incremented.

If set to No and the specified component’s log reaches the maximum “Debug Log size” limit, the existing file is overwritten.

If set to No and the specified component is restarted, the existing file is appended with the new log information.

Debug log maximum daily file age

0 This value defines the maximum log age in days. If enabled, files are deleted after they exceed the age. When set to 0, there is no limit enforced.

Page 14: Maintenance Guide

14

Maintenance Guide

2. On the Logs tab, perform the following actions:

3. Perform the following actions:

Action Procedure

Enable logging at the SRP network layer. Select the SRP check box.

Enable logging at the IPPP network layer. Select the IPPP check box.

Enable logging at the UDP network layer. Select the UDP check box.

Enable logging at the GME network layer. Select the GME check box.

Enable logging of the HTTP headers of response messages that are sent from the web server when users retrieve content from the Internet and corporate intranet.

Select the HTTP Logging Enabled check box.

Enable logging of the HTTP headers and the body of response messages that are sent from the web server when users retrieve content from the Internet and corporate intranet.

Select the Verbose HTTP Logging check box.

Enable logging when sending encrypted data to and from the origin web server using TLS.

Select the TLS check box.

Enable logging when retrieving the certificate revocation status from the OCSP server.

Select the OCSP check box.

Enable logging for requests to access a user profile or certificate from the LDAP directory.

Select the LDAP check box.

Enable logging when downloading certificate revocation lists from the CRL server.

Select the CRL check box.

Action Procedure

Specify the level of logging to write to the Mobile Data Service log file.

1. Click the File tab, and select Log Level.

2. Select the logging level. See “Log level descriptions” on page 15 for more information.

Note: Events that are written to the log begin with a 5-digit number (for example, 30126). The first digit represents the logging level of the event.

Specify the directory location of the Mobile Data Service log files.

1. Click the File tab, and select Location.

2. Type the directory location of the log file.

Specify the interval that messages are logged to the Mobile Data Service log file.

1. Click the File tab, and select Log Timer Interval (milliseconds).

2. Type the interval, in milliseconds, that messages are logged to the log file.

Specify the level of logging to write to the UDP log file.

1. Click the UDP tab, and select Log Level.

2. Select the logging level. See “Log level descriptions” on page 15 for more information.

Specify the BlackBerry Enterprise Server SNMP agent to which the Mobile Data Service connects to send a UDP log message.

1. Click the UDP tab, and select Location.

2. Type the port used to connect to the SNMP agent, in the following format: <hostname:port>.

Note: This value is specified in the following registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerrySNMPAgent\Parameters\UDPPort. Changing the UDP location, changes the location specified in the registry.

Specify the level of logging to write to the TCP log file.

1. Click the TCP tab, and select Log Level.

2. Select the logging level for the debug log file. See “Log level descriptions” on page 15 for more information.

Specify the location to which the Mobile Data Service connects to send the TCP log message.

1. Click the TCP tab, and select Location.

2. Type the location the Mobile Data Service connects to send the log message, in the following format: <hostname:port>.

Page 15: Maintenance Guide

15

1: Customizing the BlackBerry environment

4. Click Apply.

5. Click OK.

Log level descriptionsThe log levels that are available for the Mobile Data Service, UDP, TCP, and EventLog debug log files include the following:

Customize Mobile Data Service statisticsConfigure how often the Mobile Data Service calculates and stores statistics in the database.

1. In the BlackBerry Manager, right-click a server, and then click Mobile Data Service Properties.

2. On the Stats tab, perform the following actions:

Specify the level of logging to write to the EventLog.

1. Click the EventLog tab, and select Log Level.

2. Select the logging level. See “Log level descriptions” on page 15 for more information.

Note: Events that are written to the log begin with a 5-digit number (for example, 30126). The first digit represents the logging level of the event.

Action Procedure

Note: By default, if a location or file name is not specified, the log files are saved to the location specified in the registry.

Option Description

Event events defined as 0; indicates a critical error

Error events defined as level 1; indicates an error that is lower priority than an event message

Warning events defined as level 2 or lower; indicates an important event that is not an error

Information events defined as level 3 or lower; used to monitor normal message flow

Debug All events; provides additional details for debugging

Action Procedure

Specify how long statistics are stored in the database

In the Size of history (days) field, type the number of days statistics are stored.

Specify how frequently the Mobile Data Service calculates all statistics

In the Length of statistical interval (minutes) field, type the recalculation frequency. See “Interpret Mobile Data Service statistics” on page 19 for more information.

Specify how frequently the Mobile Data Service saves statistics to the database

In the History log save interval (minutes) field, type how often to save statistics.

Specify how long statistics are stored in the database

In the Size of history log kept in memory (hours) field, type the number of hours to store statistics for.

Enable access to statistics from the last 24 hours after the Mobile Data Service is restarted

Select the Perform data backfill on startup checkbox.

Page 16: Maintenance Guide

16

Maintenance Guide

Customize the interval for resending pending messages

Configure the period of time in which the BlackBerry Enterprise Server resends messages that are not received on handhelds to the wireless network. By default, pending messages expire after seven days.

1. On the computer on which the BlackBerry Enterprise Server is installed, at the command prompt, type regedit.

2. In the left pane, browse to HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server\Agents.

3. Right-click Agents, and then click New > DWORD Value.

4. Type SendWindowInDays.

5. Double-click SendWindowInDays.

6. In the Value data field, type a value greater than 7.

7. Restart the BlackBerry Dispatcher.

Customize access to BlackBerry Manager functionality

Permit and restrict access to administrative tasks and functionality by setting access modes in the BlackBerry Manager using the SetAdminKey.exe tool. You can turn off the following features in the BlackBerry Manager interface:

See “Controlling access to administration functions using the SetAdminKey tool” on page 64 for more information.

Warning: Use the Registry Editor with caution. Failure to do so might cause damage to computer programs or the Microsoft® Windows® operating system.

BlackBerry Manager menu BlackBerry Manager Properties

BlackBerry Server Properties

User menu and User Properties

Import BlackBerry Server(s)

Export BlackBerry Servers

Send All-Points-Bulletin (APB)

Update Peer-to-Peer Encryption Key

License tab

Ports tab

Database tab

Advanced tab

Policy Rules tab

PIM Sync tab

BlackBerry Enterprise Server Properties

Mobile Data Service Properties

Set as MDS Push Server

Send All-Points-Bulletin (APB)

IT Policy

Service Control to Start/Stop BlackBerry services

Enable Mobile Data Service

Disable Mobile Data Service

Enable Mobile Data Service

Disable Mobile Data Service

IT Admin commands

IT Admin tab in User Properties

Page 17: Maintenance Guide

2

Daily monitoring

Interpreting statistics and settingsView and interpret statistics and settings for BlackBerry Enterprise Servers, users, and the Mobile Data Service. The BlackBerry Enterprise Server collects statistics automatically when it is first started.

See the BlackBerry Enterprise Server Administration Guide for information on defining BlackBerry Enterprise Server, user, and Mobile Data Service settings.

Interpret BlackBerry Enterprise Server statisticsWhen you restart the BlackBerry Enterprise Server, server statistics are automatically reset.

1. In the BlackBerry Manager, in the left pane, click BlackBerry Manager.

2. View the following information:

• Interpreting statistics and settings• Configure notifications using BES Alert• Monitor components using system logging• Viewing logs• Monitoring system performance

Option Description

BlackBerry Server Name This option shows the BlackBerry Enterprise Server name.

Number of Users This option shows the number of users on the BlackBerry Enterprise Server.

Forwarded This option shows the total number of messages forwarded to BlackBerry Wireless Handhelds™. This total depends on the filters set at the user or administrator level.

Sent This option shows the total number of messages sent from handhelds.

Pending This option shows the total number of messages currently queued for delivery to handhelds.

Filtered This option shows the total number of messages to which the BlackBerry Enterprise Server applied filters and therefore did not forward to handhelds.

Expired This option shows the total number of messages that timed out without being forwarded to handhelds.

Note: Messages time out after 7 days of non-delivery to the handheld.

Mobile Data Service This option shows whether the Mobile Data Service is enabled and running on the BlackBerry Enterprise Server.

Wireless Message Reconciliation This option shows whether wireless message synchronization is enabled on the BlackBerry Enterprise Server.

SRP Status This option shows whether the BlackBerry Enterprise Server is connected successfully to the wireless network.

Server Status (PID) This option specifies whether the BlackBerry Enterprise Server is successfully running, and specifies the unique identifier of the BlackBerry Dispatcher.

Host Name This option shows the name of the computer on which the BlackBerry Enterprise Server is installed.

Page 18: Maintenance Guide

18

Maintenance Guide

Interpret user statistics1. In the BlackBerry Manager, in the left pane, click a server.

2. View the following information:

Controller (PID) This option shows whether the BlackBerry Controller is running on the server successfully, and specifies the unique identifier of the BlackBerry Controller. The possible statuses include the following:

• running• stopped• not installed

Bypass Router (PID) This option shows whether the BlackBerry Router is running on the BlackBerry Enterprise Server successfully; it also specifies the unique identifier of the BlackBerry Router.

Attachment Service (PID) This option shows whether the BlackBerry Attachment Service is installed and running on the BlackBerry Enterprise Server successfully; it also specifies the unique identifier of the Attachment Service.

Policy Service (PID) This option shows whether the BlackBerry Policy Service is running on the BlackBerry Enterprise Server successfully; it also specifies the unique identifier of the Policy Service.

Synchronization Service (PID) This option shows whether the BlackBerry Synchronization Service is running on the BlackBerry Enterprise Server successfully; it also specifies the unique identifier of the Synchronization Service.

User Administration Service (PID) This option shows whether the User Administration Service is installed and enabled on the BlackBerry Enterprise Server successfully; it also specifies the unique identifier of the User Administration Service.

Database Consistency Service (PID) This option shows whether the Database Consistency Service is enabled on the BlackBerry Enterprise Server successfully; it also specifies the unique identifier of the Database Consistency Service.

BlackBerry Alert (PID) This option shows whether the BlackBerry Alert is running on the BlackBerry Enterprise Server successfully; it also specifies the unique identifier of the BlackBerry Alert.

Option Description

Option Description

PIN Number This option shows the personal identification number (PIN) of the handheld.

Redirection This option shows whether message redirection is enabled.

Status This option shows the general status of message redirection for the user.

• Initializing: Message redirection is starting; this status remains until the user connects the handheld to the desktop computer or is activated wirelessly on a running BlackBerry Enterprise Server.

• Running: Message redirection is active.• In-cradle: Message redirection to the handheld is unavailable.• Not configured: User must start the BlackBerry Desktop Manager.• Redirection disabled: You made message redirection unavailable or the user turned off

redirection in the Desktop Manager.• Verifying forwarding address: Message address that is used to forward messages to the user's

handheld is being verified.• Invalid forwarding address: Message address is not valid.• No PIN: The user does not have a valid PIN or a PIN has not been assigned to the user.• No desktop address: User does not have a valid desktop address.

Mobile Data Service This option shows whether the Mobile Data Service is enabled for the user.

Wireless Message Reconciliation

This option shows whether wireless message synchronization is enabled on the user’s handheld.

Page 19: Maintenance Guide

19

2: Daily monitoring

Interpret Mobile Data Service statistics You view Mobile Data Service status, statistics, and errors on a handheld or using a desktop web browser. If the Mobile Data Service is not running or is listening on a port that is different from the one specified, no results display in the web browser.

Perform one of the following actions:

Wireless Calendar Synchronization

This option shows whether wireless calendar synchronization is enabled for the user.

Device Type This option shows the network on which the user’s handheld operates.

User Mailbox DN This option shows the distinguished name of the user’s mailbox.

Exch. Server This option shows the name of the user’s messaging server.

Agent ID This option shows the unique identifier of the BlackBerry Enterprise Server.

ITPolicy This option shows the name of the IT policy to which the user is assigned.

Policy Status This option shows whether the handheld received the IT policy.

Policy Time sent This option shows the time that the IT policy was last sent to the handheld.

Policy time recvd This option shows the time that the IT policy was received by the handheld.

Forwarded This option shows the total number of messages forwarded to the user’s handheld; this total depends on the filters that are set at the user or administrator level.

Sent This option shows the total number of messages that were sent from the user’s handheld.

Pending This option shows the total number of messages that are currently queued for delivery to the user’s handheld.

Filtered This option shows the total number of messages to which the BlackBerry Enterprise Server applied filters and therefore did not forward to the user’s handheld.

Expired This option shows the total number of messages that timed out without being forwarded to the handheld.

Note: Messages time out after 7 days of non-delivery to the handheld.

Last fwd time This option shows the date and time that the last message or calendar item was forwarded to the user’s handheld.

Last sent time This option shows the date and time that the last message or calendar item was sent to the user’s handheld.

Last contact time This option shows the amount of time since the last transaction occurred between the BlackBerry Enterprise Server and the handheld.

Last result This option shows the last result that the BlackBerry Enterprise Server returned to the user.

Creation Time This option shows the date on which the user account was created.

Tip: View additional user information in the BlackBerry Manager on the top bar, in the right pane.

Option Description

Task Procedure

View Mobile Data Service statuses in a web browser.

1. On your handheld or desktop computer, open a web browser.

2. In the Address field, type http://<MDS computer>:<web server port>/admin/common, where <web server port> is the port number set in the Mobile Data Service general properties. The default value is 8080.

See “Mobile Data Service statuses” on page 20 for more information.

Page 20: Maintenance Guide

20

Maintenance Guide

Mobile Data Service statuses

Mobile Data Service statistics

View Mobile Data Service statistics in a web browser.

1. On your handheld or desktop computer, open a browser.

2. In the Address field, type http://<MDS computer>:<web server port>/admin/statistics/Statistics where <web server port> is the port number set in the Mobile Data Service general properties, in the Web Server Listen Port parameter. The default value is 8080.

See “Mobile Data Service statistics” on page 20 for more information.

Note: Statistics and errors display in three columns: the first column displays results for the last hour, the second column displays results for the last 6 hours, and the third column displays results for the last 24 hours.

Task Procedure

Option Description

MDS name This option shows the name of the Mobile Data Service.

Database connection status This option shows the URL used to establish a connection to the database.

MDS started on This option shows the date and time that the Mobile Data Service last started.

SRP connection status This option shows the SRP ID that the BlackBerry Enterprise Server uses to connect to the BlackBerry Infrastructure.

Last SRP connection attempt This option shows the date and time that the Mobile Data Service last attempted to connect to the BlackBerry Enterprise Server.

MDS URL This option shows the URL of the Mobile Data Service administration web page.

Option Description

Authorization exception This option shows the number of requests that resulted in an error during authorization with the Mobile Data Service.

Authorization failure This option shows the number of requests that the Mobile Data Service failed to authorize.

Authorization success This option shows the number of requests that the Mobile Data Service authorized successfully.

Device Connections timed out

This option shows the number of handheld-initiated connections that were terminated when a connection timeout was reached.

Device Connections truncated

This option shows the number of handheld-initiated connections that requested content that exceed the maximum size for each connection.

Device authentication failure This option shows the number of handheld-initiated connections that the Mobile Data Service failed to authenticate.

Max content size of device connections (KB)

This option shows the maximum size, in kilobytes, of Mobile Data Service data packets that were requested from handhelds.

Total content size of device connections (KB)

This option shows the total size, in kilobytes, of Mobile Data Service data packets that were requested from handhelds.

Device connections: MAX latency (msecs)

This option shows the maximum time, in milliseconds, that is required to send data packets from the handheld to the Mobile Data Service.

Device connections: AVG latency (msecs)

This option shows the average time, in milliseconds, that is required to send data packets from the handheld to the Mobile Data Service.

Number of packets from device connections

This option shows the number of packets that were sent from the handheld to the Mobile Data Service.

Device connections This option shows the number of handheld-initiated connections that the Mobile Data Service received.

HTTP Errors: 400, 404, 500 This option shows the number of HTTP errors created when retrieving content from the Internet or intranet.

Max content size of push connections (KB)

This option shows the maximum packet size, in kilobytes, that the Mobile Data Service received from push application servers.

Page 21: Maintenance Guide

21

2: Daily monitoring

Set the viewing options for Mobile Data Service statistics 1. On your handheld or desktop computer, open a web browser.

2. In the Address field, type http://<MDS computer>:<web server port>/admin/statistics/Statistics where <web server port> is the port number set in the Mobile Data Service general properties.

3. Click Customize statistics.

4. In the Select reference time section, perform one of the following actions:

5. In the Select intervals section, click the time interval (before the reference time) to view statistics for, and then click Add interval(s).

6. In the Select variables section, click the statistics to view.

7. Perform one of the following actions:

8. At the top of the page, click Statistics.

Track MAPI calls to the Microsoft Exchange ServerYou can configure the BlackBerry Enterprise Server to track MAPI calls to the Microsoft Exchange Server. The BlackBerry Enterprise Server writes MAPI statistics to the BlackBerry Messaging Agent log daily.

1. On the computer on which the BlackBerry Enterprise Server is installed, at the command prompt, type regedit.

Total content size of push connections (KB)

This option shows the total packet size, in kilobytes, that the Mobile Data Service received from push application servers.

Number of packets from push connections

This option shows the number of packets that were sent from the push application server to the Mobile Data Service.

Push connections This option shows the number of push server connections that the Mobile Data Service received.

Current device requests queue size

This option shows the total packet size, in bytes, for handheld-initiated connections.

SRP Connections failed This option shows the number of connections from the origin web server or handheld to the BlackBerry Enterprise Server that failed.

SRP Connections succeeded This option shows the number of connections from the origin web server or handheld to the BlackBerry Enterprise Server that succeeded.

SRP Invalid packet This option shows the number of incorrect packets that the Mobile Data Service received.

SRP Refused packet This option shows the number of packets that the Mobile Data Service refused.

Option Description

Action Procedure

View statistics for the current time. Click Current time.

View statistics for a specified date and time. 1. Click From Date (M/d/yy h:mm am/pm).

2. Type the date and time.

Action Procedure

View selected statistics. Click Add selected statistic(s).

View all statistics. Click Add all statistics.

Page 22: Maintenance Guide

22

Maintenance Guide

2. In the left pane, browse to HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server\Agents.

3. Right-click Agents, and then click New > DWORD Value.

4. Type EnableMapiStats.

5. Double-click EnableMapiStats.

6. In the Value data field, type 1 to turn on MAPI call statistic tracking.

7. Restart the BlackBerry Controller.

Check the Messaging Agent log for MAPI statistics informationThe following is an example of the MAPI statistics log line to look for in the Messaging Agent log once you have turned on MAPI call statistic tracking:[40852] (00:04:30):{0x0550} MAPI Statistics Summary: Ave=0.0043s, Count=18, Max=0.0160s, Mailbox=Clyde Warren, ProcName=ReloadPagerConfig, Time=Thu Oct 07 10:36:49 2004

Export BlackBerry Enterprise Server statistics to a text fileSee “Interpret BlackBerry Enterprise Server statistics” on page 17 for a list of the BlackBerry Enterprise Server statistics that you can export.

1. In the BlackBerry Manager, right-click a server, and then click Export List.

2. Specify a location and file name.

3. Click Save.

Export user statistics to a text fileYou can export the display name, PIN, enabled state, forwarded, sent from handheld, pending to handheld, expired, filtered, and mailbox statistics for a specific user.

1. In the BlackBerry Manager, in the left pane, click a server.

2. In the User Name list, right-click a user, and then click Export User Info.

3. Perform one of the following actions:

4. Perform one of the following actions:

5. Specify a location and file name.

6. Click Save.

Tip: Press CTRL to select multiple users at the same time.

Action Procedure

Include usage statistics in the export. Click Yes.

Do not include usage statistics in the export. Click No.

Action Procedure

Retain user statistics after the export is complete. Click No.

Clear user statistics after the export is complete. Click Yes.

Page 23: Maintenance Guide

23

2: Daily monitoring

Clear statistics1. In the BlackBerry Manager, in the left pane, click a server.

2. Perform one of the following actions:

Configure notifications using BES AlertBES Alert watches the Microsoft Windows NT® Event log and sends defined users a copy of events whenever an error, warning, or information event is recorded. You must configure these settings on each BlackBerry Enterprise Server.

1. In the BlackBerry Manager, right-click a server, and then click BlackBerry Server Properties

2. On the BES Alert tab, perform the following actions:

3. In the User Notification section, click Add.

4. Perform the following actions:

Action Procedure

Clear server statistics. 1. Right-click a server, and then click Server Stats.

2. Click Clear Server Stats.

3. Click OK.

Clear user statistics. 1. In the User Name list, right-click a user.

2. Click User Stats.

3. Click Clear Server Stats.

4. Click OK.

Action Procedure

Define the SMTP address from which to send notifications.

In the Messages Sent From field, type the SMTP address from which to send and receive replies to alert messages (for example, [email protected]).

Define the SMTP computer through which to send notifications.

In the SMTP Server Machine field, type the SMTP server name of your gateway in DNS format (for example, smtp.CompanyName.com).

Define the level at which to monitor events.

From the Default Notification Level drop-down list, select one of the following options:•Error: All level 1 events (error)•Warning: All level 2 events and lower (warning and error)•Informational: All level 3 events and lower (informational, warning, and error)

Action Procedure

Define who to send the notifications to.

Type the recipient’s name.

Define the level at which to send notifications.

From the Notification Level drop-down list, select one of the following options:•Default: the event level defined for BES Alert•Error: all level 1 events (error)•Warning: all level 2 events and lower (warning and error)•Informational: all level 3 events and lower (informational, warning, and error)

Note: If you define a value other than Default, this setting overrides the default event level defined for BES Alert.

Define the SMTP address to send notifications to.

Type the SMTP address to which notifications are sent.

Page 24: Maintenance Guide

24

Maintenance Guide

5. Click OK.

Monitor components using system loggingSystem logging (syslog) is a standard protocol for monitoring servers on a network. If events occur, they are transferred using User Datagram Protocol (UDP) to the syslog tool, where information is logged and console or user notifications can be sent.

Use syslog for additional monitoring of all BlackBerry Enterprise Server components, except for the BlackBerry Attachment Service and the Mobile Data Service. Syslog cannot be configured for the Attachment Service. See “System logging for the Mobile Data Service” on page 25 for more information. Do not use syslog tools on the same computer that the BlackBerry Enterprise Server is installed on.

1. Install a third-party syslog tool on a computer that does not contain the BlackBerry Enterprise Server installation.

2. On the BlackBerry Enterprise Server, open regedit.exe.

3. In the left pane, browse to HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server.

4. In the Logging Info section, click the component to monitor.

5. Modify the desired values.

6. Repeat steps 4 through 5 for the remaining components.

System logging for the Mobile Data ServiceBecause the Mobile Data Service uses UDP to transfer SNMP data, use Transmission Connection Protocol (TCP) to connect to the syslog tool.

Type the SysLogHost IP address and port as the destination location for TCP logs.

See “Configure BlackBerry Mobile Data Service logging” on page 13 for more information.

Define the computers on which console message notifications display.

Type the console name on which to display notifications.

Action Procedure

Value Type Action

<Default> DWORD Define the UDP port on which syslog listens for events. The default is port 514.

SysLogHost String Type the IP address and port of the syslog tool (for example, 10.10.10.10:4070). If other sysloghost information is already configured for the component, add the syslog tool to the end of the string, separated by a comma.

SysLogLevel DWORD Define the log level to communicate events to the syslog tool.• 1: error• 2: warning• 3: informational• 4: debug• 5: other

Page 25: Maintenance Guide

25

2: Daily monitoring

Viewing logsYou view logs in the root log directory that you defined during the installation process. The default location is C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\. In the root log directory, the BlackBerry Enterprise Server organizes files into daily folders. See “Change global logging settings” on page 12 for more information.

File namesThe BlackBerry Enterprise Server creates log file names using the format <ServerName_Identifier_Instance_YYYYMMDD_Log#.txt>. See “Customizing logging configuration” on page 12 for information on changing the settings.

Default log levelsThe BlackBerry Enterprise Server defines log levels automatically during the installation process. See “Log level descriptions” on page 15 for more information.

Component name Identifier

BlackBerry Attachment Service ASRV

BlackBerry Attachment Conversion ACNV

BlackBerry Dispatcher DISP

BlackBerry Alert ALRT

BlackBerry Messaging Agent MAGT

BlackBerry Synchronization Connector CONN

BlackBerry Manager MNGR

BlackBerry Handheld Configuration Tool HHCG

BlackBerry Router ROUT

BlackBerry Controller CTRL

BlackBerry Policy Service POLC

BlackBerry Mobile Data Service MDAT

BlackBerry Synchronization Service SYNC

Backup Connector CBCK

Exchange Connector CEXC

Management Connector CMNG

Component name Default log level

BlackBerry Attachment Service 1

BlackBerry Attachment Conversion 1

BlackBerry Dispatcher 3

BlackBerry Messaging Agent 4

BlackBerry Manager 4

BlackBerry Handheld Configuration Tool 3

BlackBerry Router 3

BlackBerry Controller 3

BlackBerry Policy Service 4

BlackBerry Synchronization Service 4

Backup Connector 4

Page 26: Maintenance Guide

26

Maintenance Guide

Monitoring system performanceMonitor system performance to understand the impact of BlackBerry user growth and of specific BlackBerry components on hardware resources.

Setting performance monitoring countersUse the counters included in the BlackBerry Enterprise Server software to monitor statistics for all active users with standard performance monitoring tools, such as the Windows Performance monitor. These statistics reflect server activity since the last time that the BlackBerry Enterprise Server restarted.

Set counters1. On a remote server, on the taskbar, click Start > Programs > Administrative Tools > Performance.

2. In the left pane, click the System Monitor object.

3. Click the + icon.

4. From the Select counters from computer drop-down list, select the name of the BlackBerry Enterprise Server to monitor.

5. From the drop-down list, select a performance object.

6. Modify the desired values.

Exchange Connector 4

Management Connector 4

Component name Default log level

Note: If the BlackBerry Enterprise Server is running and the BlackBerry-specific counters are not visible in the list, you might need to re-install or repair the .dll file. See “Repairing the registration of the performance monitor file using the BBPerfmoninstall tool” on page 63 for more information.

Performance object Counter Action

BlackBerry Server Connection State

Messages Expired

Messages Filtered

Messages Forwarded

Messages Forwarded/min

Messages Pending

Messages Sent

Messages Sent/min

1. Select the All counters option.

2. Click Add.

Page 27: Maintenance Guide

27

2: Daily monitoring

7. Click Close.

Enabling loggingEnable logging on performance monitoring counters for one business day each week. Use this information to analyze the impact of additional users or the implementation of new features (for example, the Mobile Data Service or Attachment Service) on hardware resources.

Viewing statistics using SNMPYou can use Simple Network Management Protocol (SNMP) to assess the configuration and status of your BlackBerry Enterprise Server and its users.

The Management Information Base (MIB) for the BlackBerry Enterprise Server is BlackBerryServer.mib, which is located on the computer on which the BlackBerry Enterprise Server is installed (in C:\Program Files\Research In Motion\BlackBerry Enterprise Server\).

An OID is a sequence of integers that uniquely identifies a value by defining the path to that value through a registration tree. All BlackBerry Enterprise Server SNMP OIDs begin with 1.3.6.1.4.1.3530.5, and all traps begin with 1.3.6.1.4.1.3530.5. Each value integer is distinguished by a suffix, such as 25.1.1.

RequirementsViewing server redirection statistics in an SNMP browser requires the following:

• running SNMP service

• SNMP browser

Process %Processor Time

Network usage

Memory usage

1. Select the Select counters from list option.

2. In the list, click %Processor Time.

3. Select the Select instances from list option.

4. In the list, click the following instances:•BBAttachServer•BBConvert(#1-3)•BlackBerryAgent•BlackBerryDispa•bmds•BlackBerrySyncS•EXMGMT

5. Click Add.

6. Repeat steps 1 through 5 for the remaining recommended process counters.

Note: These process instances are the ones most likely to impact resources. Other BlackBerry processes can be monitored if desired.

Performance object Counter Action

Notes: A session begins when the BlackBerry Enterprise Server starts.

The counters listed in the preceding table include only messages that are routed through the BlackBerry Enterprise Server. They do not include PIN, SMS, and other messages that are not routed through the server.

Note: You must compile and register the .mib file to view descriptive names for MIB variables; otherwise, the SNMP monitor tool that you use displays the Object Identifiers (OIDs) only.

Page 28: Maintenance Guide

28

Maintenance Guide

Supported functions

Recommended values to monitorTo begin using SNMP monitoring, start with the following values. See “Appendix C: SNMP values” on page 47 for more information.

Option Description

Get This function retrieves a specified value that is stored in a table on the server. For example, a Get request for the MIB variable besTotMsgsPending returns the total number of messages that are queued for delivery to handhelds on the BlackBerry Enterprise Server.

Get Next This function fetches the next sequential MIB variable after the previous request.

Walk • This function extracts all BlackBerry Enterprise Server and user information, with two exceptions:• To WALK the BlackBerry Enterprise Server User Health container, use its full root (1.3.6.1.4.1.3530.5.30)

explicitly.

Trap This function sends messages triggered by defined events; messages are sent from the BlackBerry Enterprise Server to the client computer.

Category Value Description Object identifier

System Health

besSysHealthSrpReconnectsFail

the number of times that the BlackBerry Enterprise Server has attempted, but failed, to connect to the wireless network since startup

1.3.6.1.4.1.3530.5.25.1.13

besSysHealthSrpTotalSecNotConnected

the total number of seconds that the BlackBerry Enterprise Server has not been connected to the wireless network since startup

1.3.6.1.4.1.3530.5.25.1.14

besSysHealthSrpLastErrorText

the error text associated with the last failed connection attempt

1.3.6.1.4.1.3530.5.25.1.15

besSysHealthMsgFilteredByGlobal

the total number of messages to which the BlackBerry Enterprise Server applied global filters and did not forward to handhelds since startup

1.3.6.1.4.1.3530.5.25.1.24

besSysHealthMsgPending the total number of messages that are pending delivery to handhelds

1.3.6.1.4.1.3530.5.25.1.25

besSysHealthMsgErrors the total number of messages that were not delivered to handhelds because of an error

1.3.6.1.4.1.3530.5.25.1.27

User Health

besUserHealthLastErrorText the error text that was returned the last time an operation for this user failed

1.3.6.1.4.1.3530.5.30.1.10

besUserHealthLastErrorTime the date and time of the last error for this user 1.3.6.1.4.1.3530.5.30.1.11

besUserHealthMsgPending the total number of messages that are pending delivery to the user’s handheld

1.3.6.1.4.1.3530.5.30.1.44

Page 29: Maintenance Guide

29

2: Daily monitoring

BlackBerry Enterprise Server events

besSRPConnectEvent indicates whether the BlackBerry Enterprise Server is connected to the wireless network, as indicated by the last integer in the OID

1.3.6.1.4.1.3530.5.1.0 - specific trap #1 (connected) and #2 (disconnected)

besHungThreadEvent indicates that a BlackBerry Enterprise Server non-responsive thread has been detected

1.3.6.1.4.1.3530.5.3.0 - specific trap #3

besMailServerDownEvent indicates whether the messaging server is running, as indicated by the last integer in the OID; this event occurs if more than one user (or one user if there is only one) on the messaging server receives more than one non-access control error while connecting to the messaging server

1.3.6.1.4.1.3530.5.5.0 - specific trap #5 (mail server down) and #6 (mail server up)

besMDStoBESConnectionEvent indicates whether the Mobile Data Service is connected to the BlackBerry Enterprise Server, as indicated by the last integer in the OID

1.3.6.1.4.1.3530.5.7.0 - specific trap #7 (connected) and #8 (disconnected)

besMDSStartStopEvent indicates whether the Mobile Data Service is started, as indicated by the last integer in the OID

1.3.6.1.4.1.3530.5.11.0 - specific trap #11 (started) and #12 (stopped)

besMDStoDBConnectionEvent indicates whether the Mobile Data Service is connected to the database, as indicated by the last integer in the OID

1.3.6.1.4.1.3530.5.13.0 - specific trap #13 (connected) and #14 (disconnected)

besCriticalEvent indicates that an event has been logged with a 1xxxx or 5xxxx (critical) event ID

1.3.6.1.4.1.3530.5.21.0 - specific trap #21

Category Value Description Object identifier

Page 30: Maintenance Guide

30

Maintenance Guide

Page 31: Maintenance Guide

3

Preventive maintenance

Documenting the environmentTake the time to document your environment so that information is available in a disaster recovery scenario.

• Documenting the environment• Best practices• Backing up data• Preparing to use alternate BlackBerry Enterprise Servers

Data Details

server settings • host names• Microsoft Windows Server™ names• IP addresses

Firewall settings • connection details required by a BlackBerry Router in the DMZ• proxy configurations used by the BlackBerry Enterprise Server

BlackBerry wireless network connection credentials

• SRP address• SRP identifier• SRP authentication key

BlackBerry Enterprise Server implementation • whether the Attachment Service is on a separate server• which BlackBerry Enterprise Server is the Mobile Data Service push server• customized registry settings (for example, BES Alert, BlackBerry Controller)• IT policy settings

Firewall and proxy settings • configuration settings based on SRP connectivity

SRP connectivity information • MAPI profile information (server startup, access to Service Account Mailbox)• network access node (srp.xx.blackberry.net, proxy address)• port number (firewall access)• BlackBerry service account user profile

BlackBerry data • server name• SRP authentication key• SRP identifier

BlackBerry administration service account • account permissions• procedure for applying permissions

Installation • procedure• installation parameters• incremental changes made

Page 32: Maintenance Guide

32

Maintenance Guide

Best practices

Manage log file storageRetain only seven days of log files, depending on the logging levels used. Store older log files on a computer that does not have the BlackBerry Enterprise Server installed or include them as part of your daily backup. Use the Debug Log Maximum Daily File Age setting to delete files older than seven days. See “Change component logging settings” on page 13 for more information.

Perform BlackBerry Enterprise Server and user cleanupRun the HandheldCleanup tool to retrieve and update configuration information for BlackBerry Enterprise Servers and users. See “Retrieving and updating configuration information using the HandheldCleanup tool” on page 60 for more information.

Check MAPI subsystemUse the Mapisvc tool to verify that the MAPI subsystem is initialized. The MAPI profile is typically stored in the registry HKEY_CURRENT_USER\Software\Research In Motion\BlackBerry Enterprise Server\<component name>\MAPIProfile. An error occurs if a MAPI client is not already present on the server. The fixmapisvc tool enables the BlackBerry Enterprise Server installation to facilitate MAPI Profile creation and editing. See “Verifying that the MAPI subsystem is initialized using the Fixmapisvc tool” on page 61 for more information.

Design a disaster recovery programMethod Pros Cons

Backup/Restore • can also be used to migrate the BlackBerry Enterprise Server onto new hardware

• very resource-intensive• data is only as current as the last backup

Standby server • kept current using replication• allows for a more current restore than backup• useful for disaster recovery using a remote site

• requires many steps to get up and running and is dependent on the last replication time

• essentially the same approach as clustering, without its advantages

Sourceless move • move users from an unavailable BlackBerry Enterprise Server to an available one without needing to re-cradle or wirelessly activate the handhelds

• both BlackBerry Enterprise Servers must share the same configuration database

• Java™-based handhelds must be running Handheld Software version 4.0 and C++-based handhelds must be running Handheld Software version 2.7, otherwise the handhelds must be re-cradled

Page 33: Maintenance Guide

33

3: Preventive maintenance

Backing up dataBlackBerry handhelds maintain vital operating data in the Exchange Information Store in each user’s Microsoft Exchange mailbox. The data is stored in hidden BlackBerry folders. As long as Microsoft Exchange does not have information store problems, the BlackBerry information is safe in the event that the BlackBerry Enterprise Server becomes unavailable.

Backing up the BlackBerry Enterprise ServerPerform a full system backup regularly so that you can recover data in the event of system failure on the computer on which the BlackBerry Enterprise Server software is installed. It is critical that you back up the following data:

Backing up user mailboxes and hidden BlackBerry folders using Microsoft ExchangeBrick-level Microsoft Exchange backups back up individual user mailboxes, and is the most effective way to back up and restore BlackBerry hidden folders in Microsoft Exchange. As an additional level of redundancy, use the BlackBerry Backup utility to back up user’s BlackBerry data.

Backing up user data using the BlackBerry Backup toolThe BlackBerryBackup tool is a disaster-recovery tool that backs up and restores BlackBerry information contained in hidden folders from users’ mailboxes. You can perform a full backup of the BlackBerry Enterprise Server and its configuration information and user mailboxes using the tool.

1. At a command prompt, switch to the directory in which the installed utilities are stored.

2. Type BlackBerryBackup.exe followed by the parameters needed to configure the backup, in the following order: BlackBerryBackup.exe -b [-o <filename>] <-n/-r/-f> [-d] [-n] [-w] [-m] [-y]

See “Appendix D: Command prompt tools” on page 55 for more information on configuring the BlackBerryBackup tool.

Data Location

BlackBerry Enterprise Server registry settings HKLM\SOFTWARE\Research In Motion

Log files By default, log files are saved to C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs.

Note: If the default location is not used, use the location defined in the following registry value: HKLM\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\LoggingInfo\LogRoot.

Attachment Service executables and supporting files

By default, Attachment Service log files are saved to C:\Program Files\Research In Motion\BlackBerry Enterprise Server\AttachServer.

Microsoft Exchange user mailbox information and hidden BlackBerry folders

Microsoft Exchange Server

Note: Brick level backups only back up user mailbox information.

Note: The BlackBerryBackup tool does not back up information that is stored in the configuration database. You must back up the database to completely back up the BlackBerry Enterprise Server. See “Backing up the configuration database” on page 34 for more information.

Page 34: Maintenance Guide

34

Maintenance Guide

Backing up the configuration databaseThe configuration database is a critical part of BlackBerry Enterprise Server operations. Server and user administration, Mobile Data Service push, and PIM synchronization all depend on the information stored in the configuration database. See the BlackBerry Enterprise Server Troubleshooting Guide for more information on the impact of component failure.

Perform a full backup of the configuration database regularly so that you can recover data in the event of a failure.

Back up the configuration database using the BlackBerry Database Backup toolIf you are using MSDE 2000 for your configuration database, use the BlackBerry Database Backup tool provided with the BlackBerry Enterprise Server to perform a full backup of the database.

1. On the server where the configuration database is located, at the command prompt, switch to the Tools directory on the installation CD.

2. Type BlackBerryDBBackup.exe, followed by the parameters needed to configure the backup, in the following order: BlackBerryDBBackup.exe -d [-f] [-S] [-E | -U -P] [-p] [-?]

See “Backing up the configuration database using the BlackBerry Database Backup tool” on page 55 for more information.

3. Press Enter.

By default, the backup file is named <database name><YYYYMMDDHHMMSS>.bak.

Backing up the configuration database using SQLIf you are using SQL 2000 for your configuration database, use the tools provided with the software to perform backups.

Preparing to use alternate BlackBerry Enterprise Servers

You can minimize the impact of service or hardware failure by preparing alternate BlackBerry Enterprise Servers as failovers.

Create a standby BlackBerry Enterprise ServerYou can create a standby server that is configured identically to the active BlackBerry Enterprise Server and points to the same database. The standby server can be fully operational and running with the BlackBerry Services turned off.

Tip: You can copy this tool to your database server.

Page 35: Maintenance Guide

35

3: Preventive maintenance

Perform the following actions:

Action Procedure

Install the BlackBerry Enterprise Server.

1. Install the BlackBerry Enterprise Server on the standby server using the same version, including service pack and hotfix, as the primary server. See the BlackBerry Enterprise Server Installation Guide for more information.

2. During configuration, set the following settings to match those of the primary BlackBerry Enterprise Server:•BlackBerry Enterprise Server name•BlackBerry administration account•Configuration database name•SRP identifier and authentication key

Note: The MAPI profile does not have to be identical.

3. At the end of the configuration wizard, clear the Start Services check box.

4. If prompted, do not restart the server.

Warning: Do not start this BlackBerry Enterprise Server. You cannot have two simultaneous connections to the wireless network using the same SRP identifier. Attempts to do so make the SRP identifier unavailable.

Set the services to manual. 1. On the standby BlackBerry Enterprise Server, in the Windows Services pane, right-click BlackBerry Alert, and then click Properties.

2. Set the startup type to Manual, and then click OK.

3. Repeat steps 1 through 2 for all BlackBerry services.

Page 36: Maintenance Guide

36

Maintenance Guide

Page 37: Maintenance Guide

4

Restoring data and functionality

Moving users to another BlackBerry Enterprise Server

If one of your BlackBerry Enterprise Servers becomes unavailable, you can move users to another BlackBerry Enterprise Server before starting any recovery or failover process.

Perform a sourceless moveUnder normal conditions, the Move User task quickly moves a user from one BlackBerry Enterprise Server to another BlackBerry Enterprise Server. When a source BlackBerry Enterprise Server becomes unavailable, users can be moved manually to a functional destination server. The source BlackBerry Enterprise Server and the destination server must connect to the same configuration database and Microsoft Exchange server. The database and Microsoft Exchange server must also be running and available to complete the move. The destination BlackBerry Enterprise Server must also have sufficient capacity to accommodate the extra users.

1. In the BlackBerry Manager, in the left pane, click the source BlackBerry Enterprise Server.

2. In the User Name list, right click a user, and then click Move User.

3. In the list, click the destination BlackBerry Enterprise Server.

4. Click OK.

After the user is moved to the destination BlackBerry Enterprise Server, the user’s server name and location are updated in the configuration database. New service books are sent to the user’s handheld, so reactivation is not required.

• Moving users to another BlackBerry Enterprise Server• Restoring the BlackBerry Enterprise Server• Restoring the configuration database• Restoring remote components• Restoring functionality to handhelds

Note: Handhelds must have Handheld Software version 4.0 for Java-based handhelds or Handheld Software version 2.7 for C++-based handhelds installed to receive the new service books without reactivating the handheld. Users with earlier handheld versions must connect their handhelds to their computers for the changes to take effect.

Page 38: Maintenance Guide

38

Maintenance Guide

Restoring the BlackBerry Enterprise ServerThe following recovery methods use data made available through backup or replication. See “Backing up data” on page 33 or “Preparing to use alternate BlackBerry Enterprise Servers” on page 34 for more information.

Switch to a standby BlackBerry Enterprise ServerPerform the following actions:

Restore the BlackBerry Enterprise Server from backup on a new server

If the BlackBerry Enterprise Server that you are restoring was the Mobile Data Service push server, you can temporarily define another BlackBerry Enterprise Server as the push server. See the BlackBerry Enterprise Server Administration Guide for more information on defining a Mobile Data Service push server.

Perform the following actions:

Action Procedure

Configure access to the standby server.

1. Allow users access to the standby BlackBerry Enterprise Server.

2. If possible, deny users access to the primary server to prevent replication and, or save conflicts.

Start the standby server. Start the standby BlackBerry Enterprise Server so that it can initiate an SRP connection.

Set the services to automatic on the standby server.

1. On the standby BlackBerry Enterprise Server, in the Windows Services pane, right-click BlackBerry Alert, and then click Properties

2. Set the startup type to Automatic, and then click OK.

3. Repeat steps 1 through 2 for all BlackBerry services.

Start the services on the standby server.

On the standby BlackBerry Enterprise Server, start the services in the following order:

• BlackBerry Controller• BlackBerry Router• BlackBerry Dispatcher• all remaining services

Test the configuration settings. Open the BlackBerry Configuration Panel and test the following connections:

• SRP and BlackBerry Router connectivity• Database connectivity• SRP key and authentication• Attachment Service

Note: You can also use this procedure to migrate the BlackBerry Enterprise Server onto new hardware.

Action Procedure

Create a new server. Restore the BlackBerry Enterprise Server on a computer that•meets the BlackBerry Enterprise Server hardware minimum requirements•has the same host name as the BlackBerry Enterprise Server that it is replacing•has no existing BlackBerry Enterprise Server software installed

Page 39: Maintenance Guide

39

4: Restoring data and functionality

Restore BlackBerry Enterprise Server Microsoft Exchange componentsYou might need to restore or recreate certain Microsoft Exchange components if they become unavailable.

Restoring the configuration databaseIn the event of failure, you can recover data from a full database backup.

Restore the configuration database on the new server.

If applicable, restore the configuration database from the backed up version. See “Restoring the configuration database” on page 39 for more information.

Note: If the configuration database is on a remote server, the server must be available and you must be able to connect to the server during the installation process.

Restore BlackBerry user mailbox information.

Type BlackBerryBackup.exe, followed by the parameters needed to configure the backup in the following order: BlackBerryBackup.exe -b [-i filename] <-n/-r/-f> [-d] [-n] [-w] [-m] [-y].

See “Appendix D: Command line tools” on page 51 for more information on configuring the BlackBerryBackup tool.

Install the BlackBerry Enterprise Server on the new server.

1. Install the BlackBerry Enterprise Server on the new server using the same version, including service pack and hotfix, as the primary server. See the BlackBerry Enterprise Server Installation Guide for more information.

2. When completing the configuration wizard, use the same SRP identifier, SRP authentication key, and configuration database name as the primary server.

3. At the end of the configuration wizard, select the Start Services check box.

Warning: If the backup BlackBerry Enterprise Server is still running, do not start the services on the new BlackBerry Enterprise Server. You cannot have two simultaneous connections to the wireless network using the same SRP identifier and key. Attempts to do so make the SRP identifier unavailable.

Start the services on the new server.

1. On the new BlackBerry Enterprise Server, start the services in the following order:•BlackBerry Controller•BlackBerry Router•BlackBerry Dispatcher•all remaining services

2. If applicable, define the server as the Mobile Data Service push server.

3. Reconfigure any custom registry settings (for example, BES Alert or BlackBerry Controller).

Action Procedure

Scenario Reason Possible solution

The BlackBerry user mailbox becomes unavailable.

The Microsoft Exchange server is down or unavailable.

Restore the user on another Microsoft Exchange server, and then restore the user’s mailbox information.

The user mailbox has been deleted. Set the Deleted Item Retention option.

The MAPI profile becomes unavailable.

The MAPI profile does not exist on the server.

1. At the command prompt, run the Mapisvc tool.

2. Double-click setup.exe, and then associate a MAPI profile.

The Microsoft Exchange server is down or unavailable.

Configure a MAPI profile on another Microsoft Exchange server.

Page 40: Maintenance Guide

40

Maintenance Guide

Restore the database using the BlackBerry Database Restore toolIf you are using MSDE 2000 for your configuration database, you can use the BlackBerry Database Restore tool provided with the BlackBerry Enterprise Server software.

1. On the server where the configuration database is being restored, at the command prompt, switch to the Tools directory on the installation CD.

2. Type BlackBerryDBRestore, followed by the parameters needed to configure the restore, in the following order: BlackBerryDBRestore.exe -d [-f] [-S] [-E | -U -P] [-p] [-?].

See “Restoring the configuration database using the BlackBerry Database Restore tool” on page 56 for more information.

3. Press Enter.

4. After the restore is complete, use the BlackBerry Configuration Panel to connect the configuration database to the BlackBerry Enterprise Server. See “Assign the BlackBerry Enterprise Server to another database” on page 11 for more information.

Restore the database using SQL RestoreIf you are using SQL 2000 for your configuration database, you can use the tools provided with the software to perform a restore of the database.

After the restore is complete, use the BlackBerry Configuration Panel to connect the configurationdatabase to the BlackBerry Enterprise Server. See “Assign the BlackBerry Enterprise Server to anotherdatabase” on page 11 for more information.

Restoring remote componentsIf a remote component fails, either connect your BlackBerry Enterprise Server to a standby server or use the local component that is installed with the BlackBerry Enterpriser Server automatically.

Change the connection to the BlackBerry RouterWhen you change to a different BlackBerry Router, the BlackBerry Enterprise Server sends updated service books wirelessly, which include the routing information, to all handhelds.

1. On the taskbar, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Server Configuration.

2. On the BlackBerry Server tab, in the Router Host field, perform one of the following actions:

3. Click OK.

Tip: You can copy this tool to your database server.

Action Procedure

Connect the BlackBerry Enterprise Server to a standby remote BlackBerry Router.

Type the standby server name.

Use the BlackBerry Router installed locally. Type localhost.

Page 41: Maintenance Guide

41

4: Restoring data and functionality

Change the connection to the BlackBerry Attachment ServiceYou can set the BlackBerry Enterprise Server to connect to the Attachment Service installed locally, to a standby remote Attachment Service, or to an Attachment Service that is installed on a different BlackBerry Enterprise Server.

Allow the BlackBerry Enterprise Server to act as remote Attachment ServiceIf you want to connect to an Attachment Service on a different BlackBerry Enterprise Server, you must modify the Attachment Service settings to allow connections from remote BlackBerry Enterprise Servers.

1. Open regedit.exe.

2. In the left pane, browse to HKEY_LOCAL_MACHINE\Software\Research In Motion\BBattachServer\BBAttachBESExtension.

3. Click AllowRemoteServices and set the value to 1.

4. Restart the service.

Change the connection to the BlackBerry Attachment Service1. On the taskbar, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Server

Configuration.

2. On the BlackBerry Server tab, in the Attachment Host field, perform one of the following actions:

3. Click OK.

Restoring functionality to handhelds

Re-enable an unavailable handheldIf a user makes the handheld unavailable by typing an incorrect password the specified number of times, you can re-enable the handheld.

1. Connect the handheld to the administration computer on which the Handheld Configuration Tool is installed.

2. In the Handheld Configuration Tool, in the left pane, click Ports.

3. In the Connection list, click a connection.

4. Click Load Handheld.

Re-enable a handheld when the password is unknown1. In the BlackBerry Manager, in the left pane, click a server.

Action Procedure

Connect the BlackBerry Enterprise Server to a standby remote Attachment Service or to an Attachment Service on a different BlackBerry Enterprise Server.

Type the standby server name.

Use the Attachment Service installed locally. Type localhost.

Page 42: Maintenance Guide

42

Maintenance Guide

2. In the User Name list, right-click a user, and then click IT Admin > Set Password and Lock.

3. In the New Password and New Password Again fields, type a password that is 4 to 14 characters long.

4. Select the Set Owner Information as well check box.

5. In the Owner Name and Owner Information fields, type the information.

6. Click OK. You must wait for the command to be delivered to the handheld.

7. Type the new password on the handheld to unlock it and restore functionality.

Return a handheld to the factory default stateYou can return a handheld to its original state by erasing all applications and data that might have been loaded on the handheld.

1. Connect the handheld to the administration computer on which the Handheld Configuration Tool is installed.

2. In the Handheld Configuration Tool, in the left pane, click Ports.

3. In the Connection list, click a connection.

4. Click Nuke Handheld.

5. Click Yes.

6. In the left pane, click Ports.

7. From the Connection list, click a connection.

8. Click Load Handheld.

Warning: Do not use special characters when you create the password. The handheld does not accept special characters.

Warning: This procedure erases all data from the handheld. The data cannot be retrieved after the handheld is re-enabled.

Page 43: Maintenance Guide

Appendix A: Required third-party permissions

Microsoft Exchange permissions and privileges

The following table lists the permissions and privileges associated with the BlackBerry Enterprise Server. See the BlackBerry Enterprise Server Installation Guide for more information on creating the required permission settings.

• Microsoft Exchange permissions and privileges• Create SQL permissions and privileges

Activity Permissions Description

Install the BlackBerry Enterprise Server.

• Windows: Local administrator account with access to the remote database server, if applicable.

• Microsoft Exchange: The service account and mailbox (for example, BESAdmin) with the following permissions:•log on as service•local administrator•service account admin on Site and Configuration containers (Microsoft Exchange 5.5)•view only administrator with minimum access of Administrative Groups (Microsoft Exchange 2000/2003)•administer information store, send as, and receive as set at mailbox or server level (Microsoft Exchange 2000/2003)

Most BlackBerry services, and any applicable SQL authentication credentials, are installed using the administrator account.

Start the BlackBerry Manager on the same server.

• Windows: Local administrator account with access to the remote database server, if applicable.

• Microsoft Exchange: The service account and mailbox (for example, BESAdmin) with the administrative permissions listed in the preceding cell.

Start the BlackBerry Manager on a remote server.

• Windows: Local administrator account with access to the remote database server, if applicable.

• Microsoft Exchange: The service account and mailbox (for example, BESAdmin) with the following permissions:•local administrator•service account admin on site and configuration containers (Microsoft Exchange 5.5)•view only administrator with minimum access of Administrative Groups (Microsoft Exchange 2000/2003)•administer information store, send as, and receive as set at mailbox or server level (Microsoft Exchange 2000/2003)

Page 44: Maintenance Guide

44

Maintenance Guide

Create SQL permissions and privilegesSee the BlackBerry Enterprise Server Installation Guide for more information on creating the required permission settings.

Permissions Description

• SQL Server role: Server Administrators, Database Creators

• Database role: none

You require the Database Creator role to create the configuration database. You can remove the permission after the database is created.

Alternatively, a database administrator can create the database on a remote computer using the CreateDB tool before the BlackBerry Enterprise Server installation process.

• SQL Server role: Server Administrators• Database role: db_owner

You require the Server Administrator role to create and update the SQL scheduled tasks that are used to maintain the database. You can remove the permission after the database is populated; however, the permission is required for subsequent service pack or hotfix installations.

The administrator account that you use to install the BlackBerry Enterprise Server must be explicitly assigned the necessary permissions on the remote computer if it is not a System Administrator/Local Admin account (which has this authority by default).

• SQL Server role: none• Database role: rim_db_bes_server

The rim_db_bes_server role provides read/write access to the configuration database, enabling you to administer the BlackBerry Enterprise Server.

• SQL Server role: Server Administrators• Database role: db_owner

You must run the BlackBerry Configuration Panel after every installation or upgrade to complete database changes.

Note: Upgrading the database using the BlackBerry Configuration Panel is supported only with an existing version 4.0 or later database, or an empty database.

Page 45: Maintenance Guide

Appendix B: Default ports Warning: Use of these default ports by another application might result in service interruption.

Component Activity Connection type Default port

BlackBerry Attachment Service

incoming document submissions from/outgoing conversion results to attachment connector to Attachment Service

— 1900

incoming connections from/outgoing connections to Attachment Service tab of BlackBerry Configuration Panel

— 1999

incoming document queries from/outgoing conversion results of large attachments to attachment connector to Attachment Service

— 2000

BlackBerry Controller

incoming syslog connections from BlackBerry Messaging Agents

UDP 4070

outgoing logger connections to BlackBerry Messaging Agents

UDP port provided by the BlackBerry Messaging Agents

BlackBerry Dispatcher

incoming data connections, using BIPP, from BlackBerry Messaging Agents

TCP 5096

incoming data connections, using WART, from

•BlackBerry Mobile Data Service•BlackBerry Synchronization Service •BlackBerry Policy Service

TCP 3200

Note: After upgrading from version 3.6, the default might be 3201 or 3202.

outgoing data connection, using SRP, to BlackBerry Router

TCP 3101

BlackBerry Messaging Agent

outgoing data connection, using SRP, to BlackBerry Dispatcher

TCP 5096

incoming logger connections from

•BlackBerry Controller •CalHelpers

UDP first unused port in the range of 4085 to 4499

outgoing syslog connection to BlackBerry Controller UDP 4070

outgoing syslog connection to SNMP Agent UDP 4071

BlackBerry Mobile Data Service

incoming HTTP listener ports for

•http•https; if access control is enabled for push

— 8080 (http)

8443 (https)

outgoing data connection to BlackBerry Dispatcher TCP 3200

Note: After upgrading from version 3.6, the default might be 3201 or 3202.

outgoing syslog connection to SNMP Agent UDP 4071

BlackBerry Mobile Policy Service

incoming data connection from/outgoing data connection to BlackBerry Dispatcher

— 3200

BlackBerry Router incoming data connection from BlackBerry Dispatcher TCP 3101

outgoing data connection to BlackBerry Messaging Agent

TCP 3101

incoming data connections from handhelds using BlackBerry Handheld Manager for serial bypass

TCP 4101

Page 46: Maintenance Guide

46

Maintenance Guide

BlackBerry Synchronization Service

incoming data connection from/outgoing data connection to BlackBerry Dispatcher

— 3200

CalHelper outgoing logger connections to BlackBerry Messaging Agents

UDP port provided by BlackBerry Messaging Agents

SNMP Agent incoming syslog connections from BlackBerry Messaging Agents

UDP 4071

Component Activity Connection type Default port

Page 47: Maintenance Guide

Appendix C: SNMP values

Version 1The values in the following table represent global statistics counters from the first BlackBerry Enterprise Server session started on the system and are maintained for backward compatibility with MIB version 1.

• Version 1• Configuration• System health• Messaging server health• User health• BlackBerry Enterprise Server events

Notes: The values in the table are persistent (they do not reset at startup).

The statistics in the table include only messages that are routed through the BlackBerry Enterprise Server (for example, they do not include PIN or SMS messages).

Value Description Object identifier

besSysHealthV1MsgsPending the total number of messages that are queued for delivery to handhelds

1.3.6.1.4.1.3530.5.25.1.202

besSysHealthV1TotalMsgsSent the total number of messages that were sent from handhelds

1.3.6.1.4.1.3530.5.25.1.203

besSysHealthV1TotalMsgsReceived the total number of messages that were delivered to handhelds

1.3.6.1.4.1.3530.5.25.1.204

besSysHealthV1TotalMsgsExpired the total number of messages that have expired without being delivered to handhelds

1.3.6.1.4.1.3530.5.25.1.205

besSysHealthV1TotalMsgsFiltered the total number of messages that have been filtered 1.3.6.1.4.1.3530.5.25.1.206

besSysHealthV1MsgsSentPerMin the total number of messages that were sent from handhelds each minute

1.3.6.1.4.1.3530.5.25.1.207

besSysHealthV1MsgsRecvdPerMin the total number of messages that were delivered to handhelds each minute

1.3.6.1.4.1.3530.5.25.1.208

besSysHealthV1SRPConnectState the state of the BlackBerry Enterprise Server connection to the wireless network

1.3.6.1.4.1.3530.5.25.1.209

version the version number of the BlackBerryServer.mib file 1.3.6.1.4.1.3530.5.1.0

besTotMsgsPending the total number of messages that are queued for delivery to handhelds

1.3.6.1.4.1.3530.5.2.0

besTotMsgsSent the total number of messages that were sent from handhelds

1.3.6.1.4.1.3530.5.3.0

besTotMsgsRecvd the total number of messages that were delivered to handhelds

1.3.6.1.4.1.3530.5.4.0

besTotMsgsXpired the total number of messages that have expired without being forwarded to handhelds

1.3.6.1.4.1.3530.5.5.0

besTotMsgsFiltered the total number of messages that have been filtered 1.3.6.1.4.1.3530.5.6.0

besTotMsgsSentPerMin the total number of messages that were sent from handhelds each minute; this value is averaged from the last 10 minutes of processing

1.3.6.1.4.1.3530.5.7.0

Page 48: Maintenance Guide

48

Maintenance Guide

ConfigurationThe values in the following table represent the Configuration container for BlackBerry Enterprise Servers that are running on the system.

besTotMsgsRecvdPerMin the total number of messages that were delivered to handhelds each minute; this value is averaged from the last 10 minutes of processing

1.3.6.1.4.1.3530.5.8.0

besNumServerInfoAvailable the number of BlackBerry Enterprise Servers that are installed on the system for which information is exposed and currently available using SNMP

1.3.6.1.4.1.3530.5.15.0

Value Description Object identifier

Note: The statistics in the table include only messages that are routed through the BlackBerry Enterprise Server (for example, they do not include PIN or SMS messages).

Value Description Object identifier

besConfigServerInstance the BlackBerry Enterprise Server instance number (1...n) 1.3.6.1.4.1.3530.5.20.1.1

besConfigServerName the BlackBerry Enterprise Server name 1.3.6.1.4.1.3530.5.20.1.2

besConfigVersionString the BlackBerry Enterprise Server version information 1.3.6.1.4.1.3530.5.20.1.10

besConfigReleaseMaj indicates whether this is a major release 1.3.6.1.4.1.3530.5.20.1.11

besConfigReleaseMin indicates whether this is a minor release 1.3.6.1.4.1.3530.5.20.1.12

besConfigReleaseServicePack indicates whether this is a service pack release 1.3.6.1.4.1.3530.5.20.1.13

besConfigReleaseBuild the build number 1.3.6.1.4.1.3530.5.20.1.14

besConfigLicenceTotal the total number of end-user licenses that are installed on the BlackBerry Enterprise Server

1.3.6.1.4.1.3530.5.20.1.20

besConfigLicenceUsed the total number of end-user licenses that are currently in use on the BlackBerry Enterprise Server

1.3.6.1.4.1.3530.5.20.1.21

besConfigLicenceRemaining the total number of available end-user licenses that are not currently in use

1.3.6.1.4.1.3530.5.20.1.22

besConfigServerUID the UID (also SRP identifier) of this BlackBerry Enterprise Server instance; the UID uniquely identifies the BlackBerry Enterprise Server to the wireless network

1.3.6.1.4.1.3530.5.20.1.30

besConfigSystemAttendant the SMTP address that was defined to send and receive notifications that are sent from the BlackBerry Enterprise Server administration application

1.3.6.1.4.1.3530.5.20.1.40

besConfigSRPHost the SRP host (also SRP address) that is configured for the BlackBerry Enterprise Server; the SRP host is the BlackBerry Enterprise Server connection to the wireless network

1.3.6.1.4.1.3530.5.20.1.50

besConfigSRPPort the port that the BlackBerry Enterprise Server uses to establish outbound connectivity to the wireless network

1.3.6.1.4.1.3530.5.20.1.51

besConfigAutoBCCEnabled indicates whether messages that are sent from handhelds are automatically blind carbon copied (AutoBCC) to an address; 1 means that the option is enabled, 0 means that the option is not enabled

1.3.6.1.4.1.3530.5.20.1.60

besConfigAutoBCCAddress if the AutoBCC feature is enabled, indicates the address that is configured to receive blind carbon copies; an empty value is returned if AutoBCC is not enabled on the BlackBerry Enterprise Server

1.3.6.1.4.1.3530.5.20.1.61

Page 49: Maintenance Guide

49

Appendix C: SNMP values

System healthThe values in the following table represent the System Health container for BlackBerry Enterprise Servers that are running on the system.

besConfigForceSaveInSentEnabled indicates whether all messages that are sent from handhelds are saved in the Sent folder, regardless of users’ desktop software settings

1.3.6.1.4.1.3530.5.20.1.70

besConfigWirelessEmailRecoEnabled indicates whether wireless message reconciliation support is enabled on the BlackBerry Enterprise Server

1.3.6.1.4.1.3530.5.20.1.80.

Value Description Object identifier

Note: The statistics in the table include only messages that are routed through the BlackBerry Enterprise Server (for example, they do not include PIN or SMS messages).

Value Description Object identifier

besSysHealthServerInstance the instance number of the BlackBerry Enterprise Server (1..n)

1.3.6.1.4.1.3530.5.25.1.1

besSysHealthSrpConnectedState indicates whether the BlackBerry Enterprise Server is connected to the wireless network

1.3.6.1.4.1.3530.5.25.1.10

besSysHealthSrpLastConnectDate the date and time that the BlackBerry Enterprise Server last connected to the wireless network successfully

1.3.6.1.4.1.3530.5.25.1.11

besSysHealthSrpReconnectSuccess the number of times that the BlackBerry Enterprise Server has reconnected to the wireless network successfully since startup

1.3.6.1.4.1.3530.5.25.1.12

besSysHealthSrpReconnectsFail the number of times that the BlackBerry Enterprise Server has attempted, but failed, to connect to the wireless network since startup

1.3.6.1.4.1.3530.5.25.1.13

besSysHealthSrpTotalSecNotConnected

the total number of seconds that the BlackBerry Enterprise Server has not been connected to the wireless network since startup

1.3.6.1.4.1.3530.5.25.1.14

besSysHealthSrpLastErrorText the error text associated with the last failed connection attempt

1.3.6.1.4.1.3530.5.25.1.15

besSysHealthSrpLastErrorTime the date and time of the last connection error 1.3.6.1.4.1.3530.5.25.1.16

besSysHealthMsgTotalProc the total number of messages that the BlackBerry Enterprise Server has processed since startup; this total includes messages that were sent to the handheld, sent from the handheld, or not forwarded to the handheld because they were filtered

1.3.6.1.4.1.3530.5.25.1.20

besSysHealthMsgToHandheld the total number of messages that passed the filter criteria and were forwarded to handhelds; this total does not include calendar items

1.3.6.1.4.1.3530.5.25.1.21

besSysHealthMsgFromHandheld the total number of messages that were sent from handhelds since startup; this total does not include calendar items

1.3.6.1.4.1.3530.5.25.1.22

besSysHealthMsgFilteredByUser the total number of messages to which the BlackBerry Enterprise Server applied user-defined filters and did not forward to handhelds since startup

1.3.6.1.4.1.3530.5.25.1.23

besSysHealthMsgFilteredByGlobal the total number of messages to which the BlackBerry Enterprise Server applied global filters and did not forward to handhelds since startup

1.3.6.1.4.1.3530.5.25.1.24

Page 50: Maintenance Guide

50

Maintenance Guide

besSysHealthMsgPending the total number of messages that are pending delivery to handhelds

1.3.6.1.4.1.3530.5.25.1.25

besSysHealthMsgExpired the total number of messages that expired without being delivered to handhelds since startup

1.3.6.1.4.1.3530.5.25.1.26

besSysHealthMsgErrors the total number of messages that were non-deliverable to handhelds because of an error

1.3.6.1.4.1.3530.5.25.1.27

besSysHealthMsgMoreRequests the total number of MORE requests that were issued from handhelds since startup

1.3.6.1.4.1.3530.5.25.1.28

besSysHealthCalUsersOTACEnabled the total number of users for whom wireless calendar synchronization is enabled

1.3.6.1.4.1.3530.5.25.1.40

besSysHealthCalEventToHandheld the total number of calendar events that were sent to handhelds

1.3.6.1.4.1.3530.5.25.1.41

besSysHealthCalEventFromHandheld

the total number of calendar events that were sent from handhelds

1.3.6.1.4.1.3530.5.25.1.42

besSysHealthWERUsersEnabled the total number of users who are enabled for wireless message reconciliation

1.3.6.1.4.1.3530.5.25.1.50

besSysHealthWERRequestsToHandheld

the total number of wireless message reconciliation events that were sent to handhelds

1.3.6.1.4.1.3530.5.25.1.51

besSysHealthWERRequestsFromHandheld

the total number of wireless message reconciliation events that were sent from handhelds

1.3.6.1.4.1.3530.5.25.1.52

besSysHealthMdsDeviceConnections

the number of handheld-initiated Mobile Data Service connections that were made since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.60

besSysHealthMdsPushConnections

the number of push server connections that were made since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.61

besSysHealthMdsTotalBytesFromDevices

the total size (in bytes) of Mobile Data Service data that was sent from all handhelds since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.62

besSysHealthMdsMaxPacketSizeFromDevice

the largest packet size of Mobile Data Service data (in bytes) that was sent from a handheld since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.63

besSysHealthMdsAvgPacketSizeFromDevice

the average packet size (in bytes) of Mobile Data Service data that was sent from handhelds since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.64

besSysHealthMdsTotalBytesToDevice

the total size (in bytes) of push data that was sent from the Mobile Data Service to handhelds since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.65

besSysHealthMdsMaxPacketSizeToDevice

the largest packet size (in bytes) of push data that was sent from the Mobile Data Service to handhelds since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.66

besSysHealthMdsAvgPacketSizeToDevice

the average packet size (in bytes) of push data that was sent from the Mobile Data Service to handhelds since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.67

besSysHealthMdsRefusedPackets

the number of packets, which the wireless network refused, that were sent from the Mobile Data Service (using the BlackBerry Enterprise Server) since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.68

besSysHealthMdsInvalidPackets

the number of incorrect packets that were received by the Mobile Data Service since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.69

Value Description Object identifier

Page 51: Maintenance Guide

51

Appendix C: SNMP values

Messaging server healthThe values in the following table represent the list of messaging servers and statistics and performance values related to each particular messaging server.

User healthThe values in the following table represent the list of user configuration, statistics, and performance values related to each user and handheld on a BlackBerry Enterprise Server.

besSysHealthMdsConnectionSuccess

the number of successful connections that were initiated by the Mobile Data Service to another address or service since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.70

besSysHealthMdsConnectionFailure

the number of unsuccessful connections that were initiated by the Mobile Data Service to another address and, or service in this BlackBerry Enterprise Server session

1.3.6.1.4.1.3530.5.25.1.71

besSysHealthMdsConnectionTruncated

the number of truncated connections that were encountered by the Mobile Data Service since BlackBerry Enterprise Server startup

1.3.6.1.4.1.3530.5.25.1.72

Value Description Object identifier

Value Description Object identifier

besMailServerHealthServerInstance the server instance ID of the BlackBerry Enterprise Server 1.3.6.1.4.1.3530.5.26.1.1

besMailServerHealthServerId the server instance ID of the messaging server 1.3.6.1.4.1.3530.5.26.1.2

besMailServerHealthServerName the messaging server name 1.3.6.1.4.1.3530.5.26.1.3

besMailServerHealthTotalUsers the number of users that have accounts on this messaging server

1.3.6.1.4.1.3530.5.26.1.10

besMailServerHealthFailedConn10min

the number of failed connection attempts that the BlackBerry Enterprise Server made to this messaging server in the last 10 minutes

1.3.6.1.4.1.3530.5.26.1.12

Note: The statistics in the table include only messages that are routed through the BlackBerry Enterprise Server (for example, they do not include PIN or SMS messages).

Value Description Object identifier

besUserHealthServerInstance the instance ID of the user’s associated BlackBerry Enterprise Server

1.3.6.1.4.1.3530.5.30.1.1

besUserHealthUserId the user’s instance ID 1.3.6.1.4.1.3530.5.30.1.2

besUserHealthUserName the user name 1.3.6.1.4.1.3530.5.30.1.3

besUserHealthLastErrorText the error text that was returned the last time that an operation for this user failed

1.3.6.1.4.1.3530.5.30.1.10

besUserHealthLastErrorTime the date and time of the last error for this user 1.3.6.1.4.1.3530.5.30.1.11

besUserHealthDeviceNetwork the wireless network on which the user’s handheld operates

1.3.6.1.4.1.3530.5.30.1.20

besUserHealthDevicePIN the PIN that is associated with the user’s handheld 1.3.6.1.4.1.3530.5.30.1.21

besUserHealthDeviceInCradle indicates whether the user’s handheld is connected to the BlackBerry Desktop Software

1.3.6.1.4.1.3530.5.30.1.22

besUserHealthNumRedirectedFolders

the number of redirected folders that the user has configured

1.3.6.1.4.1.3530.5.30.1.30

Page 52: Maintenance Guide

52

Maintenance Guide

besUserHealthSaveInSent indicates whether the user has enabled the Save in Sent option in the Desktop Software

1.3.6.1.4.1.3530.5.30.1.31

besUserHealthRedirectEnabledOnDesktop

indicates whether the user has selected the Desktop Software option to redirect incoming messages to the handheld

1.3.6.1.4.1.3530.5.30.1.32

besUserHealthDisableWhileInCradle indicates whether the user has selected the Desktop Software option to turn off redirection while the handheld is connected to the computer

1.3.6.1.4.1.3530.5.30.1.33

besUserHealthFullyConfigured indicates whether the user’s handheld is fully configured with a PIN and encryption key

1.3.6.1.4.1.3530.5.30.1.34

besUserHealthEnabled indicates whether the user is currently enabled on the BlackBerry Enterprise Server

1.3.6.1.4.1.3530.5.30.1.35

besUserHealthMsgTotalProc the total number of messages that the BlackBerry Enterprise Server has processed for this user since startup; this total includes messages that were sent to the handheld, sent from the handheld, or not forwarded to the handheld because they were filtered

1.3.6.1.4.1.3530.5.30.1.40

besUserHealthMsgToHandheld the total number of messages that passed the filter criteria and were forwarded to the user’s handheld; this total does not include calendar items

1.3.6.1.4.1.3530.5.30.1.41

besUserHealthMsgFromHandheld the total number of messages that were sent from the user’s handheld in this session; this total value does not include calendar items

1.3.6.1.4.1.3530.5.30.1.42

besUserHealthMsgFiltered the total number of messages to which the BlackBerry Enterprise Server applied filters and did not forward to the user’s handheld in this session

1.3.6.1.4.1.3530.5.30.1.43

besUserHealthMsgPending the total number of messages that are pending delivery to the user’s handheld

1.3.6.1.4.1.3530.5.30.1.44

besUserHealthMsgExpired the total number of messages that expired without being delivered to the user’s handheld in this session

1.3.6.1.4.1.3530.5.30.1.45

besUserHealthMsgErrors the total number of messages that were non-deliverable to the user’s handheld because of an error

1.3.6.1.4.1.3530.5.30.1.46

besUserHealthMsgMoreRequests the total number of MORE requests that were issued from the user’s handheld

1.3.6.1.4.1.3530.5.30.1.47

besUserHealthMsgForwardedFromDevice

the total number of messages that the user has forwarded from the handheld

1.3.6.1.4.1.3530.5.40.1.48

besUserHealthMsgRepliedToWithText

the total number of messages that were replies with text from the user’s handheld

1.3.6.1.4.1.3530.5.30.1.49

besUserHealthLastTimeInCradle the date and time that the user last connected the handheld to the computer

1.3.6.1.4.1.3530.5.30.1.60

besUserHealthLastInteractionWithDevice

the date that the BlackBerry Enterprise Server and the user’s handheld last interacted

1.3.6.1.4.1.3530.5.30.1.61

besUserHealthLastMessageForwarded

the date and time that the last message or calendar item was sent to the user’s handheld

1.3.6.1.4.1.3530.5.30.1.62

besUserHealthLastKeyDateGenerated

the date and time that the user last generated an encryption key

1.3.6.1.4.1.3530.5.30.1.63

besUserHealthAvgKBForwarded the average size of messages (in KB) that the user forwarded from the handheld; for example, if the user receives a message with a 5 MB attachment and forwards it from the handheld, the value is 5120 KB

1.3.6.1.4.1.3530.5.30.1.70

Value Description Object identifier

Page 53: Maintenance Guide

53

Appendix C: SNMP values

BlackBerry Enterprise Server eventsThe values in the following table represent event-driven traps that notify the server management application when an event takes place in the system.

besUserHealthAvgKBReplyWithText the average size of messages (in KB) that the user replied to with text from the handheld; for example, if the user receives a message with a 5 MB attachment and replies to it with text on the handheld, the value is 5120 KB

1.3.6.1.4.1.3530.5.30.1.71

besUserHealthAvgLatencyInSecLast10Msg

for the last 10 messages sent to the user’s handheld, the average length of time (in seconds) between the message arriving on the messaging server and the DELIVERED message appearing on the user’s handheld

1.3.6.1.4.1.3530.5.30.1.72.1.1

besUserHealthCalOTAEnabled indicates whether wireless calendar synchronization is enabled for the user

1.3.6.1.4.1.3530.5.30.1.80

besUserHealthCalEventToHandheld the total number of calendar items that were sent to the user’s handheld

1.3.6.1.4.1.3530.5.30.1.81

besUserHealthCalEventFromHandheld

the total number of calendar events that the user sent from the handheld

1.3.6.1.4.1.3530.5.30.1.82

besUserHealthWirelessEmailRecoEnabled

indicates whether the user is enabled for wireless message reconciliation

1.3.6.1.4.1.3530.5.30.1.90

besUserHealthWERRequestsToHandheld

the total number of wireless message reconciliation events that were sent to the user’s handheld

1.3.6.1.4.1.3530.5.30.1.91

besUserHealthWERRequestsFromHandheld

the total number of wireless message reconciliation events that were sent from the user’s handheld

1.3.6.1.4.1.3530.5.30.1.92

Value Description Object identifier

Value Description Object identifier

besSRPConnectEvent indicates whether the BlackBerry Enterprise Server is connected to the wireless network, as indicated by the last integer in the OID

1.3.6.1.4.1.3530.5.1.0 - specific trap #1 (connected) and #2 (disconnected)

besHungThreadEvent indicates that a BlackBerry Enterprise Server non-responsive thread has been detected

1.3.6.1.4.1.3530.5.3.0 - specific trap #3

besMailServerDownEvent indicates whether the messaging server is running, as indicated by the last integer in the OID; this event occurs if more than one user (or one user if there is only one) on the messaging server receives more than one non-access control error while connecting to the messaging server

1.3.6.1.4.1.3530.5.5.0 - specific trap #5 (mail server down) and #6 (mail server up)

besMDStoBESConnectionEvent indicates whether the Mobile Data Service is connected to the BlackBerry Enterprise Server, as indicated by the last integer in the OID

1.3.6.1.4.1.3530.5.7.0 - specific trap #7 (connected) and #8 (disconnected)

besMDSStartStopEvent indicates whether the Mobile Data Service is started, as indicated by the last integer in the OID

1.3.6.1.4.1.3530.5.11.0 - specific trap #11 (started) and #12 (stopped)

besMDStoDBConnectionEvent indicates whether the Mobile Data Service is connected to the database, as indicated by the last integer in the OID

1.3.6.1.4.1.3530.5.13.0 - specific trap #13 (connected) and #14 (disconnected)

besCriticalEvent indicates that an event has been logged with a 1xxxx or 5xxxx (critical) event ID

1.3.6.1.4.1.3530.5.21.0 - specific trap #21

Page 54: Maintenance Guide

54

Maintenance Guide

Page 55: Maintenance Guide

Appendix D: Command prompt tools

Backing up the configuration database using the BlackBerry Database Backup tool

If you are using MSDE 2000 for your configuration database, you can use the BlackBerry Database Backup tool provided with the BlackBerry Enterprise Server software to perform a full backup of the database. By default, this backup file is named <database name><YYYYMMDDHHMMSS>.bak.

Run the BlackBerry Database Backup tool1. On the server where the configuration database is located, at the command prompt, switch to the

Tools folder on the installation CD.

2. Type BlackBerryDBBackup.exe, followed by the parameters needed to configure the backup, in the following order: BlackBerryDBBackup -d [-f] [-S] [-E | -U -P] [-p].

3. Configure BlackBerryDBBackup using the following parameters:

• Backing up the configuration database using the BlackBerry Database Backup tool• Restoring the configuration database using the BlackBerry Database Restore tool• Backing up and restoring BlackBerry data using the BlackBerry Backup and Restore tool• Creating the configuration database using the CreateDB tool• Migrating users using the BESMigration tool• Retrieving and updating configuration information using the HandheldCleanup tool• Verifying that the MAPI subsystem is initialized using the Fixmapisvc tool• Verifying BlackBerry Enterprise Server permissions using the IEMSTest tool• Testing the BlackBerry Enterprise Server SRP connection using the BBSRPTest tool• Repairing the registration of the performance monitor file using the BBPerfmoninstall tool• Verifying Mobile Data Service data consistency using the DBConsistency tool• Controlling access to administration functions using the SetAdminKey tool

Parameter Procedure

-d Type the database name.

-f Type the folder in which the backup file is saved. By default, this is set to the current location.

Note: If you specify a different location, the folder must already exist.

-S Type the name of the server where the database is located. By default, this is set to the local server.

-E Specify if Windows authentication is used to connect to the database. By default, this is set to False.

Note: If you want to use SQL authentication, omit this parameter from the statement and provide the SQL credentials.

Page 56: Maintenance Guide

56

Maintenance Guide

4. Press Enter.

ExampleC:\Documents and Settings\Desktop\CDLayout\tools>BlackBerryDbBackup -d BESMgmt -f c:\DB_backup_folder -U sqlusername -P sqlpasswordConnecting to SQLServer...Connected.

Backing up to file [c:\DB_backup_folder\BESMgmt_20040512122125.bak]

Percent done: 31 @ Mon May 12 12:21:25 2004Percent done: 62 @ Mon May 12 12:21:25 2004Percent done: 93 @ Mon May 12 12:21:25 2004Percent done: 100 @ Mon May 12 12:21:25 2004

Backup Completed @ Mon May 12 12:21:25 2004[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE successfully processed 385 pages in 0.743 seconds (4.238 MB/sec).

Restoring the configuration database using the BlackBerry Database Restore tool

If you are using MSDE 2000 for your configuration database, you can use the BlackBerry Database Restore tool provided with the BlackBerry Enterprise Server software to restore the configuration database.

Run the BlackBerry Database Restore tool1. On the server where the configuration database is located, at the command prompt, switch to the

Tools folder on the installation CD.

2. Type BlackBerryDBRestore, followed by the parameters needed to configure the restore, in the following order: BlackBerryDBRestore -d [-f] [-S] [-E | -U -P] [-p].

3. Configure BlackBerryDBRestore.exe using the following parameters:

-U Type the SQL authentication user name. By default, this is set to System Administrator.

Note: If you do not want to use the System Administrator account, you must use an account with SQL Server Administrator and Database Owner permissions.

-P Type the SQL authentication password. By default, this is blank.

-p Type the interval at which you want progress reported. By default, this is set to 10%.

Parameter Procedure

Parameter Procedure

-d Type the database name.

Note: You must use the same database name for restore that you used for backup. You cannot use this tool to change a database name.

-f Type the name of the backup file.

-S Type the name of the server where the database is located. By default, this is set to the local server.

Page 57: Maintenance Guide

57

Appendix D: Command prompt tools

4. Press Enter.

ExampleC:\Documents and Settings\Desktop\CDLayout\tools>BlackBerryDbRestore -d BESMgmt -f c:\DB_backup_folder\BESMgmt_20040512122125.bak -U sqlusername -P sqlpasswordConnecting to SQLServer...Connected.

Restore starting...Percent done: 10 @ Wed May 12 12:21:26 2004Percent done: 20 @ Mon May 12 12:21:26 2004Percent done: 31 @ Mon May 12 12:21:26 2004Percent done: 41 @ Mon May 12 12:21:26 2004Percent done: 52 @ Mon May 12 12:21:26 2004Percent done: 60 @ Mon May 12 12:21:26 2004Percent done: 70 @ Mon May 12 12:21:26 2004Percent done: 81 @ Mon May 12 12:21:26 2004Percent done: 91 @ Mon May 12 12:21:26 2004Percent done: 100 @ Mon May 12 12:21:26 2004

Restore Completed @ Mon May 12 12:21:26 2004[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE successfully processed 385 pages in 0.536 seconds (5.875 MB/sec).

Backing up and restoring BlackBerry data using the BlackBerry Backup and Restore tool

Run the BlackBerryBackup toolUse the following parameters to configure the BlackBerryBackup tool:

-E Specify if Windows authentication is used to connect to the database. By default, this is set to False.

Note: If you want to use SQL authentication, omit this parameter from the statement and provide the SQL credentials.

-U Type the SQL authentication user name. By default, this is set to System Administrator.

Note: If you do not want to use the System Administrator account, you must use an account with SQL Server Administrator and Database Owner permissions.

-P Type the SQL authentication password. By default, this is blank.

-p Type the interval at which you want progress reported. By default, this is set to 10%.

Parameter Procedure

Note: Brackets [ ] around a flag indicate a mandatory flag; angle brackets <> around a flag indicate an optional flag.

Commands Description

-b [-o filename/-i filename] <-n/-r/-f> performs a backup/restore on the entire BlackBerry Enterprise Server (and all its users)

-u [-o filename/-i filename] <-d/-n> performs a backup/restore on a single user

Page 58: Maintenance Guide

58

Maintenance Guide

The following table lists examples of commands that use values for file and server name variables:

Creating the configuration database using the CreateDB tool

Use the CreateDB tool to create the configuration database. The details of the installation are written to a log file. By default, this log file is named DBInstallV<YYMMDDHHMMSS>.log.

Configure the database using the BESMgmt.cfg file1. On any BlackBerry Enterprise Server, at the command prompt, switch to the Database folder on the

installation CD.

2. Open BESMgmt.cfg.

-r [-o filename/-i filename] performs a backup/restore on the BlackBerry Enterprise Server configuration information; the -r flag can also be used in conjunction with the -b flag

-p [-i filename] [-o filename] prints user information to file from the specified input file

-o filename specifies the file to back up information to

-i filename specifies the file from which you restore information

-f filename specifies a backup file containing a list of users; the first line must be the number of users in the file; each user must appear on a separate line, and the last character must be a new line character

-d specifies the display name of the user whose information data is to be backed up/restored. If the display name is not provided, the user is prompted for it; the -d flag can only be used with the -u flag

-n specifies the BlackBerry Enterprise Server name (it can be used with all flags except -p). If the name is not provided, the user is prompted for it

-w specifies the password required to read or restore the file; if the password is not provided, the user is prompted for it

-m specifies the MAPI profile name used for the BlackBerry backup/restore utility; if the MAPI profile name is not provided, the user is prompted for it

-y specifies the BlackBerry backup/restore utility to always overwrite an output file if it exists; if this command is not specified, the user is prompted to overwrite output files

-v uses the user mailbox information to overwrite existing user information that might already exist

Note: If you do not specify -v, you are prompted to overwrite user information for each user. Type A to overwrite user information for all users.

Commands Description

Examples Description

-b -o backup.txt This command example performs a backup of an entire BlackBerry Enterprise Server to an output file called backup.txt.

-u -i user1.txt This command example loads a single user from an input file called user1.txt.

-r -i bes.txt -n "Test BES" This command example loads the BlackBerry Enterprise Server configuration information from an input file called bes.txt into a server called Test BES.

-p -i bes.txt -o print_bes.txt This command example creates a printable version of the data in an input file called bes.txt and outputs it to a file called print_bes.txt.

Page 59: Maintenance Guide

59

Appendix D: Command prompt tools

3. Configure the file using the following commands:

4. Save the file to the computer and close it.

Run the CreateDB tool1. On any server, at the command prompt, switch to the database directory on the installation CD.

2. Type CreateDB.exe <path>BESMgmt.cfg.

Command Procedure Default

Database_name Type the database name. -

CMD Specify the type of database action to perform.• Install (default): creates a new database• Migrate: migrates an existing database to the most recent

version• Restore: restores a previously backed up database from the

RESTORE_FILENAME• UpdateData: obtains the latest data values applied after the

schema change

Note: If you are upgrading from 3.6, you can only use UpdateData on a database after you perform the Install or Migrate action on the database.

Install

Verbose Set to True to include information and error messages in the log file.

False

Version Specify the database version to create and, or migrate to.• 3.5• 3.6• 4.0

4.0

Create Set to False if you do not want to create a database.

Note: The CreateDB tool ignores this setting in a database migration.

True

Backup Set to True to back up the existing database. False

Drop Set to True to drop the existing database.

Note: This setting is ignored in a database migration.

False

Server Specify the BlackBerry Enterprise Server on which to install the database.

Local

Userid

Password

Specify the user name and password to use to connect to the BlackBerry Enterprise Server.

Note: If you are using SQL authentication, you must use an account with SQL Server Administrator and Database Creator permissions.

User running the program file

Stop Specify whether the process should stop if an error is encountered. True

Script_root Specify the path to the DBInstallScripts directory. Same root as createdb.exe

Log_dir Specify the path to the directory in which to create log files. Same root as createdb.exe

Timestamp Set to False to remove the time stamp (HHMMSS) from log files. True

DBMS Specify which database management system to use. SQL

Db_file_dir Specify the directory in which to save the database files. This directory must already exist.

Same root as createdb.exe

Backup_dir Specify the directory in which to save the database backup. This directory must already exist.

Same root as createdb.exe

Restore_filename Specify the file to use for a database restore.

Note: If more than one backup file exists, the configuration database uses the most current version.

<database location>\DatabaseNameBKUP.dat

Generate_execute Set to False to generate, but not execute, the SQL files. True

Page 60: Maintenance Guide

60

Maintenance Guide

3. Press Enter.

Migrating users using the BESMigration toolUse the BESMigration tool to migrate multiple instances of the BlackBerry Enterprise Server on a single computer to one single instance. Versions of the BlackBerry Enterprise Server earlier than version 4.0 supported multiple instances of the BlackBerry Enterprise Server on a single computer. BlackBerry Enterprise Server version 4.0 supports only a single instance of the BlackBerry Enterprise Server on a single computer.

Run the BESMigration tool1. On the server where the BlackBerry Enterprise Server is located, at the command prompt, switch to

the Tools folder on the installation CD.

2. Type BESMigration.exe to view the list of commands that can be used with the BESMigration tool.

Retrieving and updating configuration information using the HandheldCleanup tool

Use the HandheldCleanup tool to retrieve and update configuration information for BlackBerry Enterprise Servers and users.

Command Description

-s <MAPI profile> <old server> <new server>

uses the MAPI connection (specified as <MAPI profile>) to migrate server information and user information to the new server, and creates the primary server name (specified as <new server>)

-r restores the administration folder, server information, and user information to the original server (specified as <old server> in -s option); used in conjunction with -s to reverse the direction of the migration

-d <DB server name> <DB name>

specifies the database server name and database name to be used for the user migration

-l <log filename> specifies the name of the log file generated during the user migration

-t <status filename> specifies the file from which to read status information during the migration

-w specifies the status and progress information that is written to the registry

-u <username> <password> specifies that the database is using SQL authentication

-p runs a preview of the user migration without making any changes to the database and displays any errors that occur

Note: This option does not check for server errors.

-q runs the user migration silently

-g prints user properties retrieved from the user’s mailbox to the UserMigration.log installation log file

Note: Use this command for troubleshooting purposes only.

Page 61: Maintenance Guide

61

Appendix D: Command prompt tools

Running the HandheldCleanup tool1. On the server where the BlackBerry Enterprise Server is located, at the command prompt, switch to

the Utility folder created during the installation process.

2. Type HandheldCleanup.exe to view the list of commands that can be used with the HandheldCleanup tool.

3. At the command prompt, type a command in the form HandheldCleanup.exe -flag <optional arguments>.

Verifying that the MAPI subsystem is initialized using the Fixmapisvc tool

Use the Fixmapisvc tool to verify that the MAPI subsystem is initialized. The MAPI profile is stored in the registry (HKEY_CURRENT_USER/Software/Research In Motion/BlackBerry Enterprise Server/Management/MAPIProfile). An error occurs if a MAPI client is not already present on the server. The fixmapisvc tool enables the BlackBerry Enterprise Server installation to facilitate MAPI profile creation and editing.

Run the Fixmapisvc tool1. Open either Microsoft Exchange 5.5 Administrator or Microsoft Exchange 2000/2003 System

Manager.

2. At the command prompt, switch to the Utility folder created during the installation process.

Command Description

-d [<filename>] [-p <MAPI profile name>]

This command dumps the handheld information for each handheld on a specified BlackBerry Enterprise Server (the prompt for a BlackBerry Enterprise Server name appears).

The following are optional arguments:

• <filename> is a file name to dump handheld information to. If it is not specified, the information is dumped to the screen.

• -p is a flag to signify a profile; it is combined with <MAPI profile name>.• <MAPI profile name> is an existing MAPI profile name.

-u [-p <MAPI profile name>]

This command performs the following tasks:

• Performs handheld mailbox check and update; checks for any mailboxes that have been moved.

• If the mailbox is moved, the ServerDN is set to the Global Address List ServerDN. • Any handhelds with the ServerDN changed are printed. Otherwise, no output is given.

Note: The Global Address List does not contain hidden mailboxes.

The following are optional arguments:

• -p is a flag to signify a profile; it is combined with <MAPI profile name>.• <MAPI profile name> is an existing MAPI profile name.

-c "DB Connect String" This command signifies the ODBC connection string for the database. If the connection string is not provided, the connection string is retrieved from the registry.

Note: Enclose the ODBC connection string in double quotation marks.

-h or -? This command lists all available commands

Page 62: Maintenance Guide

62

Maintenance Guide

3. Type Fixmapisvc.exe.

If fixmapisv.inf is already stored, the following message appears:

MSEMS service information already exists in C:\Program Files\Common Files\System\Mapi\1033\NT\mapisvc.inf

Otherwise, fixmapisvc.exe registers mapisvc.inf in that location.

Verifying BlackBerry Enterprise Server permissions using the IEMSTest tool

Use the IEMSTest tool to test permissions on the BlackBerry Enterprise Server.

Run the IEMSTest tool1. On the server where the BlackBerry Enterprise Server is located, at the command prompt, switch to

the Utility folder created during the installation process.

2. Type IEMSTest.exe.

3. From the Profile Name drop-down list, select the correct BlackBerry Enterprise Server MAPI profile.

4. Click OK.

The utility connects to the Microsoft Exchange Server and checks permissions.

Testing the BlackBerry Enterprise Server SRP connection using the BBSRPTest tool

Use the BBSRPTest tool to test the connection of the BlackBerry Enterprise Server—using the BlackBerry Router—to the SRP address.

Run the BBSRPTest tool 1. On the server where the BlackBerry Enterprise Server is located, at the command prompt, switch to

the Utility folder created during the installation process.

2. Type BBSRPTest.exe -? to view the list of commands that can be used with BBSRPTest.

Command Description

-server <Servername> This command enables you to specify the BlackBerry Enterprise Server instance to test, if multiple instances are installed.

-host <hostname> This command enables you to specify which host to test. If no host name is specified, the host name is retrieved from the registry.

-port <port> This command enables you to specify which port to test. If no port is specified, the port is retrieved from the registry.

-quiet This command prevents output to the screen.

-wait This command returns the SRP connection information and then prompts you to click Enter to continue.

Page 63: Maintenance Guide

63

Appendix D: Command prompt tools

3. At the command prompt, type BBSRPTest.exe -flag <optional arguments>. The tool checks the BlackBerry Enterprise Server network access node (for example, srp.na.blackberry.net) and confirms whether the SRP connection to the wireless network exists.

Repairing the registration of the performance monitor file using the BBPerfmoninstall tool

If problems with performance monitor counters occur, use the BBPerfmoninstall tool to repair the registration of the performance monitor tool .dll file.

Run the BBPerfmoninstall tool1. On the server where the BlackBerry Enterprise Server is located, at the command prompt, switch to

the Utility folder created during the installation process.

2. Type BBPerfmoninstall.exe -uninstall.

3. Type BBPerfmoninstall.exe -install. The tool repairs the registration of the performance monitor .dll file.

Verifying Mobile Data Service data consistency using the DBConsistency tool

The DBConsistency tool is the Mobile Data Service database consistency utility, and it is required by the Mobile Data Service push server. It verifies that user information that is stored in the configuration database (which is also used by the Mobile Data Service) is consistent with information stored in users’ mailboxes.

Run the DBConsistency tool1. On the server where the BlackBerry Enterprise Server is located, at the command prompt, switch to

the folder in which the Mobile Data Service utility is stored.

2. At the command prompt, type DBConsistency [command].

Note: If you set a BlackBerry Enterprise Server as a Mobile Data Service push server, the BlackBerry Database Consistency service is installed and is enabled automatically. The Database Consistency (DBConsistency.exe) tool automatic update of the email-to-PIN mapping runs by default on the push server at the specified update frequency to pick up changes. If you do not set the BlackBerry Enterprise Server as a push server, then you must start the BlackBerry Database Consistency service manually every time. If you make the BlackBerry Enterprise Server unavailable as a Mobile Data Service push server, the Database Consistency service is also made unavailable.

Commands Description

-remove This command removes the service.

-install This command installs the service.

-login=<domain>\<account> This command sets the login name.

Page 64: Maintenance Guide

64

Maintenance Guide

Start or stop the BlackBerry Database Consistency Service

Perform one of the following actions:

Controlling access to administration functions using the SetAdminKey tool

Use the SetAdminKey tool to define the accessibility of certain Blackberry Enterprise Server functions on specific administration computers. The SetAdminKey tool can enable the following three levels of access to the BlackBerry Enterprise Server administration options:

• user access mode

• policy access mode

• full access mode

SetAdminKey tool requirementsLocal administrator permissions are required to run the SetAdminKey.exe tool.

If you have a previous installation of the SetAdminKey tool installed and you have upgraded the BlackBerry Enterprise Server Software, you must install the most recent version of the SetAdminKey tool that is packaged with the current BlackBerry Enterprise Server Software.

See the BlackBerry Enterprise Server Administration Guide for information on administering the BlackBerry Enterprise Server Software.

-password=<password> This command sets the login password.

-auto This command sets the service to start automatically when the system starts.

-manual This command sets the service to be started manually (default).

-debug This command runs the DBConsistency.exe in console debug mode.

-console This command runs the DBConsistency.exe in console mode.

Commands Description

Action Procedure

Start or stop the service through Windows services.

1. Open the Windows Services window.

2. Right-click BlackBerry Database Consistency Service, and then click Start or Stop.

Start or stop the service using the command prompt.

1. On the server where the BlackBerry Enterprise Server is located, at the command prompt, switch to the directory in which the Mobile Data Service utility is stored.

2. Type DBConsistency 'net [start] DBConsistency'or DBConsistency 'net [stop] DBConsistency’.

3. In console mode, hold X to exit the DBConsistency.exe.

Warning: If users have sufficient permissions to edit the registry keys on the BlackBerry Manager computer, those users can also modify the access level of the SetAdminKey tool.

Page 65: Maintenance Guide

65

Appendix D: Command prompt tools

Install the SetAdminKey tool

1. Using a service account with Local Administrator permissions, log into the BlackBerry Manager computer on which you want to change the access level of BlackBerry Enterprise Server administration functions.

2. On the BlackBerry Enterprise Server Software CD, open the Tools directory.

3. Copy the SetAdminKey.exe file from the Tools directory to a new location on the C: drive of the computer.

Change the access mode using the SetAdminKey tool

1. Verify that you are logged into the BlackBerry Manager computer on which you want to change the access level of BlackBerry Enterprise Server administration functions, using a service account with Local Administrator permissions.

2. At the command prompt, switch to the directory in which you saved the SetAdminKey.exe file.

3. Type SetAdminKey.

4. Use the following list of commands to change the access mode:

See “BlackBerry Manager interface access level changes” on page 66 for more information.

5. Type SetAdminKey.exe <command>.

Note: The SetAdminKey tool must be installed on the same computer as the BlackBerry Manager.

Note: The BlackBerry Manager must be installed on the computer before you start the SetAdminKey tool.

Note: If you change the access mode of the SetAdminKey tool, you must first close the BlackBerry Manager and re-open it for the new access mode to take effect.

Command Description

-r user access mode; enables control over the following functions of the BlackBerry Manager

• turns off all server functionality• turns off all server management properties other than the Control settings• turns off access to the IT policy and the Mobile Data Service settings

-p policy access mode; enables control over the following functions of the BlackBerry Manager

• turns off all server functionality other than IT policy• turns off all server management properties other than the control settings

Note: Access to enable or disable the Mobile Data Service using the user menu and access to IT admin commands through the user menu are enabled.

-f full access mode; all existing functionality remains enabled

Page 66: Maintenance Guide

66

Maintenance Guide

BlackBerry Manager interface access level changesThe following features and functionality are turned off in the BlackBerry Manager when a command is specified:

Command BlackBerry Manager menu BlackBerry Manager Properties

BlackBerry Server Properties

User menu and properties

-r Import Blackberry Server(s)

Export BlackBerry Servers

Send All-Points-Bulletin (APB)

Update Peer-to-Peer Encryption Key

License tab

Ports tab

Database tab

Advanced tab

Policy Rules tab

PIM Sync tab

BlackBerry Enterprise Server Properties

Mobile Data Service Properties

Set as MDS Push Server

Send All-Points-Bulletin (APB)

IT Policy

Service Control to Start/Stop BlackBerry services

Enable Mobile Data Service

Disable Mobile Data Service

Enable Mobile Data Service

Disable Mobile Data Service

IT Admin commands

IT Admin tab in User Properties

-p Import Blackberry Server(s)

Export BlackBerry Servers

Send All-Points-Bulletin (APB)

Update Peer-to-Peer Encryption Key

License tab

Ports tab

Database tab

Advanced tab

PIM Sync tab

BlackBerry Enterprise Server Properties (with the exception of the IT Admin tab)

Mobile Data Service Properties

Set as MDS Push Server

Send All-Points-Bulletin (APB)

Service Control to Start/Stop BlackBerry services

Enable Mobile Data Service

Disable Mobile Data Service

Page 67: Maintenance Guide
Page 68: Maintenance Guide

©2006 Research In Motion LimitedPublished in Canada.