BlackBerry TM Enterprise Server 2.1 for Microsoft Exchange Service Pack 3A update information March 14, 2002

Transcription

1 BlackBerry TM Enterprise Server 2.1 for Microsoft Exchange Service Pack 3A update information March 14, 2002 PLEASE READ THE LEGAL NOTICES SET OUT AT THE END OF THIS DOCUMENT. Contents Fixed issues in this release System requirements Preinstallation requirements Installing BlackBerry Enterprise Server 2.1 SP3A Upgrading to BlackBerry Enterprise Server 2.1 SP3A Post-installation requirements Removing BlackBerry Enterprise Server Software About the BlackBerry Enterprise Server About the administration software Package contents

2 Fixed issues in this release Performance-Related Enhancements 1. A new threading model has been added to address hung thread issues due to MAPI deadlocks. 2. In previous releases, under certain conditions a user's MAPI notifications may have delayed in the BlackBerry Enterprise Server until further mailbox activity occurred. This issue is fixed in this release. Miscellaneous Fixed Issues SYMPTOM 1 In previous releases, the SMTP command "RCPT TO:" for BESAlert.exe did not properly terminate. Microsoft Exchange 2000 requires proper termination with both a carriage return and a linefeed. DETAILS This issue is fixed in this release, but the following configuration should take place: Microsoft Exchange 2000 requires that the "Notification login name" field be filled in (by characters, not blank spaces), and that the Microsoft Exchange 2000 Server will by default prevent BESAlert from sending to addresses outside the Microsoft Exchange 2000 Server, or possibly the routing group. It is required that you either configure the server to allow relaying, or restrict the addresses to those within the server or routing group.

3 SYMPTOM 2 In previous releases, non-responsive threads might occur under certain conditions when a consistency check of the calendar was performed. During a consistency check, an exception might be thrown and a lock might not be released, resulting in possible nonresponsive threads. This issue is fixed in this release. SYMPTOM 3 In previous releases, when the DebugLogFile was changed to a nonexistent path, the Event ID logged was 1 digit. Also, the event was logged repeatedly. DETAILS These issues have been fixed; an Event ID of 5 digits is now logged, and the event is logged only once. SYMPTOM 4 In previous releases, if a user's alias name contained a period, the alias name could not be resolved. When the user was added to the BlackBerry Enterprise Server, and a BlackBerry device was cradled while the Properties page was open, the following message appeared in the BlackBerry Enterprise Server Management console: "The computer does not know its address. Either the system is not configured properly or this system is not supported." Errors resulted in the BlackBerry Enterprise Server indicating a failure to resolve the user. This issue is fixed in this release. SYMPTOM 5 In previous releases, the BlackBerry Enterprise Server's main processing thread could hang under certain conditions. While in this state, message flow through the BlackBerry Enterprise Server

4 was significantly reduced. A processing thread hang could be triggered by a mailbox move, or by the restart of a user that previously failed to start. This issue is fixed in this release. SYMPTOM 6 The following issue was first addressed in a Service Pack 2 hotfix release: Previously, when wireless calendar synchronization was enabled and a recurring appointment was created on the desktop in the Arizona time zone, the appointment would not synchronize properly. Recurring appointments created in the Arizona time zone were incorrectly identified as a different time zone on the device when synchronization or bulk loading occurred. DETAILS Microsoft Outlook incorrectly formatted the time zone in the recurring appointment. In this release, the improperly specified time zone is identified as "Arizona" and correctly sent to the device using the BlackBerry Desktop bulk load and BlackBerry Enterprise Server wireless calendar synchronization. Over-the-Air Calendar Issues SYMPTOM 7 In previous releases, a meeting request sent to an invalid address that did not include '@' resulted in a duplicate entry in the calendar of the meeting organizer. The message itself would fail but the meeting would appear twice in the meeting organizer's calendar, with no Organizer or Invited fields. This issue is fixed in this release; a meeting request sent to an invalid address will still fail, but no calendar entries will be created for a failed request.

