BlackBerry Enterprise Server for Microsoft Exchange Version 3.5 Service Pack 1 December 2002 PLEASE READ THE LEGAL NOTICES SET OUT AT THE END OF THIS DOCUMENT. This document provides information about BlackBerry Enterprise Server for Microsoft Exchange, Version 3.5 Service Pack 1, as well as answers to questions you might have.
Contents •
Fixed issues in BlackBerry Enterprise Server version 3.5 Service Pack 1
•
About the BlackBerry Enterprise Server
•
About the administration software
•
About Mobile Data Service
•
Handheld compatibility
•
System requirements
•
Preinstallation procedures
•
Prerequisites for migrating from Microsoft Exchange 5.5 administration extensions
•
Installing BlackBerry Enterprise Server version 3.5 Service Pack 1
•
Upgrading to BlackBerry Enterprise Server version 3.5 Service Pack 1
•
Post-installation requirements
•
Removing BlackBerry Enterprise Server Software
•
Additional documentation
•
Package contents
Fixed issues in BlackBerry Enterprise Server version 3.5 Service Pack 1 Miscellaneous issues
2
1.
In previous releases, Performance Monitor values were not updated correctly when the Clear Server Stats option was used. The values should be reset to 0, but were only updated when the corresponding object was updated in the Global Stats (that is, Message Sent was updated when a message was sent, but Message Received was not updated until a new message was received). All Performance Monitor values can be updated simultaneously by restarting the BlackBerry service. This issue is fixed in this release.
2.
In previous releases, when a Lotus Notes user sent a meeting request to a user on a BlackBerry Enterprise Server for Microsoft Exchange and the invitee accepted the meeting request on the handheld, the meeting organizer did not receive the accepted response. An error message might have appeared on the invitee’s handheld indicating that the meeting had been updated or deleted when the meeting organizer had not updated or deleted the meeting. This issue is fixed in this release.
3.
In previous releases, certain configurations resulted in the BlackBerry Enterprise Server being unable to save user statistics to the BlackBerry Enterprise Server administration mailbox quickly enough. This caused degradation in message delivery times. This release includes improvements to the ability of the BlackBerry Enterprise Server to cache statistics and write them to the administration mailbox at regular intervals (the default frequency is once per minute), which are configurable via the registry settings.
4.
In previous releases, under some conditions while processing a user's filter rules, the BlackBerry Enterprise Server might crash. This issue is fixed in this release.
5.
In previous releases, the BlackBerry Enterprise Server might have crashed during handheld startup, if more than 15 minutes elapsed before service began for all users. This issue is fixed in this release.
6.
In previous releases, during an upgrade, the installer did not stop the BlackBerry User Administration (BBUserAdmin) service, causing the older version of BBUserAdminService.exe to remain on the computer.
7.
In previous releases, if the BlackBerryBackup.exe utility was run with the -b flag in conjunction with the -r flag, only the system configuration was backed up and the user information was excluded. This issue is fixed in this release.
BlackBerry Enterprise Server for Microsoft Exchange
8.
In previous releases, when opening a user information file in Microsoft Excel that was exported from Handheld Manager, Forwarded data appeared under the Sent From Handheld column heading, and all other entries were transposed 1 column to the right. This issue is fixed in this release.
9.
BESAlert has been changed in this release to prevent clients from receiving old event messages. Code was changed to improve performance and responsiveness of the BESAlert service.
10. In previous releases, if, during startup of the BlackBerry Enterprise Server, more than 2 minutes elapsed before a single user was initialized, the BlackBerry Enterprise Server might crash. This issue is fixed in this release. 11. In previous releases, Simple Network Management Protocol (SNMP) did not support viewing multiple BlackBerry Enterprise Server services on a single computer. If you installed multiple BlackBerry Enterprise Server services, you could tell which service’s statistics you were viewing, and you could not view statistics for more than one service. This issue is fixed in this release. 12. In the previous BlackBerry Enterprise Server version 3.5 release, when BlackBerryBackup.exe was run using the -r switch to restore the system information, a misleading message indicating that no users had been added appeared when the restore was complete, although the restore was not intended to add any users. The message has been amended in this release. 13. In previous releases, when a meeting request was opened in Microsoft Outlook, while running Windows XP, the following error might have appeared under some conditions: "The function cannot be performed because the message has changed." The user had to close and reopen the meeting request before it could be accepted or declined from the Preview pane. One condition under which this error might occur was identifed and is resolved in this release.
Wireless synchronization issues 1.
In previous releases, deleting a recurring weekly/monthly/yearly appointment after the first occurrence of the appointment series was already deleted did not wirelessly synchronize to the desktop. This issue is fixed in this release.
2.
In the previous BlackBerry Enterprise Server version 3.5 release, when the IT Admin command Kill Handheld was sent to a handheld that did not support wireless synchronization of IT Admin commands, the status displayed Applied Successfully even though the command was not applied successfully. This issue is fixed in this release.
3.
In previous releases, when a delegate created a meeting directly in a manager's calendar, the delegate appeared as the meeting organizer on the manager's handheld. This issue is fixed in this release.
BlackBerry Enterprise Server for Microsoft Exchange
3
BlackBerry Enterprise Server Management issues 1.
In previous releases, when exporting user information from BlackBerry Enterprise Server Management, some export stats were exported even when explicitly chosen not to be exported. This issue is fixed in this release.
2.
In previous releases, the BlackBerry Enterprise Server Management console appears to hang when Export User Info is selected for multiple users. This issue is fixed in this release.
3.
In previous releases, when exporting user information for a subset of users in BlackBerry Enterprise Server Management, the export file misleadingly listed the number of users exported as equal to the total number of users on the BlackBerry Enterprise Server, although only the users selected for exporting appear in the file. This issue is fixed in this release.
4.
In previous releases, under some conditions the Email-to-PIN mapping in BlackBerry Enterprise Server Management was not automatically populating the BlackBerry Enterprise Server name on the General tab of a user's Properties window when a handheld was assigned. This issue is fixed in this release.
5.
In previous releases, the frequency with which the DBConsistency utility updated the Email-to-PIN mapping in the database could be changed only by editing the registry key. This issue is remedied in this release; when a BlackBerry Enterprise Server is set as the Mobile Data Service Push Server, an extra tab called Push Server with a field for setting the Email-to-PIN mapping update frequency appears in the Mobile Data Service Properties window.
6.
In previous releases, after the BlackBerry Enterprise Server service account was deleted, orphaned servers could not be removed from the BlackBerry Enterprise Server Management console. This issue is fixed in this release.
7.
In previous releases, while adding a BlackBerry Enterprise Server to the BlackBerry Enterprise Server Management console, adding the Administration mailbox name by typing it in the field (instead of clicking Select Mailbox and choosing a mailbox from the dialog that appeared) might have resulted in an inaccurate error message indicating that the mailbox was not in the current site. This issue is fixed in this release.
8.
In previous releases, in a Microsoft Exchange 2000 environment, BlackBerry Enterprise Server Management did not find any routing groups in the domain if a routing group had a slash mark (/) in its name. This issue is fixed in this release.
9.
In previous releases, under some conditions in a Microsoft Exchange 5.5 environment, BlackBerry Enterprise Server Management required a long time to open. This issue is fixed in this release.
Mobile Data Service issues 1.
4
In the previous BlackBerry Enterprise Server version 3.5 release, the Mobile Data Service has to be manually enabled after installation. Mobile Data Service is now automatically enabled when the BlackBerry Enterprise Server service starts.
BlackBerry Enterprise Server for Microsoft Exchange
2.
Previously, a Mobile Data Service exception (java.lang.NullPointerException) might have been thrown when the handheld disconnected from the Socket Connection, preventing access of streaming applications to Mobile Data Service and effectively stopping the client application from receiving data from Mobile Data Service. This issue is fixed in this release.
3.
In the .cached.properties file, the field called application.handler.tls.allowUntrustedServers is renamed application.handler.tls.allowUntrustedServer in this release, enabling Mobile Data Service to correctly read the field value.
4.
Previously, when a connection request was sent from the handheld and immediately followed by a disconnect, 100% utilization of the CPU might result. This issue is fixed in this release.
5.
Previously, an HTTP Redirection status 302 response code might result from a POST transaction if the resource required by the POST transaction had moved, causing a 'Malformed Content' message on the Browser. This issue is fixed in this release; redirection now returns the correct page on the Browser.
6.
Previously, when a URL contained a character escape sequence, it was not converted by the Mobile Data Service. For example, when '&' appeared within a link, it should have been converted to '&' by the Mobile Data Service; instead the link would fail. This transcoder failure is fixed in this release.
7.
Previously, executing WMLS scripts resulted in a java.lang.VerifyError preventing browsing of the WMLS page. This issue is fixed in this release.
8.
Servers that use response codes that are not in the HTTP specifications prevent data from being sent to the handheld. An exception is caught and reported by the Mobile Data Service when it proxies an unknown response code from a server. This issue is fixed in this release.
About the BlackBerry Enterprise Server The BlackBerry Enterprise Server consolidates the operation of individual Desktop Redirectors into a server that the IT department can monitor and control. The server supports laptop users and enables users to turn off their computers at the end of the day. IT departments manage the centralized administration and control of mobile email, and users can continue to configure email redirection options using the BlackBerry Desktop Software on their PCs. For administrative procedures, please refer to the BlackBerry Enterprise Server for Microsoft Exchange Administration Guide.
BlackBerry Enterprise Server for Microsoft Exchange
5
About the administration software To administrate BlackBerry Enterprise Server(s) in a native Microsoft Exchange 2000, Microsoft Exchange 5.5, or mixed (Microsoft Exchange 2000 and Microsoft Exchange 5.5) environment, you must install BlackBerry Enterprise Server Management Software. BlackBerry Enterprise Server Management functions as a snap-in to the Microsoft Management Console. From the BlackBerry Enterprise Server Management console, you can administrate users at the server level and mailbox level. The BlackBerry Enterprise Server Management 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 console (the interface that enables administration of the BlackBerry Enterprise Server(s) and its users)
About Mobile Data Service The Mobile Data Service is a new feature of this release. After the Mobile Data Service is enabled for users, they can use the handheld Browser to view Wireless Markup Language (WML) pages. The Mobile Data Service manages and alters information so that it can pass between the intranet and the BlackBerry handheld more efficiently. When you install BlackBerry Enterprise Server, you have the option of installing one Mobile Data Service for each BlackBerry Enterprise Server service you install. Direct flow between the handheld application and a network server does not occur all information must pass through the Mobile Data Service first. As the intermediary agent, the Mobile Data Service fulfills two possible functions: •
Data conversion: As a proxy, Mobile Data Service intercepts information passing between handheld applications and the content server. Data conversion might be necessary if the content returning from the server is not appropriately formatted for the application’s needs.
•
Data routing: As a channel, Mobile Data Service passes information back and forth between the handheld application and the content server. The information transferred is “untouched” — the content sent by the application and the content sent by the server are not altered before being passed on to their destinations.
After BlackBerry Enterprise Server with Mobile Data Service and BlackBerry Enterprise Server Management Software are installed, in the BlackBerry Enterprise Server Management console, Mobile Data Service properties enable you to:
6
•
set the connection to the BlackBerry Enterprise Server hostname and port, Push Server Connection Listen Port, Monitor Agent Listen Port, and Web Server Listen Port;
•
configure Hypertext Transfer Protocol (HTTP) properties so that Mobile Data Service can act as a proxy for HTTP messages exchanged between the client handheld and the server;
BlackBerry Enterprise Server for Microsoft Exchange
•
configure TLS (Transport Layer Security) and HTTPS (HyperText Transport Protocol Secure) properties;
•
configure Online Certificate Status Protocol (OCSP) properties (required for S/MIME digital · signing);
•
and configure Lightweight Directory Access Protocol (LDAP) properties (required for S/MIME digital · signing;
About S/MIME and Mobile Data Service The current BlackBerry infrastructure provides secure email transport between your organization’s network and the BlackBerry Wireless Handheld using Triple Data Encryption Standard (DES) encryption technology. This means that email delivered to handhelds is as secure as messages that are delivered to a personal computer on your organization’s network. Secure Multipurpose Internet Mail Extensions (S/MIME) offers an additional layer of security between the sender and recipient of an email message. S/MIME technology enables end-to-end authentication and confidentiality, and protects data integrity and privacy from the time the originator of the message sends it over the BlackBerry wireless network, until it is decoded and read by the message recipient. S/MIME is enabled at the server level (through the BlackBerry Enterprise Server Management console), and on the handheld. Mobile Data Service parameters for Online Certificate Status Protocol (OCSP) properties and Lightweight Directory Access Protocol (LDAP) are required for S/MIME digital signing to work. Configure Mobile Data Service Parameters through the BlackBerry Enterprise Server’s Mobile Data Service Properties window in the BlackBerry Enterprise Server Management console. Warning: Before users can send and receive S/MIME messages, they must install the BlackBerry Desktop Manager with S/MIME Support and update their handhelds to support S/MIME services. After S/MIME is enabled, they can send and receive encrypted messages, attach a signature to outgoing messages, and perform wireless certificate searches.
About the Browser On the RIM 850 Wireless Handheld™, RIM 857 Wireless Handheld™, RIM 950 Wireless Handheld™, and RIM 957 Wireless Handheld™, the Browser only works with the Mobile Data Service. The Mobile Data Service must be enabled for users to use the Browser. On the BlackBerry 5800 Series, BlackBerry 6500 Series, and BlackBerry 6700 Series of wireless handhelds, the Browser works with two types of gateways: a WAP gateway that is operated by the network operator, or the Mobile Data Service (MDS). The Mobile Data Service must be used to access corporate intranets, but it can also be used to access the Internet. Support for WAP or MDS depends on provisioning by the network operator.
BlackBerry Enterprise Server for Microsoft Exchange
7
The Mobile Data Service uses a protocol called the IP Proxy Protocol (IPPP) to communicate with the handheld. Communication between the handheld and the Mobile Data Service is encrypted in the same way as email.
Handheld compatibility Handhelds running with BlackBerry Desktop Software version 2.0 or higher are compatible with BlackBerry Enterprise Server version 3.5 or later. Note that a handheld with software version 2.0 will not support the wireless calendar synchronization feature, as BlackBerry Desktop Software version 2.1 and BlackBerry Handheld Software version 2.1 (or later versions of the software) must be used in conjunction with BlackBerry Enterprise Server version 2.1 (or later versions of the software) in order to support this feature. The wireless synchronization of IT Policy settings and IT Admin commands are available only with version 2.5 of the handheld software for the RIM 850 Wireless Handheld™, RIM 857 Wireless Handheld™, RIM 950 Wireless Handheld™, and RIM 957 Wireless Handheld™ and with version 3.6 of the handheld software for the BlackBerry 5800 Series, BlackBerry 6500 Series, and BlackBerry 6700 Series of wireless handhelds. The Global Address Lookup feature is available only with version 2.5 of the handheld software for the RIM 850 Wireless Handheld™, RIM 857 Wireless Handheld™, RIM 950 Wireless Handheld™, and RIM 957 Wireless Handheld™ and with version 3.6 of the handheld software for the BlackBerry 5800 Series, BlackBerry 6500 Series, and BlackBerry 6700 Series of wireless handhelds.
System requirements The BlackBerry Enterprise Server Software requires the following hardware and software components:
Hardware •
Computer with an Intel® Pentium® III processor or compatible (500 MHz or later, 256-MB RAM, 1-GB hard drive)
Software BlackBerry Enterprise Server works in Microsoft Exchange 5.5 (or later) or Microsoft Exchange 2000 native environments, or in a mixed (Microsoft Exchange 5.5 and Microsoft Exchange 2000) environment.
8
BlackBerry Enterprise Server for Microsoft Exchange
Warning: Universal Serial Bus (USB) drivers have been added in this release and are supported only in a Windows 2000 Server environment. USB support on Windows NT 4.0 Server is not available. USB support in Microsoft Exchange 5.5 is available only on computers on which the Microsoft Exchange 5.5 administration extension installer has been run. USB support does not replicate to all Microsoft Exchange 5.5 administration computers.
This section is divided into software requirements specific to the following situations. •
Installing with Microsoft Exchange 5.5
•
Installing with Microsoft Exchange 2000
•
In all installations
You must install the requirements for either the Installing with Microsoft Exchange 5.5 section or the Installing with Microsoft Exchange 2000 section, and then install the requirements in the In all installations section. The following software is required for the BlackBerry Enterprise Server to function:
Installing with Microsoft Exchange 5.5 •
Windows NT® 4.0 (Service Pack 5 or later) or Windows 2000 Server (Service Pack 1 or later)
•
Microsoft Internet Explorer 5.00 or later if running on Windows NT 4.0
•
Microsoft Exchange 5.5, Service Pack 4 or later mail server environment
Warning: We recommend installing the BlackBerry Enterprise Server service on a computer without Microsoft Exchange 5.5 installed.
•
Microsoft Exchange 5.5 Administrator (Verify that LDAP default settings include the following: Port number value is 389 (this value can be changed to prevent a port conflict with Active Directory, but you must change the LDAP port value in BlackBerry Enterprise Server Management after it is installed), Enable protocol is selected, Windows NT Challenge/Response authentication is selected at the site level and the server level.
Note: If you are using Microsoft Exchange 5.5 in a Windows 2000 environment, you may need to create or modify an existing Exchange55 key in the registry before you can see your routing groups in BlackBerry Enterprise Server Management. Refer to "No routing groups found in BlackBerry Enterprise Server Management" in the BlackBerry Enterprise Server for Microsoft Exchange 5.5 Installation and Getting Started Guide for more information.
•
Before installing BlackBerry Enterprise Server, install the CDO.dll hotfix for Microsoft Product Support Services Knowledge Base article Q312273. You can download the hotfix and obtain information on the Knowledge Base article from:
BlackBerry Enterprise Server for Microsoft Exchange
9
http://www.microsoft.com/downloads/release.asp?ReleaseID=38967&area=se arch&ordinal=1, and then copy the CDO.dll hotfix to C:/winnt/system32/. The
CDO.dll should be version 05.05.79.2655. The following software is required for BlackBerry Enterprise Server Management to function on a Windows NT 4.0 Server. These tools are built into Windows 2000 Server; you need only install them if you are running Windows NT 4.0 Server: •
Microsoft Management Console 1.2: You can download this software from http://www.microsoft.com/downloads/release.asp?ReleaseID=39918&area=search&ord inal=3
After installing Microsoft Management Console 1.2, you should do an initial startup of the installed software (type MMC at the command prompt) before continuing. •
Active Directory Service Interfaces (ADSI) 2.5: You can download this software from http://www.microsoft.com/ntserver/nts/downloads/other/ADSI25/default.asp
Installing with Microsoft Exchange 2000 •
Windows 2000 Server (Service Pack 1 or later)
•
Microsoft Exchange 2000 (Service Pack 2 or later) mail server environment
Warning: We recommend installing the BlackBerry Enterprise Server service on a computer without Microsoft Exchange 2000 installed.
•
Microsoft Exchange 2000 System Manager, on the same computer as the BlackBerry Enterprise Server service
Note: If Service Pack 2 of Microsoft Exchange 2000 is installed on the Microsoft Exchange Server, it should also be installed on the BlackBerry Enterprise Server to update Microsoft Exchange 2000 System Manager.
•
Before installing BlackBerry Enterprise Server, install the CDO.dll hotfix for Microsoft Product Support Services Knowledge Base article Q314606. You can download the hotfix and obtain information on the Knowledge Base article from: http://www.microsoft.com/downloads/release.asp?ReleaseID=38952&area=se arch&ordinal=2, and then copy the CDO.dll hotfix to C:/winnt/system32/.The
CDO.dll should be version 06.00.16.5770.
10
BlackBerry Enterprise Server for Microsoft Exchange
In all installations The following software is required for BlackBerry Enterprise Server Management to function: •
A database tool (MSDE, SQL 7.0, or SQL 2000) must be installed before, during, or after BlackBerry Enterprise Server Management installation, before you can use BlackBerry Enterprise Server Management
The following software is required for Mobile Data Service 1.0 (with BlackBerry Enterprise Server version 3.5) to function: •
Open Database Connectivity (ODBC) 2.6 or later on the Mobile Data Service computer. ODBC is installed with SQL Server (7.0 or 2000) or MSDE; if you are not installing a database tool (which is required for the BlackBerry Enterprise Server Management database), download Microsoft Data Access Components (MDAC) 2.6 or later from http://www.microsoft.com/data/download.htm
•
The BlackBerry Enterprise Server must be able to send HTTP requests through TCP/IP Port 3101 for browsers on Mobile Data Service-enabled handhelds to function properly
•
Java Runtime Environment (JRE) 1.4: This software is provided on the BlackBerry Enterprise Server CD in drive:\tools\. Launch j2re-1_4_1-windows-i586-i.exe and complete the installation. This version of JRE has Java Secure Socket Extension (JSSE) imbedded.
Warning: To install BlackBerry User Administration, BlackBerry Enterprise Server Management must also be installed on the same computer.
Note: BlackBerry Enterprise Server and Microsoft Exchange are not required on the same computer as BlackBerry User Administration. BlackBerry User Administration has the same system requirements but requires different permissions than the BlackBerry Enterprise Server.
Refer to the BlackBerry Enterprise Server for Microsoft Exchange 5.5 Installation and Getting Started Guide or the BlackBerry Enterprise Server for Microsoft Exchange 2000 Installation and Getting Started Guide for further details on the appropriate system requirements for your installation environment.
Firewall configuration The BlackBerry Enterprise Server initiates outbound, bidirectional connections to the wireless network. To support BlackBerry in an environment with a firewall in place, you must configure the firewall to enable the computers running the BlackBerry
BlackBerry Enterprise Server for Microsoft Exchange
11
Enterprise Server within the company to initiate TCP/IP connections to an outside server listening on port 3101. 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) IS used to 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 3101.
Please verify that your firewall is configured to accommodate these types of outbound-initiated connections bidirectionally.
Preinstallation procedures The following procedures are required before you can begin installing BlackBerry Enterprise Server Software. 1.
Defining a service account and mailbox in Microsoft Exchange
2.
Setting permissions on service accounts for BlackBerry Enterprise Server, BlackBerry Enterprise Server Management, and BlackBerry User Administration (if you will install these tools)
3.
Installing and registering CDO.dll
4.
Preparing to create a MAPI profile
5.
Installing database software
If you are migrating from using Microsoft Exchange 5.5 administration extensions to using BlackBerry Enterprise Server Management, the following procedure is also required before you can begin installing BlackBerry Enterprise Server version 3.5 Service Pack 1. •
Exporting system information from the Microsoft Exchange 5.5 administration extensions
It is recommended that you complete the following procedure AFTER you have installed BlackBerry Enterprise Server version 3.5 Service Pack 1. •
Removing BlackBerry Enterprise Server administration extensions
Note: After upgrading to BlackBerry Enterprise Server, you must import the server information you exported from the BlackBerry Enterprise Server administration extensions. Refer to “Importing system information” in the BlackBerry Enterprise Server for Microsoft Exchange 5.5 Installation and Getting Started Guide or the BlackBerry Enterprise Server for Microsoft Exchange 2000 Installation and Getting Started Guide for further details.
12
BlackBerry Enterprise Server for Microsoft Exchange
Installing and registering a CDO hotfix Note: The CDO.dll supplied with Microsoft Outlook does not enable wireless calendar synchronization. (BlackBerry Desktop Software 3.0, a European release, does not support wireless calendar synchronization.) You must install the CDO.dll hotfix (on the BlackBerry Enterprise Server service computer) and the correct administration tool (Microsoft Exchnage System Manager or Microsoft Exchange 5.5 Administrator) to have the correct CDO and MAPI versions.
1.
Verify you are logged on to the BlackBerry Enterprise Server computer as the Administrator.
2.
If Microsoft Outlook is currently installed, remove it.
3.
If you have not already done so, copy the CDO.dll hotfix to C:/winnt/system32/.
4.
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 box, in the Open field, type: regsvr32 cdo.dll
Defining a service account and setting its permissions You must define an administration service account and mailbox. The administration service account acts as your BlackBerry Enterprise Server service account, and requires permissions. If you install BlackBerry Enterprise Server Management, Mobile Data Service, and BlackBerry User Administration, the service accounts for those tools also require permissions. You can use the same administration service account for multiple tools installed on the same computer.
If you are installing with Microsoft Exchange 5.5 Your BlackBerry Enterprise Server service account requires the following Windows NT/2000 permissions: •
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 be set by default
•
Log on as a service: This permission should be set automatically when you install BlackBerry Enterprise Server. Verify that it is set.
AND the following Microsoft Exchange site permissions
BlackBerry Enterprise Server for Microsoft Exchange
13
•
Service Account Admin. permissions on the Site container and Configuration container
AND
•
Local administrator permissions on the BlackBerry Enterprise Server service computer
Your BlackBerry Enterprise Server Management service account requires the following Microsoft Exchange site permissions •
Service Account Admin. permissions on the Site container and Configuration container
AND •
Local administrator permissions on the BlackBerry Enterprise Server service computer and the BlackBerry Enterprise Server Management computer (these might be the same computer)
Note: The service account used by Mobile Data Service to access the database (the BlackBerrry Enterprise Server Management service account), requires read/write access on the database.
Your BlackBerry User Administration service account requires the following Microsoft Exchange site permissions •
Service Account Admin. permissions on the Site container and Configuration container
AND •
Local administrator permissions on the BlackBerry Enterprise Server service computer and the BlackBerry Enterprise Server Management computer (these might be the same computer)
If you are installing with Microsoft Exchange 2000 Your BlackBerry Enterprise Server service account requires the following Windows 2000 and Microsoft Exchange 2000 permissions:
14
•
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 be set by default.
•
Log on as a service: This permission should be set automatically when you install BlackBerry Enterprise Server. Verify that it is set.
•
Local administrator permissions on the BlackBerry Enterprise Server service computer
•
Microsoft Exchange View Only Administrator (minimum) access at the Administrative Groups level in Microsoft Exchange 2000 to be able to read from the Active Directory.
BlackBerry Enterprise Server for Microsoft Exchange
•
Microsoft Exchange Administer Information store, set at the Mailbox store level or the Microsoft Exchange server level (to write information to the administration service account mailbox)
Your BlackBerry Enterprise Server Management service account requires the following Windows 2000 and Microsoft Exchange 2000 permissions: •
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 be set by default
•
Log on as a service: This permission should be set automatically when you install BlackBerry Enterprise Server. Verify that it is set.
•
Local administrator permissions on the BlackBerry Enterprise Server service computer and the BlackBerry Enterprise Server Management computer (these might be the same computer)
•
Microsoft Exchange View Only Administrator (minimum) access at the Administrative Groups level in Microsoft Exchange 2000 to be able to read from the Active Directory.
•
Microsoft Exchange Administer Information store, set at the Mailbox store level or the Microsoft Exchange server level (to write information to the administration service account mailbox)
Your BlackBerry User Administration service account requires the following Windows 2000 and Microsoft Exchange 2000 permissions: •
Log on as a service: This permission should be set automatically if you install BlackBerry Enterprise Server on the same computer as BlackBerry User Administration. Verify that it is set.
•
Local administrator permissions on the BlackBerry Enterprise Server service computer and the BlackBerry Enterprise Server Management computer (these might be the same computer)
•
Microsoft Exchange View Only Administrator (minimum) access at the Administrative Groups level in Microsoft Exchange 2000 to be able to read from the Active Directory.
•
Receive as permissions within the Microsoft Exchange routing group
Note: A user running the BlackBerry User Administration client does not need any permissions.
The setting of these permissions is detailed in the BlackBerry Enterprise Server Software for Microsoft Exchange 2000 Installation and Getting Started Guide and the BlackBerry Enterprise Server for Microsoft Exchange 5.5 Installation and Getting Started Guide.
BlackBerry Enterprise Server for Microsoft Exchange
15
Preparing to create a MAPI profile You must create a MAPI profile to be used by each of the service accounts you created, which may include a BlackBerry Enterprise Server service account, a BlackBerry Enterprise Server Management service account, and a BlackBerry User Administration service account. (The same account can be used for all of these tools.) You can create separate MAPI profiles for each tool, or you can use one MAPI profile for all tools. The MAPI profile(s) can point to the same BlackBerry Enterprise Server administration mailbox. The following procedure verifies that you will be able to create the MAPI profile(s) during the installation of the BlackBerry Enterprise Server, BlackBerry Enterprise Server Management, and BlackBerry User Administration. 1.
Verify that opening either Microsoft Exchange 5.5 Administrator or Microsoft Exchange 2000 System Manager initializes the MAPI subsystem.
2.
Open the Tools folder on the BlackBerry Enterprise Server Software CD.
3.
Run the fixmapisvc.exe utility from the command prompt and specify the mapisvc.inf file as follows: "fixmapisvc.exe c:\winnt\system32\mapisvc.inf". A DOS screen will appear briefly onscreen. The mapisvc.inf file is automatically installed under C:/winnt/system32/.
Installing database software One of the following database tools must be installed if you want to host the BlackBerry Enterprise Server Management database on the BlackBerry Enterprise Server: MSDE, SQL 7.0, or SQL 2000. If you do not have a copy of SQL 7.0 or SQL 2000 you can obtain a copy of MSDE from Research In Motion (download MSDE.zip from: http://www.blackberry.com/support/downloads/msde.shtml). MSDE can also be installed directly from the Microsoft Office 2000 Developer CD-ROM. Refer to the BlackBerry Enterprise Server Software for Microsoft Exchange 2000 Installation and Getting Started Guide or the BlackBerry Enterprise Server for Microsoft Exchange 5.5 Installation and Getting Started Guide for details.
16
BlackBerry Enterprise Server for Microsoft Exchange
Prerequisites for migrating from Microsoft Exchange 5.5 administration extensions The following procedures are required if you want to migrate from using the Microsoft Exchange 5.5 administration extensions to using BlackBerry Enterprise Server Management •
Exporting system information from the Microsoft Exchange 5.5 administration extensions
•
Upgrading to BlackBerry Enterprise Server version 3.5 Service Pack 1
•
Importing system information to BlackBerry Enterprise Server Management
•
Removing BlackBerry Enterprise Server administration extensions
You must complete these procedures in order. Complete the following procedure to export system information from the Microsoft Exchange 5.5 administration extensions before you install BlackBerry Enterprise Server version 3.5 Service Pack 1.
Exporting system information from the Microsoft Exchange 5.5 administration extensions You can use the Export feature on the BlackBerry Servers Properties window to export server information for migration to BlackBerry Enterprise Server Management. 1.
From the Configuration container of the Microsoft Exchange Administration window, double-click the BlackBerry Servers item. The BlackBerry Server Properties window opens.
2.
In the BlackBerry Servers Properties window, from the Server Config list, click Export to open a Save As dialog.
3.
Browse to the desired directory location and click Save to return to the BlackBerry Servers Properties window. A text file, which contains configuration information for each BlackBerry Enterprise Server in the site, is saved in the defined location. The generated text file contains a line for each BlackBerry Enterprise Server in the site. The information includes server name, server mailbox display name, server Domain Name (DN), and BlackBerry Enterprise Server DN.
BlackBerry Enterprise Server for Microsoft Exchange
17
Note: After upgrading to BlackBerry Enterprise Server, you must import the server information you exported from the BlackBerry Enterprise Server administration extensions. Refer to “Importing system information” in the BlackBerry Enterprise Server for Microsoft Exchange 5.5 Installation and Getting Started Guide or the BlackBerry Enterprise Server for Microsoft Exchange 2000 Installation and Getting Started Guide for further details. It is also recommended that you remove the administration extensions after importing the system information. Refer to “Removing BlackBerry Enterprise Server administration extensions” in the BlackBerry Enterprise Server for Microsoft Exchange 5.5 Installation and Getting Started Guide or the BlackBerry Enterprise Server for Microsoft Exchange 2000 Installation and Getting Started Guide for further details.
Installing BlackBerry Enterprise Server version 3.5 Service Pack 1 Warning: Before you install BlackBerry Enterprise Server, temporarily disable any "watchdog" agents (for example, BMC Patrol,NetIQ,Tivoli,or HP OpenManage) that are currently monitoring the BlackBerry Enterprise Server, before proceeding with the installation. Typically, a "watchdog" agent is used to restart services that may stop during normal operation. If you are running a "watchdog" agent, and you do not disable it, it may restart the BlackBerry service without warning during the install process, causing unpredictable results.
To perform an initial BlackBerry Enterprise Server install with Microsoft Exchange 5.5 or Microsoft Exchange 2000, the following tasks are required: 1.
Defining a service account and creating a Microsoft Exchange mailbox
2.
Setting permissions
3.
Installing and registering the CDO.dll hotfix
4.
Installing the BlackBerry Enterprise Server Software
5.
Post-installation procedures
You should perform these steps in the order in which they appear in this document. All of the steps are required unless otherwise stated. For further information on installing BlackBerry Enterprise Server Software, refer to the BlackBerry Enterprise Server Software for Microsoft Exchange 5.5 Installation and Getting Started Guide or the BlackBerry Enterprise Server for Microsoft Exchange 2000 Installation and Getting Started Guide. The upgraded files are version 3.5.1.6. To check the version number, in BlackBerry Enterprise Server Management, select Help > About BlackBerry Enterprise Server Management.
18
BlackBerry Enterprise Server for Microsoft Exchange
Upgrading to BlackBerry Enterprise Server version 3.5 Service Pack 1 Upgrading your BlackBerry Enterprise Server consists of the following tasks: 1.
Installing your software
2.
Restarting the BlackBerry Enterprise Server service (see Post-installation requirements)
To upgrade your software, complete the steps in the InstallShield Wizard as illustrated in the BlackBerry Enterprise Server for Microsoft Exchange 2000 Installation and Getting Started Guide or the BlackBerry Enterprise Server for Microsoft Exchange 5.5 Installation and Getting Started Guide. The upgraded files are version 3.5.1.6. To check the version number, in BlackBerry Enterprise Server Management, select Help > About BlackBerry Enterprise Server Management.
Post-installation requirements Procedures to be completed after you install the BlackBerry Enterprise Server Software include: •
Configuring the BlackBerry Enterprise Server
•
Starting the BlackBerry Enterprise Server services
•
Removing BlackBerry Enterprise Server administration extensions (if you have them installed and have exported your system information)
You should perform these steps in the order in which they appear in this document. All of the steps are required unless otherwise stated.
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. 1.
In the BlackBerry Enterprise Server Management interface, right-click the routing group.
2.
Select New BlackBerry Server.
BlackBerry Enterprise Server for Microsoft Exchange
19
3.
In the Server Name field, type the server name that you provided during the BlackBerry Enterprise Server files installation.
4.
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.
5.
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.
6.
After you complete all of the fields, click OK to close the BlackBerry Enterprise Server System Info 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 verify that the SRP identifier and authentication keys are unique for each BlackBerry Enterprise Server.
Stopping/starting the BlackBerry Enterprise Server services Note: Mobile Data Service is automatically enabled when you start the BlackBerry Enterprise Server service.
The services are installed as automatic services, and they are started automatically after the installation or upgrade. This writes the host name of the BlackBerry Enterprise Server computer to the administration mailbox. If you need to stop and restart the services at any time, complete one of the following procedures: Starting/stopping services through Windows Services If you are using Windows NT: 1.
From the Start button, select Settings > Control Panel to open the Control Panel window.
2.
Double-click Services. The Services window appears.
3.
Stop/Start services: •
20
Select the BlackBerry Server item. Right-click and select Stop to stop the service. 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
BlackBerry Enterprise Server for Microsoft Exchange
startup to Automatic and click OK. Click Start to start the BlackBerry Server service.
4.
•
Select the BlackBerry Mobile Data Server item. Click Stop or Start to stop or start the Mobile Data Service.
•
BESAlert and the BlackBerry Database Consistency Service can also be stopped and started through Services.
Close the window.
If you are using Windows 2000: 1.
From the Start button, select Programs > Administrative Tools > Services to open the Services window.
2.
Stop/Start services:
3.
•
Select the BlackBerry Server item. Right-click and select Stop or Start to stop or start the BlackBerry Enterprise Server service.
•
Select the BlackBerry Mobile Data Server item. Right-click and select Stop or Start to stop or start the Mobile Data Service.
•
BESAlert and the BlackBerry Database Consistency Service can also be stopped and started through Windows Services.
Close the window.
Starting/stopping services through BlackBerry Enterprise Server Management 1.
Open BlackBerry Enterprise Server Management. The Tree view expands automatically and displays a list of BlackBerry Server site/routing groups.
2.
In the Tree view, expand a routing group and right-click a BlackBerry Enterprise Server.
3.
Stop/Start services: •
Select Stop Server or Start Server to stop or start the BlackBerry Enterprise Server.
•
Select Stop Mobile Data Service or Start Mobile Data Service to stop or start the Mobile Data Service.
Now that you have set up the appropriate accounts, installed the executables and created a BlackBerry Enterprise Server, you are ready to use the server and its tools.
Removing BlackBerry Enterprise Server administration extensions If you previously used Microsoft Exchange 5.5 administration extensions to manage BlackBerry Enterprise Server, you should remove the BlackBerry Enterprise Server administration extensions. You must do so AFTER you upgrade to BlackBerry Enterprise Server version 3.5 Service Pack 1.
BlackBerry Enterprise Server for Microsoft Exchange
21
Verify that you have exported all server information from the administration extensions, installed the BlackBerry Enterprise Server version 3.5, and imported the server information to BlackBerry Enterprise Server Management before you remove the administration extensions. Note: Performing this step results in the removal of all defined BlackBerry Enterprise Servers from the routing group configuration.
1.
Log in using an account with administrative privileges (typically, BESAdmin) on the local computer.
2.
From the Start menu, select BlackBerry Enterprise Server > Uninstall Administration Extensions.
Note: If you are using Windows NT 4.0 Server, verify that you have installed Microsoft Management Console 1.2 and Active Directory Service Interfaces (ADSI) 2.5 before installing BlackBerry Enterprise Server Software.
Removing BlackBerry Enterprise Server Software Note: This removal 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. Warning: If you have USB drivers installed, they must be removed separately.
To remove BlackBerry Enterprise Server Software, or to remove individual components such as BlackBerry Enterprise Server Management, Mobile Data Service, BlackBerry User Administration, or BlackBerry utilities, refer to the BlackBerry Enterprise Server Installation and Getting Started Guide chapter, "Removing software".
Additional documentation After you install the software, all documentation is located in the Docs directory, with the installed software. BlackBerry Enterprise Server Management Software offers online Help to guide you and answer your questions. To open the online Help, click Help in the Help menu of any active window.
22
BlackBerry Enterprise Server for Microsoft Exchange
Refer to the BlackBerry Enterprise Server Software for Microsoft Exchange 2000 Installation and Getting Started Guide or the Microsoft Exchange 5.5 Installation and Getting Started Guide for more information about installing the BlackBerry Enterprise Server Software.
Installation Documentation Title
Location on installation CD
BlackBerry Enterprise Server Software for Microsoft Exchange 2000 Installation and Getting Started Guide
Root_directory:\Docs\Installation with Microsoft Exchange 2000.pdf
BlackBerry Enterprise Server Software for Microsoft Exchange 5.5 Installation and Getting Started Guide
Root_directory:\Docs\Installation with Microsoft Exchange 5.5.pdf
Administration Documentation Title BlackBerry Enterprise Server Software Administration Guide
Location on installation CD Root_directory:\Docs\Administration Guide.pdf
If any of these components are missing, contact your point of purchase of your license for BlackBerry Enterprise Server Software.
Package contents Your BlackBerry Enterprise Server Software package should contain the following items: BlackBerry Enterprise Server Software and additional tools
Description
BlackBerryServer.exe
This program redirects email from the user's Microsoft Exchange mailbox to the BlackBerry handheld
BESAlert.exe
This program monitors the Windows NT Event Log and can be configured to send notification to defined users when specified event levels are logged
dbghelp.dll
This .dll file is a helper file for debug logging
BlackBerry Enterprise Server for Microsoft Exchange
23
BlackBerry Enterprise Server Software and additional tools C:\WINNT\System32\BESPerfInfo.dll
This .dll file enables administrators to view dynamic Global Statistics
C:\Program Files\Research In Motion\BlackBerryEnterprise Server\BlackBerryServerSNMP Agent.dll
This .dll file enables administrators to view dynamic Global Statistics
BESManMMC.msc
This BlackBerry Enterprise Server Management (MMC Snap-in) Software is used to administer the BlackBerry Enterprise Server
createdb.exe
This program creates the BlackBerry Enterprise Server Management (MMC Snap-in) database; the database can also be created during the installation of the BlackBerry Enterprise Server Management Software
Utilities
24
Description
Description
BESProfile.exe
This GUI program enables you to edit the MAPI profile being used by the BlackBerry Enterprise Server
DBConsistency.exe
Mobile Data Service’s database consistency utility; runs every 24 hours by default; the update frequency may be changed
BBUserAdminClient.exe
This program enables administrators to add, delete, or list users on a specified BlackBerry Enterprise Server
BBUserAdminService.exe
This service executes the requests made by the BBUserAdminClient
BBPerfMonInstall.exe
This utility repairs the installation of the BlackBerry Enterprise Server Performance Monitor .dll file
BBSRPTest.exe
This utility tests the SRP connection to the wireless network
BlackBerryBackup.exe
This utility enables backup of BlackBerry Enterprise Server and its users
FBUpdate.exe
This utility is a helper program used by the BlackBerry Enterprise Server to force updates to Microsoft Outlook free/busy information
BlackBerry Enterprise Server for Microsoft Exchange
Utilities
Description
HandheldCleanup.exe
This utility enables administrators to retrieve and update configuration for individual BlackBerry Enterprise Server users as well as the configuration information for each BlackBerry Enterprise Server
IEMSTest.exe
This utility tests the permission requirements for a BlackBerry Enterprise Server
fixmapisvc.exe
This utility should be run before creating a new MAPI Profile when the MAPI Profile cannot be found
If any of these components are missing, contact your point of purchase of your license for BlackBerry Enterprise Server Software.
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. © 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 www.rim.net/patents.shtml for a current listing of applicable patents.
This product includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/
Part No.:PDF-04436-032
BlackBerry Enterprise Server for Microsoft Exchange
25
