I'm building a new installation of BES 4.1 on Server 2003, so I can replace my crummy BES 4.0-that-is-also-installed-on-the-machine-running-Exchange setup that I have now.

I did a fresh install of 2003, and then set up SQL Server. I then used SQL Server's copy wizard to move my BESMgmt database from the old server to the new one. Then I configured MAPI, made the BES admin account with correct permissions (I hope), etc.

I then installed BES 4.1 and upgraded the 4.0 database. Then I moved some test users over to the BES 4.1 manager.

If you fire up the BES 4.1 services, users can send emails from their handhelds and two-way sync their calendars. This is good.

However, the handhelds DO NOT see changes made in the Outlook inbox that are made at the desktop. If you sit at your desk and send an email, nothing shows up on the handheld. This is no good

Eh, I kinda solved my own problem. If you move a user over to the 4.1 and then perform Enterprise Activation on their device, it works.

What I did, originally was this:

- I have old server OLDBES and new server NEWBES.
- OLDBES is version 4.0.5 with hotfix 2.
- I built up NEWBES to 4.0.5 with hotfix 2.
- I migrated the SQL db to NEWBES using MS SQL copy.
- I configured the MAPI on NEWBES using the Bes Admin account with appropriate permissions in Exchange.
- I tested the NEWBES by moving one user to NEWBES from OLDBES. Tested email, etc., worked great.
- I upgraded NEWBES to 4.1
- Tested my one user, he can make calendar appointments, and send mail, but mail sent in Outlook at the desktop is not seen by the handheld.
- Performed Enterprise Activation again
- Now one user under NEWBES works great.

So, something must be happening during EA that enables the user to work with the new 4.1 database (resending the service book?) Hope that helps somebody else who runs into this problem.