5 SYMPTOM 8 In previous releases, an occurrence of a recurring meeting request sent to an attendee was removed from the original attendee's Desktop if another attendee was added to that occurrence. This issue is fixed in this release. SYMPTOM 9 In previous releases, when a meeting request with comments included in the Notes field was sent and accepted on a wireless handheld, under certain conditions where the meeting organizer received an acceptance and then canceled the meeting, with added comments in the Notes field, the meeting invitee would receive the cancellation message without the new comments. However, if the invitee viewed the cancellation in Microsoft Outlook, the new comments were visible. This issue is fixed in this release. SYMPTOM 10 In previous releases, when a single all-day appointment was created on the handheld, once wireless synchronization occurred, the appointment might appear on the Desktop without the 'All day event' option selected in Microsoft Outlook. This problem did not occur when the all-day appointment was created in Microsoft Outlook. This issue is fixed in this release. SYMPTOM 11 In previous releases, mail delivery to and from the BlackBerry wireless handheld could be interrupted when a user with wireless calendar synchronization enabled created an appointment in their calendar. Under certain conditions, the BlackBerry Enterprise Server

6 failed to process the calendar item properly. Bad calendar data was sent to the wireless handheld and the wireless handheld had to be reset before it could send or receive mail. This issue is fixed in this release. BlackBerry Enterprise Server Management Issues SYMPTOM 12 In previous releases, when the BlackBerry Enterprise Server Management DebugLogFile was changed to a non-existent path, the event was logged repeatedly. DETAILS This issue is fixed in this release; the event is now logged only once. SYMPTOM 13 In previous releases, if a routing group name contained a comma, no BlackBerry TM Enterprise Servers were found in the routing group and the routing group appeared as read-only in the BlackBerry Enterprise Server Management console. This issue is fixed in this release. System requirements The BlackBerry Enterprise Server Software requires the following hardware and software components: Hardware PC with an Intel -compatible Pentium processor or compatible (233 MHz or higher, 128-MB RAM, 1-GB hard disk Software BlackBerry Enterprise Server works in Microsoft Exchange 5.5 (or later) or Microsoft Exchange 2000 native environments, or in a

7 mixed environment (Microsoft Exchange 5.5 and Microsoft Exchange 2000). Note Microsoft Exchange Service Pack 4 is not required on your Microsoft Exchange 5.5 Server(s). It IS required for the computer on which your BlackBerry Enterprise Server service is installed. The following software is required for the BlackBerry Enterprise Server to function: Windows NT 4.0 (Service Pack 5 or later recommended) OR Windows 2000 (Service Pack 1 or later recommended) Microsoft Exchange 5.5 (recommended installation on a separate computer from than the BlackBerry Enterprise Server service) OR Microsoft Exchange 2000 (Service Pack 1 or later recommended) If Microsoft Exchange Service Pack 2 is installed on the Microsoft Exchange Server, it should also be installed on the BlackBerry Enterprise Server WARNING When installing the Blackberry Enterprise Server Software on a Microsoft Small Business Server (MSBS) 2000 system, the Microsoft Data Engine (MSDE) software that ships with the product does not install and returns no error messages. For solutions to this problem, refer to section "Installing BlackBerry Enterprise Server 2.1 SP3A." Microsoft Exchange Administrator 5.5 (with Microsoft Exchange 5.5 Service Pack 4 installed), on the BlackBerry

8 Enterprise Server service computer, with access to the Microsoft Exchange Server: WARNING If you install Microsoft Exchange Administrator 5.5 on a new computer, you must run it and connect to a Microsoft Exchange Server that shares the site in which you will install the BlackBerry Enterprise Server. BlackBerry Enterprise Server Management (MMC Snap-in) Software (required if Microsoft Exchange 2000 is installed) with Microsoft Exchange 2000 System Manager (installed on the computer on which the BlackBerry Enterprise Server service will be installed) You should not have Microsoft Outlook installed on the computer on which you are installing the BlackBerry Enterprise Server. If Microsoft Outlook is present on the BlackBerry Enterprise Server computer, wireless calendar synchronization will not work because Microsoft Outlook s versions of CDO and MAPI.DLL files do not support wireless calendar synchronization. If Microsoft Outlook is opened on a BlackBerry Enterprise Server, it will attempt to overwrite the MAPI system. Therefore, Microsoft Outlook on a BlackBerry Enterprise Server is an unsupported configuration. Note BlackBerry Desktop Software 3.0 (European release) does not support wireless calendar synchronization. Before installing BlackBerry Enterprise Server, Install the CDO.dll hotfix for Microsoft Product Support Services Knowledge Base article Q You can download the hotfix and obtain information on the Knowledge Base article from:

9 Release.asp?ReleaseID=29085 The CDO.dll should be version , Service Pack 5. Note Your corporate firewall must allow the Domain Name System (DNS) to resolve Internet addresses. Firewall configuration The BlackBerry Enterprise Server initiates outbound, bidirectional connections to the wireless network. To support the BlackBerry solution in an environment with a firewall in place, you must configure the firewall to allow the computers running the BlackBerry Enterprise Server within the company to initiate TCP/IP connections to an outside server listening on port If you use a proxying firewall, the proxy must be transparent. Note A transparent proxy does NOT modify requests or responses through the proxy during proxy authentication and identification, whereas a non-transparent proxy (where the client specifies the hostname and port number of the proxy) DOES modify requests or responses through the proxy. If you have a non-transparent proxy, the BlackBerry Enterprise Server can be configured to access an internal proxy address which is then translated externally to the SRP Host on port Verify that your firewall is configured to accommodate these types of outbound-initiated connections bidirectionally.

10 Preinstallation requirements Installing and registering a CDO hotfix Note The CDO.dll supplied with Microsoft Outlook does not allow Over the Air (OTA) calendaring. (BlackBerry Desktop Software 3.0 does not support wireless calendar synchronization.) You must install both the CDO.dll hotfix and Microsoft Exchange 5.5 Service Pack 4 to have the correct CDO and MAPI versions. 1. Install the CDO.dll hotfix for Microsoft Product Support Services Knowledge Base article Q You can download the hotfix and obtain information on the Knowledge Base article from: Release.asp?ReleaseID=29085 The CDO.dll should be version , Service Pack 5 2. Manually register the CDO.dll hotfix using one of the following methods: a) At the command prompt (C:/winnt/system32/), type the following: regsvr32 cdo.dll b) Select Start> Run. In the Run dialog, in the Open field, type: regsvr32 cdo.dll Defining a service account and setting its permissions You must define a user service account and mailbox. The new user will act as your BlackBerry Enterprise Server service account, with the following permissions:

