User guide

Wireless Continuity for BlackBerry Requirements Licensed Customer Confidential
28 Email Continuity Administrator Guide version 6.5 (1st ed.)
Windows Authentication Limitations
The following are known limitations for Windows Authentication:
• Disabled Active Directory accounts cannot log in.
• Windows NT login IDs cannot be used; there is no way to ensure that an
NT ID is globally unique. The SMTP address is a unique identifier.
• In multi-domain forests, sufficient trusts must be in place between
accessible domain controllers between domains to authenticate users.
• By design, if an Active Directory account is locked, the user’s logon will fail
for Email Continuity even if they have not exceeded the Max Password
Attempts count.
• If a user changes his Active Directory password after having logged in and
cached his password in Email Continuity, the cached password remains
the Email Continuity password until the Cached Windows Password time-
out expires.
Wireless Continuity for BlackBerry Requirements
To use Wireless Continuity for BlackBerry, the following requirements must be
met:
• Blackberry device software versions 4.1 or greater must be installed;
earlier versions of device software are not supported.
• BES 4.1 and later.
• The MDS service is running on all BES servers.
• The SyncManager software has network access to the BES databases by
Window NT authentication.
• If using MSDE, the service account needs read permissions for the
directory where the BESMgmnt_data.mdf and Besmgmnt_log.mdf
reside.
• The RedirectorController software must be able to post HTTP requests to
the BES systems that have push capability.
• Each user’s display name must match the name on the host where his
BlackBerry device is cradled. If a user’s name changes, the MAPI profile
on the host must be changed as well.
• It is possible to have multiple instances of the MSDE/SQL installed on any
one host. However, if your environment includes only one database
instance on one host and provides for auto-detection, the installation
process auto-detects the correct instance. If your environment does not
provide for auto-detection, you must set this manually.