I see this time and time again. A user is having problems with his device so after some basic troubleshooting you decide to wipe and reactivate the device ...

You don't remove the user from the BES because you don't want to have to setup Groups / IT Policy / Software Configuration ... and you don't want to lose Automatic Wireless Backup data ... but the user wants his messages back.

Well, as we all know, there is no way to guarantee you'll get all of your messages...

Welcome to Part 2 of at least a 20 part series looking at the BES logs. (Part 1)

Each day I'll talk about a specific type of log file and hopefully we'll all learn something.

The ALRT log is fed data through the BlackBerry Alert service. The BlackBerry Alert service also feeds data to the Windows Application log. You'll notice a duplication of data in the ALRT log and Windows Application log.

For those of us that do event log scraping or have triggers...

I really wanted to title this series: BES Logs ... do I really care?

... but if anyone knows me, you know I love the logs and just couldn't say a bad thing about them. Why, you ask? Are you ready for the answer ... The logs don't lie. Users lie ... administrators lie ... but the logs tell us like it is.

Over the next 20 days, each day I'm going to talk about one specific BES Log file along with:

• What function it serves
• What service(s) feed it information
• A

...

BlackBerry® Enterprise Server 5.0 officially rolled in support for Microsoft® SQL Server® database mirroring.

Historically BES Administrators were forced to either setup transactional replication or some form of manual (or scripted) log shipping to achieve high availability with their BlackBerry® Configuration Database. While other methods of high availability exist for SQL Server such as Neverfail or Veritas Cluster Server, they aren't officially supported by RIM (even if RIM uses...