11 Log on locally with local permissions (this is optional, but useful for troubleshooting - if you prefer, you can remove this after install): this permission should already be set by default Log on as a service Service Account Admin. permissions on the Site container and Configuration container Local administrator permissions Note To install the Microsoft Exchange 5.5 administration extensions, Write permissions must be assigned to the "Add-Ins" shared folder on the Microsoft Exchange Server. The setting of these permissions is detailed in the BlackBerry Enterprise Server Software for Microsoft Exchange Installation and Getting Started Guide provided on your BlackBerry Enterprise Server Software installation CD (open Root_directory:\bes.pdf). Installing BlackBerry Enterprise Server 2.1 SP3A To perform an initial BlackBerry Enterprise Server install with Microsoft Exchange 5.5 or Microsoft Exchange 2000, the following tasks are required: 1. Installing and registering the CDO.dll hotfix 2. Defining a service account and creating a Microsoft Exchange mailbox 3. Setting permissions: Assigning Local administrator permissions to the BlackBerry Enterprise Server service account on the BlackBerry Enterprise Server machine

12 Assigning BlackBerry Enterprise Server service account permissions to the BlackBerry Enterprise Server on the Microsoft Exchange server Assigning permissions to the BlackBerry Enterprise Server account within the Microsoft Exchange site 4. Installing the BlackBerry Enterprise Server Software WARNING You can install MSDE, SQL 7.0 or SQL 2000 manually or, when you install BlackBerry Enterprise Server Management, if you do not have MSDE installed, the InstallShield Wizard will offer to install it at that time. However, when installing the BlackBerry Enterprise Server on a Microsoft Small Business Server (MSBS) 2000 system, the MSDE software that ships with the product will not install and returns no error messages. In this situation you can use one of the following two solutions. Solution 1 1. Install the MSDE 2000 that ships with MSBS This software can be found on CD 2 in the \SQL2000\MSDE directory. 2. Run setup.exe SECURITYMODE=SQL. You can now install the BlackBerry Enterprise Server Management Software. This will allow the software to correctly create the database for the BlackBerry Enterprise Server Management. Details By default, when run on the Microsoft Windows NT 4.0 or Microsoft Windows 2000 operating system, the Desktop Engine Setup configures the installed instance of Microsoft SQL Server to use Windows Authentication, and places the Windows local administrator's group in the SQL Server sysadmin fixed server role. When running Desktop Engine Setup on the Windows NT 4.0 or Windows 2000 operating system, you can specify a SECURITYMODE=SQL parameter to have the installed instance configured to use SQL Server Authentication with a null sa

