As many people know, I am a big fan of BES and the devices in the enterprise. I am also a fan of Traveler. But these are two very different beasts.
Traveler is free, and you get what you pay for. It is a fully functional mail / PIM tool for multiple devices. It does this very well. For free. It uses it’s own client and SyncML or Activesync when needed, depending on the device.
Blackberry Enterprise server is also this and a whole lot more. Much more customisable, much more malleable, much more secure, much more functional in the application space, a web proxy and a total extension of your corporate world. It routes all messages through military secure NOC’s globally with many certifications for encryption. It is not as consumer focused as the typical Traveler devices. Because Blackberry came from the enterprise world.
Many companies only see the word “free” and going down the path of Traveler. Some are abandoning their BES architcture and license costs for Traveler. This is fine as long as it suits your business. On a number (more then 4, less then 10) of times I have been asked the following types of questions by operations teams that now support Traveler.
Q: “Can I control all the devices fully with Traveler”
A: Not really
Q: “I have been told to implement clustering for it. Does it support it?”
A: Not really. Or at all, depending on how you look at it.
Q: “I want to push out secure applications to the devices”
A: I hate to disappoint.. but.
Q: “I have been asked to disable xx applications on the devices now. Can I do this in Traveler?”
A: “In some cases yes, but in many no”
Q: “I want to use Traveler to control all data on the devices, and disable some of its features. Can I do this in Traveler?”
A: “It depends, but simple answer is you don’t have full control anymore”
Why? Because you get what you pay for. If you want the hammer to hit the nail, go with Traveler. But don’t give your operations team grief when you want to use the hammer to build a fort. It doesn’t work that way. Buy a BES.