 |
Categories |
|
|
| |
Most Popular This Week |
|
|
| |
Most Popular This Month |
|
|
| |
Most Downloaded This Month |
|
|
| |
Most Downloaded This Week |
|
|
|
| Home : BlackBerry Documentation : BES MS Exchange |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
BES MS Exchange Listings
|
|
Total:
8 | Displaying: 1 - 8 |
|
|
|
Upgrading to BlackBerry Enterprise Server version 4.1
When you upgrade to BlackBerry Enterprise Server® version 4.1, the changes to your BlackBerry® environment depend on the version from which you are upgrading.
If you are upgrading from BlackBerry Enterprise Server version 3.5.2 or BlackBerry Enterprise Server version 2.1.5,
the upgrade process updates your BlackBerry Enterprise Server software, removes Microsoft® administrative
extensions, creates a new schema for the BlackBerry Configuration Database, and migrates users to the new schema.
If you are upgrading from BlackBerry Enterprise Server version 3.6, the upgrade process updates your BlackBerry Enterprise Server software, consolidates BlackBerry Enterprise Server instances, creates a new schema for the configuration database, and migrates users to the new schema.
You can preview the user migration into the configuration database to identify any issues that might occur (for example, identifying inactive users that you cannot migrate) and to estimate the time that it should take to migrate users during the upgrade process.
If you are upgrading from BlackBerry Enterprise Server version 4.0, the upgrade process updates your BlackBerry Enterprise Server software, including any BlackBerry components that you installed separately (for example, the BlackBerry Manager), and upgrades the schema of the configuration database.
In a mixed-version environment that includes BlackBerry Enterprise Server version 3.6 and earlier and BlackBerry
Enterprise Server version 4.0 or later, your Mobile Data Service push server must be version 4.0 or later.
After you upgrade the Mobile Data Service to version 4.1, the service name becomes BlackBerry Mobile Data System™ (BlackBerry MDS™) Connection Service.
Version: 4.1 - Updated: 24/02/2006
|
|
|
Administrative roles
The BlackBerry Enterprise Server® uses predefined roles, which correspond to common corporate administrative roles, to control who can perform specific tasks and limit who can access sensitive data.
You assign either trusted Microsoft® Windows® users or groups, or SQL logins to each role. If you already manage your organization using Windows groups, assign those groups to the administrative roles so role membership is managed through the group.
This and more in the BES Administartion guide 4.1 for Exchange
Version: 4.1 - Updated: 24/02/2006
|
|
|
The BlackBerry Enterprise Server® - BES - consists of services and components. The BlackBerry® services are designed to provide productivity tools—such as email, instant messaging, and personal information management (PIM) functionality—and data from enterprise applications to mobile users. The BlackBerry components are designed to monitor BlackBerry services; process, route, compress, and encrypt data; and communicate with the wireless network.
You can install all BlackBerry components on one computer, or you can install particular components on separate computers. Consider any impacts on system resources when deciding where to install a component.
You can choose only one setup type for each computer in your environment.
Version: 4.1 - Updated: 24/02/2006
|
|
|
Architecture overview
The BlackBerry Enterprise Server® consists of services and components. The BlackBerry® services are designed to provide productivity tools—such as email, instant messaging, and personal information management (PIM) functionality—and data from enterprise applications to mobile users. The BlackBerry components are designed to monitor BlackBerry services, to process, route, compress, and encrypt data, and to communicate with the wireless network.
Components
Component Description
BlackBerry Attachment Service
The attachment service is designed to convert supported attachments into a format that users can view on the BlackBerry device.
BlackBerry Collaboration Service
The collaboration service is designed to provide an encrypted connection between the instant messaging server and the enterprise messenger application on the BlackBerry device.
BlackBerry Configuration Database
The configuration database is a relational database that contains configuration information that is used by the BlackBerry components that do not connect to the messaging server directly. The configuration database includes the following information:
•details about the connection from the BlackBerry Enterprise Server to the wireless network
•user list
•PIN-to-email address mapping for connection service push functionality
•read-only copy of each user security key
BlackBerry Controller
The BlackBerry Controller is designed to monitor the BlackBerry components and to restart them if they stop responding.
BlackBerry Dispatcher
The BlackBerry Dispatcher is designed to compress and encrypt all BlackBerry data. It routes the data through the BlackBerry Router to and from the wireless network.
BlackBerry Manager
The BlackBerry Manager is designed to run on the administrator’s computer and to connect to the configuration database for remote administration.
BlackBerry Mobile Data System™ (BlackBerry MDS™) Connection Service
The connection service is designed to provide users with access to online content and applications on the corporate intranet or the Internet.
BlackBerry MDS Services
The BlackBerry MDS Services are designed to provide connectivity between BlackBerry MDS Studio™ Applications on BlackBerry devices and enterprise applications.
BlackBerry MDS Studio Application repository
The repository is designed to manage and store BlackBerry MDS Studio Applications.
BlackBerry Messaging Agent
The messaging agent is designed to connect to the messaging and collaboration server to provide message, calendar, address lookup, attachment, and wireless encryption key generation services. The messaging agent also acts as a gateway for the synchronization service to access PIM data on the messaging server. It synchronizes configuration data between the configuration database and the message store user databases.
BlackBerry Policy Service
The policy service is designed to perform administration services wirelessly such as sending IT policies and IT commands, and provisioning service books.
BlackBerry Router
The BlackBerry Router is designed to connect to the wireless network to route data to and from the BlackBerry device. It is also designed to route data within your network to BlackBerry devices that are connected to the user’s computer using the BlackBerry Device Manager.
BlackBerry Synchronization Service
The synchronization service is designed to synchronize PIM application data between the BlackBerry device and the messaging server wirelessly.
corporate application and content server
The corporate application and content server is designed to provide push applications and intranet content for the BlackBerry MDS Services.
instant messaging server
The instant messaging server stores instant messaging accounts.
messaging and collaboration server
The messaging server stores messaging accounts.
Version: 4.1 - Updated: 20/02/2006
|
|
|
CDO and Outlook are both MAPI applications, meaning that they use MAPI APIs to access their data and, therefore, the underlying providers. CDO and Outlook share a common set of Properties that, when taken together, define different classes of messages and different functionality. This works similar to the schema in a database; however, MAPI32 does not implement the storage. The Message Store Provider does. In the case of Exchange Server, this provider is EMSMDB, and Exchange Server is mostly agnostic about the semantics of the data that applications choose to store. Exchange Server 5.5 has almost no knowledge of individual named property meanings. Exchange 2000 Server and Exchange Server 2003 are considerably more aware of the significance of particular named properties on different message classes, in particular, calendar items. This logic is implemented in EXOLEDB and EXCDO. In general, it is up to users of a particular set of properties to agree on what those properties mean and how they are manipulated.
Updated: 17/02/2006
|
|
|
Complete Installation Guide BlackBerry Enterprise Server (BES) for Microsoft Exchange version 4.0. Version Microsoft Exchange 5.5, 2000 & 2003.
Step by step installation. Manual - Documentation.
Version: 4.0 - Updated: 14/05/2005
|
|
|
BlackBerry Enterprise Server (BES) for Microsoft Exchange Documentation
BlackBerry Enterprise Server is designed to provide IT departments with simplified management and centralized control of wireless devices in a secure, scalable and flexible architecture that leverages existing infrastructure and investment
For information on all the components of the BlackBerry solution for the enterprise visit the Solutions section.
Updated: 18/04/2005
|
|
|
| This BlackBerry Enterprise Server for Microsoft Exchange 2000/2003 Installation and Getting
Started Guide will help you
• set up the accounts, permissions, and profiles required for installation
• install or upgrade the server software
• answer frequently asked questions about the installation
• describe error messages that you might encounter during the installation
Version: 3.6 - Platform(s): BES Exchange - Updated: 17/03/2005
|
|
|
 |
 |
| BlackBerry Links and BlackBerry Resources (C) 2005 |
|
| |
|