13 password. If the MSDE 2000 software has been installed previously, the Security model can be changed by editing the following registry key: HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\Lo ginmode The default for this key is "1" to enable integrated security. Changing this key to "2" will change the server security setting to "mixed" and allow the BlackBerry Enterprise Server to create the database. Solution 2 If the MSDE software has already been installed and the BlackBerry Enterprise Server Software setup has been run, the database can be recreated following these steps: 1. After setting the security mode as specified above, open the Createdb.sql file located in \Program Files\Research in Motion\BlackBerry Enterprise Server Management\Database\. 2. This file specifies c:\mssql7\data\, as the default path for the database data directory. 3. This has to be changed to: C:\Program Files\Microsoft SQL Server\MSSQL\data\. 4. Once the file has been modified, open a command prompt and change to the \Program Files\Research in Motion\BlackBerry Enterprise Server Management\Database\ directory. 5. Run Createdb.exe from the command line. Once this has completed you will receive the following message: Database setup complete. Check the setup.txt for any sql messages. You can now install the BlackBerry Enterprise Server as you would on any Microsoft Exchange 2000 system. Details The setup.txt file should look like this:

14 Starting the database creation script Creating the database now The CREATE DATABASE process is allocating 1.00 MB on disk 'BESMgmt'. The CREATE DATABASE process is allocating 1.00 MB on disk 'BESMgmtLog'. Creating the tables Adding error messages to the database Creating the stored procedures in the database Finished setting up the stored procedures 6. Post-installation procedures Installing the administration extensions (for Microsoft Exchange 5.5 only) Configuring the BlackBerry Enterprise Server Starting the BlackBerry Enterprise Server services Perform the steps in the order in which they appear. All of the steps are required unless otherwise stated. For further information on installing BlackBerry Enterprise Server Software, please see the BlackBerry Enterprise Server Software for Microsoft Exchange Installation and Getting Started Guide provided on your BlackBerry Enterprise Server Software installation CD (open Root_directory:\bes.pdf). Upgrading to BlackBerry Enterprise Server 2.1 SP3A If you are running BlackBerry Enterprise Server 1.6 or 2.0, you do not need to remove your current software to upgrade your BlackBerry Enterprise Server Software.

15 Upgrading your BlackBerry Enterprise Server consists of the following tasks: 1. Upgrading your software 2. Restarting the BlackBerry Enterprise Server service (see Postinstallation requirements) Upgrading your software To upgrade your software, complete the following steps: 1. Log on to the BlackBerry Enterprise Server target machine as the BlackBerry Enterprise Server service account or site services account (this account should have Local Administrator rights to the BlackBerry Enterprise Server). 2. If BESMonitor is running, stop it by double-clicking the BESMonitor icon in the Windows SysTray and clicking Exit. 3. If you are using Windows 2000: In the Start menu, select Programs> Administrative Tools> Services. Right-click BlackBerry Server and select Stop to stop the BlackBerry Server service. Right-click BES Alert and select Stop to stop the BlackBerry Server service. If you are using Windows NT: In the Start menu, select Settings> Control Panel. Double-click Services. Select BlackBerry Server and select Stop to stop the BlackBerry Server service. Select BES Alert and select Stop to stop the BlackBerry Server service. 4. If you have just removed Microsoft Outlook, install Microsoft Exchange 5.5 Service Pack 4 on the BlackBerry Enterprise Server (or reinstall if it is already present). 5. Before upgrading BlackBerry Enterprise Server, install the CDO.dll hotfix for Microsoft Product Support Services

