Archive for the ‘BES’ Category


For BES Plan Make sure of this, even though the setting is Default.

BES Configuration.

If you are at a company and you are on a BES 4.0, your Administrator must enable the “” setting on the BES. This is a new setting in the Version 4.0 of BES. BlackBerry IPModem

Set the enable IP Modem IT Policy to False under the Security Policy Group in the IT Policy menu.

  1. Open BlackBerry Manager by navigating to Start > All Programs > BlackBerry Enterprise Server > BlackBerry Manager.
  2. On the left-hand side, click on BlackBerry Domain.
  3. On the right-hand side, click on the Global tab.
  4. Click Edit Properties.
  5. On the left-hand side, click on IT Policy.
  6. On the right-hand side, click on IT Policies.
  7. Click the button to open a new dialog box.
  8. Select the appropriate IT Policy and click Properties.
  9. On the left-hand side, select the Security Policy Group.
  10. On the right-hand side, select Enable IP Modem.
  11. Set to False to turn on the IP Modem functionality on the BlackBerry smartphones assigned to this IT Policy.

Happy To Help

A word of advice, please do not install any unwanted / unnecessary apllications on your Blackberry. By doing so, it will reduce clutter and free up much needed memory for your Blackberry to perform.

  1. Save your pictures onto your memory card instead of your device.
  2. Uninstall all unwanted language packs (This can be done by using you Desktop Manager).
  3. Run backups on Desktop Manager every month.

These are the major things that you can do to save some space on your Blackberry.

Just my two cents.


Please remember that when installing BES for Exchange using local MSDE, disaster recovery does not mean cutover.

Time and again I have reminded my mentors about this, but they keep on using the BlackberryDBBackup.exe tool on the primary BES to backup the MSDE (BESMgmt) and move it to a new server and then use the BlackberryDBRestore.exe tool to restore it there.

This would result in having the BES name following the primary BES computer name.

The correct method is just to use a remote SQL server. So that failover is almost seamless.

Installing the Blackberry Enterprise Server (BES) is a cinch. But to get it running is another thing. When something goes wrong, there are a lot of variable that can contribute to the problem.

Even after you manage to install the software, with correct permissions, maitenance releases packs etc… there will be problems with email delivery as it is closely linked with any one of the three mailservers (Groupwise, Domino and Exchange).

Troubleshooting involves studying the lgs files, checking permissions, etc. Usually, the clients need it repaired “immediately”, and it involves some Telco dude breathing down your neck… asking you what you are doing at every step.

Life certainly sucks for us BES Admins. Luckily we’re not Ce**** vendors. They toil so much for the Telco, who are slave drivers. But in the end, the vendor gets no credit.

Anyway… this is just my opening post. Just to let you know that BES is also covered on Suka Blackberry.

See you soon.