The Nexus Service offers a BlackBerry Enterprise Server (BES) for the connection of BlackBerry devices to the Microsoft Exchange element of the service. All connections to the service are governed by the University IT Rules and Regulations, the Nexus Service Level Description (Exchange) and these Terms and Conditions.
All devices connected to the service are treated as personal devices.
2. Exchange Integration
The Nexus BES will synchronise the following types information to BlackBerry devices which are capable of receiving them:
- Calendar Entries
Integration is provided by a BlackBerry Enterprise Server (BES) hosted as part of the Nexus infrastructure. As with other elements of the Nexus service, the BES service is configured as a two-site highly-available solution.
3. SharePoint Integration
The Nexus BES does not provide support for using SharePoint on a BlackBerry at this time. As SharePoint is a web-based application, it can be used via the standard BlackBerry web browser however the small screen size may limit usage.
4. Device Support Policy
All connected devices are treated as personal rather than corporate (University-owned) devices. As such OUCS recommend that users contact their local ITSS for support. If they are unable to provide support, for the actual device, then OUCS will do so on a best-efforts basis.
The connection of any BlackBerry device to a BES server requires that an IT policy is pushed to the device. The IT policy delivered by the Nexus BES is documented in the appendix below. In summary the policy will not inhibit the use of any features of the BlackBerry. It will not monitor usage and will set limits only where applicable to the connection between the device and the Nexus BES.
The device owner is responsible for ensuring that the device firmware is at an appropriate level to allow connection to the Nexus BES, including any upgrade that may be required. The device owner is also responsible for the purchase of the device, and any contracts or fees required for making use of the device with the Nexus BES. Not all mobile service provider contracts include a BES element when a BlackBerry device is purchased/used. OUCS urge the device owner to ensure that they have a "BES-enabled plan" for their device prior to requesting connection to the Nexus BES.
5. Service Support Policy
OUCS provide full support and documentation for both activating the connection between and BlackBerry device and the Nexus BES, and for using the device with the Nexus BES. Any documentation is based upon the Nexus Team's test BlackBerry and there may be differences with other BlackBerry models. Problems with the service should be reported through the usual channels to OUCS.
Device remote wipe is not supported at this time.
Remote device backup is not supported at this time.
Device monitoring is not supported as all devices are treated as personal devices.
MDS service are not supported at this time.
6. Service Activation
The Nexus BES will perform over-the-air activation where possible. If a device cannot be activated over-the-air, then first the device owner should confirm they have a BES capable contract with their mobile service provider and then contact OUCS. OUCS will attempt to activate the device via a USB cable to a BES-connected PC at OUCS if over-the-air activation proves unsuccessful.
7. Service Configuration and Limits
When a connection to the Nexus BES is activated, the BES will populate the BlackBerry with messages from the Nexus mailbox. The Nexus BES is configured to populate up to 750 messages going back 14 days.
Due to the time/cost involved in downloading large attachments to a BlackBerry, the Nexus BES limits the size of attachments that can be sent. This limited is 3MB per attachment/5MB in total for all attachments. For attachment downloads, a 5MB limit applies.
Each BlackBerry device connected to the Nexus BES requires a BES Client Access License (CAL). CALs are sometimes provided with BES-enabled mobile contracts. For those who do not have a BES CAL code, OUCS will provide one for the lifetime of their connection to the Nexus BES at cost price. After the device owner has left the University, a personally owned CAL will be removed from the Nexus BES and a confirmation, that this has taken place, will be sent. If a Nexus-owned CAL is in use, then ownership of this CAL will return to OUCS for re-use.
OUCS ensure the central BES component is licensed and appropriately supported.
There is currently no charge for connecting a BlackBerry device to the Nexus BES. If a BES Client Access License (CAL) code is not supplied/available then OUCS will provide a license, for the lifetime of the device's connection to Nexus, for 35 pounds+VAT.
10. Appendix 1: Default IT Policy Details
The Nexus default IT Policy is set as per the values contained in the following Blackberry documentation: RIM BlackBerry Enterprise Server 5.0.1 Default IT Policy