16 Knowledge Base article Q You can download the hotfix and obtain information on the Knowledge Base article from: Release.asp?ReleaseID=29085 The CDO.dll should be version , Service Pack 5l Note The CDO.dll supplied with Microsoft Outlook does not allow wireless calendar synchronization. (BlackBerry Desktop Software 3.0, a European release, does not support wireless calendar synchronization.) In a Microsoft Exchange 5.5 environment You must install both the CDO.dll hotfix and Microsoft Exchange 5.5 Service Pack 4 to have the correct CDO and MAPI versions. 6. Manually register the CDO.dll hotfix using one of the following methods: a) At the command prompt (C:/winnt/system32/), type the following: regsvr32 cdo.dll b) Select Start > Run. In the Run dialog, in the Open field, type: regsvr32 cdo.dll 7. If Microsoft Outlook (97, 98, or 2000) is installed on the BlackBerry Enterprise Server, a warning message appears that Microsoft Outlook should be removed before proceeding with

17 the BlackBerry Enterprise Server install. Remove Microsoft Outlook now. Note If Microsoft Outlook is present on the BlackBerry Enterprise Server machine, wireless calendar synchronization will not work because Microsoft Outlook s versions of CDO and MAPI DLLs do not support wireless calendar synchronization. (BlackBerry Desktop Software 3.0, a European release, does not support wireless calendar synchronization.) If Microsoft Outlook is opened on a BlackBerry Enterprise Server, it will attempt to overwrite the MAPI system. Thus, Microsoft Outlook on a BlackBerry Enterprise Server is an unsupported configuration. 8. To begin the installation, run the Setup file provided for BlackBerry Enterprise Server 2.1 SP3A. For further information on installing BlackBerry Enterprise Server Software, please see the BlackBerry Enterprise Server Software for Microsoft Exchange Installation and Getting Started Guide provided on your BlackBerry Enterprise Server Software installation CD (open Root_directory:\bes.pdf). Post-installation requirements Procedures to be completed after you have installed the BlackBerry Enterprise Server Software include: Installing the administration extensions (optional, for Microsoft Exchange 5.5 only) Configuring the BlackBerry Enterprise Server Starting the BlackBerry Enterprise Server services You should perform these steps in the order in which they appear in this document. All of the steps are required unless otherwise stated.

18 Installing the administration extensions (optional) Note You can choose to install the administration extensions after the BlackBerry Enterprise Server installation. You need only complete this procedure if you are using Microsoft Exchange Administrator 5.5 and you did not install the extensions using the BlackBerry Enterprise Server InstallShield Wizard. Before you can administer the BlackBerry Enterprise Server in a Microsoft Exchange 5.5 environment with Microsoft Exchange Administrator 5.5 installed, you must install the BlackBerry Enterprise Server extensions for Microsoft Exchange Administrator. This step needs to be performed once in a single Microsoft Exchange site. After the administration extensions are installed, Microsoft Exchange automatically propagates the extensions to every Microsoft Exchange Server in the site. To install the administration extensions, complete the following steps: 1. Log in to the BlackBerry Enterprise Server computer as the BlackBerry Enterprise Server service account. 2. Ensure that Write permission is assigned to the Add-Ins shared folder on the Microsoft Exchange Server. 3. On the Start menu, select Programs > BlackBerry Enterprise Server > Install Administration Extensions. The Exchange Server Information dialog opens. By default, the name of the home Microsoft Exchange Server, on which you will install the BlackBerry Enterprise Server administration extensions, should appear in the Exchange Server Information dialog box.

19 4. If the server name does not appear, type the NetBIOS name (the first part of a server name, for example, Server1, where the full server name is Server1/Server/BlackBerry), also known as the common name, of the Microsoft Exchange Server onto which you want to install the extensions, and then click OK. The extensions are installed to the specified Microsoft Exchange Server. Microsoft Exchange will propagate the extensions through every Microsoft Exchange Server in the site. If you choose to install upgraded extensions at a later date or remove the extensions, you should specify this Microsoft Exchange Server during the installation or removal. Note The users BlackBerry handheld devices must have BlackBerry Desktop Software version 2.1 (version 3.1 in Europe) installed for wireless calendar synchronization to work. BlackBerry Desktop Software 3.0 (European release) does not support wireless calendar synchronization. Once you have upgraded the BlackBerry Enterprise Server to version 2.1, all users must synchronize their BlackBerrys to have access to this functionality. Configuring the BlackBerry Enterprise Server After you install the BlackBerry Enterprise Server files and the corresponding Microsoft Exchange administration software, you must configure the BlackBerry Enterprise Server. If you are using Microsoft Exchange 5.5: a) In the Microsoft Exchange Administrator 5.5 window, select the Configuration container. b) Double-click the BlackBerry Servers object to open the BlackBerry Servers Properties window. c) Click Add Server to open the BlackBerry Server System Info window.

