I've spent a fair amount of time this week deploying a Blackberry server and handsets for my new company (well, not my company, but you know what I mean). I haven't installed a Blackberry Enterprise Server since version 3.6, we are now on version 4.1 and the installation routine has been updated and simplified slightly in the new version:

  • You don't need to muck around with cdo.dll anymore. The DLL and Patch that used to be required for cdo.dll is rolled into Windows Server 2003 SP1.
  • You don't need to install MSDE anymore. It's done automatically by the BES setup program.
  • Since MSDE is set up for you, all of the choices to do with the SQL database have been removed from the setup program.

The BES I have been configuring is actually running in a virtual environment, which is a concept new to me ... but the end result is exactly the same as if it was installed on a physical server.

My next task has been documenting the configuration. This involves creating an extremely detailed Word document (using a standard company template) detailing the configuration with diagrams and installation instructions, and a 2nd document which will be a single sheet containing all the basics you would need to know if you were left to look after a bunch of Blackberry users for a few weeks. Good documentation is incredibly valuable but it's such a time consuming process (and not my most favourite thing to do ....)


Blackberry Topology

Blackberry Server tip of the day

Blackberry log files have to be kept in check or they will slowly consume all of your free disk space. I would recommend turning logging off completely, and then just switching it on for troubleshooting if required.

Start > Programs > Blackberry Enterprise Server > Blackberry Server Configuration

On the Logging tab, change all instances of “Debug log daily file” to “No”.

Technorati Tags: , ,