Blackberry isn't so easy to crack Hi,
Excuse me if I'm stating the obvious here, but I recently came to understand a little bit about how the whole RIM/BB/Exchange set-up works and I thought it might help others too.
I happened to be talking to a RIM integrator recently and he told me that in a corporate scenario when a new BB handset is set-up, a GUID is registered with RIM who then list the company's specific BES server as the only allowed originating server for that handset. I think the terminology is: "homing" the device. It means that RIM get to know about every device out there, plus the device will only communicate with the BES it's registered with. Apparently BES is also very strict about the Exchange message store from a security standpoint. Other features are that homed handsets can be controlled from within BES for updates/remote wipe/etc. and devices can be locked so that users can't install software on them...
The "RIM way" appears to provide excellent security (registered handsets only), a reliable and good user experience (validated handsets only), and device management (essential for corporates), not to mention plenty of $'s for RIM...
In my naivety I had always assumed that the Zimbra BB solution would involve getting the BB handset to sync natively with the Zimbra server (without the need for BES) using a reverse engineered version of RIM's sync protocol, rather like Zimbra have done with Active Sync. However I now realise that this would not only be a large task, likely requiring custom software on the device, but would defeat the whole reason for running a BB solution - in effect it would be a lengthy and costly way to do what we can do now with Active Sync + many current devices.
So it seems, if this is what has been done, that keeping BES in the mix and "simply" replacing exchange with Zimbra as the back-end store is a sound direction and will hopefully allow us to offer a complete BB solution. A solution which should really rock :-)
Can't wait to see it in action...
Cheers,
Marc |