20 OR If you are using Microsoft Exchange 2000: a) In the BlackBerry Enterprise Server Management (MMC Snap-in) interface, right-click the routing group. b) Select New BlackBerry Server. The remaining steps are the same in both Microsoft Exchange Administrator and BlackBerry Enterprise Server Management. 1. In the Server Name field, type the server name that you provided during the BlackBerry Enterprise Server files installation. 2. In the SRP Identifier and SRP Authentication Key fields, type the appropriate information provided on the installation CD label. This information is unique to each host license. If host routing information was also provided on the installation CD label, in the Host Routing Info field, define the necessary information to connect to the mobile network. WARNING You should only define values in this field if values are provided with the installation material. If you define incorrect values in this field, connection to the mobile network will not be possible. 3. In the Admin Mailbox field, click Select Mailbox to locate the mailbox that you set up for BlackBerry Enterprise Server administration (or type a name and click Check Name to verify it). 4. Once you ve completed all of the fields, click OK to close the BlackBerry Enterprise Server System Info window.

21 5. If you are using Microsoft Exchange Administrator 5.5, click OK to close the BlackBerry Servers Properties window. Repeat the procedure for additional BlackBerry Enterprise Servers. For each server added, you must install the BlackBerry Enterprise Server files on the corresponding computer. To prevent loss of service, please ensure that the SRP identifier and authentication keys are unique for each BlackBerry Enterprise Server. Starting the BlackBerry Enterprise Server service The services are installed as automatic services, but must be manually started after the installation or upgrade. 1. From the Start button, select Settings> Control Panel to open the Control Panel window. 2. Click Services to open the Services window. 3. Select the BlackBerry Server item. Click Startup... to start the BlackBerry Enterprise Server service. Verify that the BlackBerry Enterprise Server service account name appears in the Account field. Change the service startup to Automatic and click OK. Click Start to start the BlackBerry Server service. 4. Select the BESAlert item, and click Start to start the BESAlert service. 5. Click Close to return to the Control Panel window. Now that you ve set up the appropriate accounts, installed the executables and the extensions and created a BlackBerry Enterprise Server, you are ready to use the server and its tools.

22 Removing BlackBerry Enterprise Server Software Removing BlackBerry Enterprise Server administration extensions If you want to remove the BlackBerry Enterprise Server administration extensions, you must do so BEFORE you remove the BlackBerry Enterprise Server Software. Note You should only remove the extensions if no BlackBerry Enterprise Servers are needed within the Microsoft Exchange site. Performing this step results in the removal of all defined BlackBerry Enterprise Servers from the site configuration. To remove the BlackBerry Enterprise Server administration extensions, while logged on as BESAdmin, on the Start menu, select BlackBerry Enterprise Server > Uninstall Administration Extensions. Removing BlackBerry Enterprise Server Software Note This procedure does not remove the BlackBerry Enterprise Server administration extensions from Microsoft Exchange. If you want to remove the administration extensions, you must do so BEFORE you remove the BlackBerry Enterprise Server Software. To remove BlackBerry Enterprise Server Software, complete the following steps: 1. From the Control Panel window, double-click Add/Remove Programs.

23 2. The Add/Remove Programs window appears. 3. From the list of programs, select BlackBerry Enterprise Server and click Add/Remove. 4. Click OK to confirm that you want to remove the application and all of its components. Removing BlackBerry Enterprise Server Management (MMC Snap-in) Software To remove BlackBerry Enterprise Server Management (MMC Snapin) Software, complete the following steps: Note Removing BlackBerry Enterprise Server Management does not automatically remove MSDE or the BlackBerry Enterprise Server Management database. They must be removed individually. 1. From the Control Panel window, double-click Add/Remove Programs. 2. The Add/Remove Programs window appears. 3. From the list of programs, select BlackBerry Enterprise Server Management and click Add/Remove. 4. Click OK to confirm that you want to remove the application and all of its components. Removing BlackBerry User Administration Software To remove BlackBerry User Administration Software, complete the following steps:

