I am currently running BES for Exchange 4.1.0.38 and would like to upgrade to the latest greatest 4.1.4. As a good data center minion, I now get to fully document every procedure that takes place in my inner sanctum and I need to know the following:
Do I need to install 4.1.1, 4.1.2, 4.1.3 prior to installing 4.1.4?
Any gotchas coming my way?

TIA,
tsarchasm

p.s. I humbly apologize if this question has been asked ad infinitum, please be gentle.

A good question! RIM has a best practice recommendation:

Best practices for installing a BlackBerry Enterprise Server service pack

Service packs are all inclusive of previous versions so you'd just need to do 4.1.4. Is the BES Configuration database local to the BES running on MSDE or is it remote?

You might also look to install the released maintenance releases too ... they are all inclusive of each other so MR2 can be installed without MR1, but you need to have SP4 on first.

Thanks for the fast reply, We are on SQL 2000 SP2, now I need to figure out how to migrate this to our SQL 2005 database server.

Search through the forums here and at BlackBerry Technical Solution Center ... look for "move sql" or "sql migration" ... you'll find lots of references.

Insert the disk...next, next, next, make cup of tea, re-boot server and relax..

It's pretty painless but BACKUP first the database, reg entries etc. and make sure you have original disks, and paper records of SRP ID & Auth code & CAL details.. just in case it all goes a bit strange..

My worst was a 3.6 to 4.0 upgrade, which to get working I had to hose the OS and start from scratch - but the original 3.6 implementaiton (not mine) was pretty screwy anyway!

Yeesh, the 3.6 to 4.0 upgrade was the stuff of nightmares.

Okay, I'm resigned to doing a db migration first, I have roughly 200 users living in that database, if all goes well, how long you think to move everything and bring the BES back up? The Change Advisory Board is breathing down my back.

I recently completed the upgrade from 4.1 to 4.1.4 and I was surprised how painless it was.

The only hic up during the install was for some reason my Auth code was not accepted. I had to call tech support and they generated a new code for me.

Good luck.