[billpoly]

Hello-

I recently upgraded a customer's Exchange-integrated BES from 4.1.3 to 4.1.6MR5. The only problem is as follows-

One thing that is not working correctly is the calendar management from BBY handheld to Outlook. All changes made in outlook are updating on the handheld but not vice versa. If I remember correctly this may have something to do with permissions or send as functionality.

The Exchange server is running on an SBS 2003 server, and the BES is running on a different server. Any suggestions?

Best,
Bill

[bmwilson1978]

Yep, possibly permissions - was bidirection calendar sync working prior to the upgrade? I presume the upgrade was performed as the BESAdmin service account? Does the problem happen with all BlackBerry users or some?

Confirm the ESM version (including SP level) and CDO.dll version on the BES is the same or later as what is running on the Exchange server.

Are there any MAPI error messages mentioned in the MAGT log files?

[stuwhite]

Did you actually check the perms?
Is the user a member of one of the protected groups? Perms might be getting revoked if so.

[billpoly]

stuwhite-

What permissions should I be checking? What are the protected groups? Sorry - I'm pretty new at this.

Calendar sync was working prior to the upgrade, so I assume that the basics are intact and the upgrade is the source of the problem (or something that happened during the upgrade).

[billpoly]

bmwilson1978-

Bidirectional calendar sync was working prior to the upgrade. I performed the upgrade as the domain admin account, which in the case of this customer is the same as the BESAdmin service account. The upgrade is happening with all users.

I'll check the log files and post any error messages that I find.

Thanks!

[stuwhite]

Originally Posted by billpoly

stuwhite-

What permissions should I be checking? What are the protected groups? Sorry - I'm pretty new at this.

Calendar sync was working prior to the upgrade, so I assume that the basics are intact and the upgrade is the source of the problem (or something that happened during the upgrade).

No worries, we all started somewhere! Check the BESadmin perms section in this thread - http://www.blackberryforums.com/bes-...es-thread.html and ensure you have the perms applied for besadmin as directed on the user account in question.

Protected groups -

http://www.blackberryforums.com/bes-...ml#post1338365 - if the user is a member of one of these groups, the sendas perm will be revoked after you set it.

[billpoly]

Thanks, stuwhite!

It looks like the upgrade either wasn't performed as the BESAdmin account or the BES services were all switched to the domain admin account for some reason. Switching all services to an already existing BESAdmin account seemed to do the trick.

[stuwhite]

Originally Posted by billpoly

Thanks, stuwhite!

It looks like the upgrade either wasn't performed as the BESAdmin account or the BES services were all switched to the domain admin account for some reason. Switching all services to an already existing BESAdmin account seemed to do the trick.

Cool. As long as all upgrades and patches are done as besadmin you should be fine. Make sure your customers know that the services (except attachment) need to run as besadmin, and they shouldn't change them.