24 1. From the Control Panel window, double-click Add/Remove Programs. 2. The Add/Remove Programs window appears. 3. From the list of programs, select BlackBerry User Administration and click Add/Remove. Click OK to confirm that you want to remove the application and all of its components. About the BlackBerry Enterprise Server The BlackBerry Enterprise Server consolidates the operation of individual desktop redirectors into a server that the system administrators can monitor and control. The server supports laptop users and enables PC users to turn off their computers at the end of the day. System administrators manage the centralized administration and control of mobile , and users can continue to configure redirection options using the BlackBerry Desktop Software on their PCs. For administrative procedures, refer to the BlackBerry Enterprise Server Installation and Getting Started Guide and online Help. About the administration software BlackBerry Enterprise Server can be administered by one of two management tools, depending on whether you are installing in a Microsoft Exchange 5.5 or Microsoft Exchange 2000 environment, or in a mixed environment, where a Microsoft Exchange 2000 server is added to an existing Microsoft Exchange 5.5 environment.

25 BlackBerry Enterprise Server administration extensions for Microsoft Exchange Administrator 5.5 To administer the BlackBerry Enterprise Server in a Microsoft Exchange 5.5 or mixed environment, with Microsoft Exchange Administrator 5.5 installed, you must install the BlackBerry Enterprise Server extensions for Microsoft Exchange Administrator 5.5 to a server on the target Microsoft Exchange site. This step only needs to be performed once in a single Microsoft Exchange site. After they are installed, Microsoft Exchange automatically propagates the extensions to every Microsoft Exchange Server in the site. BlackBerry Enterprise Server Management (MMC Snap-in) To administer BlackBerry Enterprise Server(s) in a native Microsoft Exchange 2000 or mixed (Microsoft Exchange 2000 and Microsoft Exchange 5.5) environment, you must install BlackBerry Enterprise Server Management (MMC Snap-in) Software. BlackBerry Enterprise Server Management (MMC Snap-in) functions as a snapin to the Microsoft Management Console. From the BlackBerry Enterprise Server Management (MMC Snapin) console, you can administrate users at the server-level and mailbox-level. The BlackBerry Enterprise Server Management (MMC Snap-in) Software includes an MSDE or SQL database (to store data relevant to the BlackBerry Enterprise Server(s) and administration mailboxes), and the BlackBerry Enterprise Server Management (MMC Snap-in) console (the interface that allows administration of the BlackBerry Enterprise Server(s) and its users).

26 Package contents Your BlackBerry Enterprise Server package should contain the following BlackBerry Enterprise Server Software and additional tools: - BlackBerryServer.exe: the program that redirects from the user's Microsoft Exchange mailbox to the BlackBerry handheld - BESMonitor.exe: the program that shows you the current status of the BlackBerry Enterprise Server running on that machine - BESAlert.exe: the program that monitors the Windows NT Event Log and can be configured to send notification to defined users when specified event levels are logged - Add-Ins\BBMailboxExt\i386\BBMailboxExt.dll (used only in a Microsoft Exchange 5.5 environment): adds the BlackBerry tab to mailbox properties for all recipients within the site that contains the selected server - Add-Ins\BBMailboxExt\i386\BBServerExt.dll (used only in a Microsoft Exchange 5.5 environment): adds a BlackBerry Servers object in the Configuration branch of the site that contains the selected server - Policy.inf file: allows IT managers to change the default settings for users desktop software - ITPolicy.exe: used in conjunction with the policy.inf file to generate a scrambled policy.bin file that is used to configure users' desktop software default settings - Keyword.txt: lists all policy.inf keys - WinBBAdminInstall.exe: supports installing and removing the extensions from the Start menu

27 - FBUpdate.exe: a helper program used by the BlackBerry Enterprise Server to force updates to Microsoft Outlook s free/busy information - dbghelp.dll: a helper file for debug logging - C:\WINNT\System32\CDO.dll: allows use of Microsoft Exchange Server 5.5 Collaboration Data Objects (CDO) - C:\WINNT\System32\BESPerfInfo.dll: allows administrators to view dynamic Global Statistics - C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BlackBerryServerSNMPAgent.dll: allows administrators to view dynamic Global Statistics - BESManMMC.msc: BlackBerry Enterprise Server Management (MMC Snap-in) Software, used to administrate the BlackBerry Enterprise Server in a Microsoft Exchange 2000 native or mixed (Microsoft Exchange 5.5 and Microsoft Exchange 2000) environment - createdb.exe: used to create the BlackBerry Enterprise Server Management (MMC Snap-in) database; the database can also be created during installation of the BlackBerry Enterprise Server Management (MMC Snap-in) Software - MMCProfile.exe: used to create/edit the BlackBerry Enterprise Server Management (MMC Snap-in) service account s MAPI Profile; the profile can also be created during installation of the BlackBerry Enterprise Server Management (MMC Snap-in) Software Utilities - BESProfile.exe: a GUI program that allows you to edit the MAPI profile being used by the BlackBerry Enterprise Server - BBUserAdminClient.exe: allows administrators to add, delete, or list users on a specified BlackBerry Enterprise Server

