For a long time I’ve played by the RIM rules in believing that an Exchange email account can only be linked to one BlackBerry handset through a BES server. The wording is exactly right, but the ‘one handset’ limitation can be overcome with a little planning.
Here’s the environment that I’ve tested this on;
- Windows Server 2003 R2 with all service packs
- Exchange Server 2003 SP2 with all service packs
- BlackBerry Enterprise Server 4.1.6.10
Other items you’ll need;
- 1 spare Exchange CAL per user
- 1 spare BES CAL per user
- Spare BlackBerry handset – I’ve used 8310, 8320 and 9000
- Spare BES actived SIM
How it works
- Create a new user in Active Directory (I used firstname2@domain.com for the email address)
- Create a new user on your BES Server and select firstname2@domain.com for that user
- Activate the spare BlackBerry with the SIM for firstname2@domain.com
- Finally enable email forwarding from the first account to the 2nd account
New email will start flowing to the 2nd BlackBerry as Exchange forwards it from the primary account to the secondary account. Personal Address Book synchronisation can be achieved through a manual export and import, and the same with calendars.
Pitfalls
- 2 mobile phone numbers, although one can be put on permanent divert to the other
- 2 SMS locations – SMS messages cannot be routed from one SIM to another at the network level
- Calendars – you’ll need to invite two users (firstname and firstame2) to the same meetings so the the entry appears on both handsets
- 2 BlackBerry Messenger clients – this has caused confusion, with some people deleting the primary contact once the second handset added them
- Handset rebuild – if you need to rebuild the primary or secondary handset, you MUST DISABLE email forwarding, otherwise the activation process on the handset doesn’t complete
Conclusions
This is by no means an easy solution. However if your users demand a 2nd handset for emergency email, it is possible. Set the expectations right, and this just might save your bacon.
