bes 5.0 nightmare

Well BES 5.0, so far anyway, sucks. It sucks to get set up, the interface sucks, the it policy area looks like something that was designed as a rough draft on a white board and then just put into the product and so many other issues I really can't list them all.

got my 8900

So far so good, really enjoying the 5.0 OS

Would you move to BES 5.0

Honestly,

Is the ability to move flagged messages, forward calendar appointments, really that ground breaking? accessing public folders ( which by the way, Microsoft is getting rid of anyway, or moving away from and towards sharepoint ) really going to make you move to a platform that we have proven isn't very stable and well documented?

For me and my clients, so far that answer is a resounding no.

BlackBerry Enterprise Transporter

So lets talk about the Transporter

The transporter has two different modes

In live mode, you can move user accounts when the BlackBerry® Enterprise Server instances
in both the destination BlackBerry Domain and the source BlackBerry Domain are running. If
you choose this mode, the BlackBerry Enterprise Server instances in both BlackBerry Domain
instances must use different SRP IDs.
In this mode, the BlackBerry Enterprise Server instances in the destination BlackBerry Domain
must be running. This must occur so that the BlackBerry Enterprise Transporter can monitor
the organizer data synchronization and calendar synchronization processes and IT
administration commands (such as Resend IT Policy or Switch Service) that the destination
BlackBerry Enterprise Server instances send to the BlackBerry devices to complete the
migration process.

In bulk mode, you can move all user accounts on a BlackBerry Enterprise Server. During the
migration process, you must turn off the BlackBerry Enterprise Server instances in both the
source BlackBerry Domain and the destination BlackBerry Domain. In the destination
BlackBerry Domain, however, you must turn on the BlackBerry Administration Service.

BRK issues

So BRK 4.1.6 has issues that RIM knows about and refuses to fix for whatever reason. Either they don't have developers to do it, or they are pushing everyone towards BES 5.0. Whatever the reason is, it really is sad that they won't even publish a KB article addressing the problem. So many companies have build entire infrastructure around this software, and to not acknowledge this problem is lame to say the least.