28 - BBUserAdminService.exe: the service that executes the requests made by the BBUserAdminClient - BBPerfMonInstall.exe: a utility that repairs the installation of the BlackBerry Enterprise Server Performance Monitor DLL - BBSRPTest.exe: tests the SRP connection to the wireless network - HandheldCleanup.exe: allows administration to retrieve and update configuration for individual - BlackBerry Enterprise Server users as well as the configuration information for each BlackBerry Enterprise Server - IEMSTest.exe: tests the permission requirements for a BlackBerry Enterprise Server - Tools\fixmapisvc.exe: to be run before creating a new MAPI Profile when the MAPI Profile cannot be found Note Each command-line utility includes a usage parameter, which offers more extensive information on each utility. SRP Authentication Values The following values are listed on the SRP Authentication Information label (located on your installation CD jewel case): SRP Address SRP Identifier SRP Authentication Key Installation Documentation - BlackBerry Enterprise Server Software for Microsoft Exchange Installation and Getting Started Guide: Root_directory:\bes.pdf

29 - BlackBerry Enterprise Server Management (MMC Snap-in) Software for Microsoft Exchange 2000 Installation and Getting Started Guide: Root_directory:\BESManMMC\mmc_snap-in.pdf - BlackBerry Enterprise Server for a Clustered Environment Installation and Getting Started Guide: Root_directory:\Cluster\BES_cluster.pdf Administration Documentation - BlackBerry Enterprise Server Software for Microsoft Exchange 5.5 Administration and Getting Started Guide: Root_directory:\docs\bes_admin_with_exchange5.5.pdf - BlackBerry Enterprise Server Management (MMC Snap-in) Software for Microsoft Exchange 2000 Administration and Getting Started Guide: Root_directory:\docs\bes_admin_with_mmc.pdf - BlackBerry User Administration Installation and Getting Started Guide: Root_directory:\BBUserAdmin\BBUserAdmin.pdf - BlackBerry Enterprise Server for a Clustered Environment Installation and Getting Started Guide: Root_directory:\Cluster\BES_cluster.pdf For technical support your question to support@blackberry.net for a prompt response go to 24-hour Technical Support: +1(877) (U.S. and Canada only)

30 contact your point of purchase for your licence to BlackBerry Enterprise Server Software (Europe only) NOTE This document is provided for informational purposes only, and does not constitute a binding legal document. RIM assumes no responsibility for any typographical, technical or other inaccuracies in this document, and makes no warranties, express or implied, with respect to the content of 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. IN NO EVENT SHALL RIM BE LIABLE TO ANY PARTY FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES FOR ANY USE OF THIS DOCUMENT, INCLUDING WITHOUT LIMITATION, RELIANCE ON THE INFORMATION PRESENTED, LOST PROFITS OR BUSINESS INTERRUPTION, EVEN IF RIM WAS EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any software that is provided with this document will be governed by the terms and conditions of the RIM software license provided to you with either your RIM wireless handheld or the RIM BlackBerry Enterprise Server Software, as applicable, and, by using the software provided with this document, you agree to be bound by such terms. Warning: This document is for the use of licensed users only. Any unauthorized copying, distribution or disclosure of information is a violation of copyright laws. No reproduction in whole or in part of this document may be made without express written consent of RIM.

31 2002 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 and the BlackBerry logo are registered with the U.S. Patent and Trademark Office and may be pending or registered in other countries. All other brands, product names, company names, trademarks and service marks are the properties of their respective owners. The handheld 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; D,445,428; D,433,460; D,416,256. Other patents are registered or pending in various countries around the world. Please visit patents.shtml for a current listing of applicable patents. PDF