Wednesday, 12 August 2009
Blackberry Calender not Synchronising Both Ways
We've had a long-standing problem at work where appointments added to Blackberry handset do not show up in Outlook.
We run Balckberry Professional Software 4.1 which is a cut-down version of Blackberry Enterprise Software (BES) for small businesses and Exchange 2000. The problem only affected a small number of out users but was naturally frustrating. I searched for solutions via Google and tried my own troubleshooting. Evenually, I asked for support form Gen-i who sold us the software.
They pointed me in the direction of the "send as" and "receive as" permissions on the mailboxes in question. I could see that the BES account was denied those permissions on the affected accounts, but this setting was being inherited and I could not figure out from where. Further research showed that some built-in accounts are denied these permissions by default.
I needed to use the Exchange System Manager program to change the permissions on the Organisation to eliminate the "deny". The problem is that that program doesn't display the permissions by default and a registry hack is needed to make them accessable. The other option would have been to use a new account for the BES service.
Once I had done this, the problem disappear and I now have (probably temporarily) a couple of very happy users.
We run Balckberry Professional Software 4.1 which is a cut-down version of Blackberry Enterprise Software (BES) for small businesses and Exchange 2000. The problem only affected a small number of out users but was naturally frustrating. I searched for solutions via Google and tried my own troubleshooting. Evenually, I asked for support form Gen-i who sold us the software.
They pointed me in the direction of the "send as" and "receive as" permissions on the mailboxes in question. I could see that the BES account was denied those permissions on the affected accounts, but this setting was being inherited and I could not figure out from where. Further research showed that some built-in accounts are denied these permissions by default.
I needed to use the Exchange System Manager program to change the permissions on the Organisation to eliminate the "deny". The problem is that that program doesn't display the permissions by default and a registry hack is needed to make them accessable. The other option would have been to use a new account for the BES service.
Once I had done this, the problem disappear and I now have (probably temporarily) a couple of very happy users.
# posted by Gareth Bezett @ 6:03 PM 
