Blackberry Send-As / Exchange Permission Cache

The Send As permission is stored in Microsoft Active Directory and read by the Microsoft Exchange Server when the user attempts to send an email from the BlackBerry smartphone. Once the permission has been read by the Microsoft Exchange Server, the Microsoft Exchange Server will now cache the Send As permission (either Allow or Deny) for 2 hours, which if a Deny Send As permission for the user is in the Microsoft Exchange permission cache, it will still prevent the user from sending email from their BlackBerry smartphone.

If it has been confirmed that the Send As permission is applied to the user’s account in Active Directory Users and Computers and they still cannot send email from their BlackBerry smartphone, then the Microsoft Exchange permission cache must be cleared before they can send email again.

Restart the Microsoft Exchange System Attendant and Microsoft Exchange Information Store. Restarting these services purges the Microsoft Exchange permission cache and Microsoft Exchange will read the current Send As permission from Microsoft Active Directory when the next the user sends an email.

Important Note : Restarting the Microsoft Exchange System Attendant and Microsoft Exchange Information Store is not recommended by Research In Motion.

BES Express Network Bug

There was a major bug discovered in BES Express but has since been fixed in very recent releases. Sherry installed BES-X around May 15, and by May 25 it was fixed… The bug causes random problems with registering blackberry phones. This problem only occurs on networks where there is a zero in any of the octets. In this case, Shasta Mosquito, is a 10.0.0.0/24 network – so there was the problem. Updating the BES server to the latest release (or more specifically any release after 5.0.12) resolves this issue.

Powered by WordPress.com.

Up ↑