I'm posting this here, and not mentioning the dreaded CDO.DLL file. I've verified and re-verified the CDO file, and every other file I could find with the letters "CDO" in it as you can see here.... I've listed ALL the CDO File(s), their Location and the Server upon which they reside. MAIL01 and MAIL02 are, as you expect the Exchange Servers and the MGMT1 is the BES Server itself..

MAIL01 cdo.dll C:\Program Files\Exchsrvr\bin 6.5.7651.61 718,848 bytes
MGMT1 cdo.dll C:\Program Files\Exchsrvr\bin 6.5.7651.61 718,848 bytes
MAIL02 cdo.dll C:\Program Files\Exchsrvr\bin 6.5.7651.61 718,848 bytes
MGMT1 cdo.dll C:\WINDOWS\system32 6.5.7651.61 718,848 bytes

MAIL01 cdoex.dll C:\Program Files\Common Files\Microsoft Shared\CDO 6.5.7652.24 3,945,984 bytes
MAIL02 cdoex.dll C:\Program Files\Common Files\Microsoft Shared\CDO 6.5.7652.24 3,945,984 bytes

MAIL01 cdoexm.dll C:\Program Files\Exchsrvr\bin 6.5.7638.1 2,865,664 bytes
MAIL02 cdoexm.dll C:\Program Files\Exchsrvr\bin 6.5.7638.1 2,865,664 bytes
MGMT1 cdoexm.dll C:\Program Files\Exchsrvr\bin 6.5.7638.1 2,865,664 bytes

MGMT1 cdosys.dll C:\WINDOWS\system32 6.5.6757.0 2,098,688 bytes
MAIL01 cdosys.dll C:\WINDOWS\system32 6.5.6757.0 2,098,688 bytes
MAIL02 cdosys.dll C:\WINDOWS\system32 6.5.6757.0 2,098,688 bytes

MAIL01 cdowf.dll C:\Program Files\Exchsrvr\bin 6.5.6944.0 591,360 bytes
MAIL02 cdowf.dll C:\Program Files\Exchsrvr\bin 6.5.6944.0 591,360 bytes

MAIL01 cdowfevt.dll C:\Program Files\Exchsrvr\bin 6.5.6944.0 122,368 bytes
MAIL02 cdowfevt.dll C:\Program Files\Exchsrvr\bin 6.5.6944.0 122,368 bytes

MAIL02 excdo.dll C:\Program Files\Exchsrvr\bin 6.5.7652.24 3,631,616 bytes
MAIL01 excdo.dll C:\Program Files\Exchsrvr\bin 6.5.7652.24 3,631,616 bytes

MAIL01 Microsoft.CDO.dll C:\Program Files\Symantec\SMSMSE\5.0\Server\DExLService\bin\R eporting 1.0.0.0 61,440 bytes
MAIL02 Microsoft.CDO.dll C:\Program Files\Symantec\SMSMSE\5.0\Server\DExLService\bin\R eporting 1.0.0.0 61,440 bytes
MAIL02 Microsoft.CDO.dll C:\Program Files\Symantec\SMSMSE\5.0\UI 1.0.0.0 61,440 bytes
MAIL01 Microsoft.CDO.dll C:\Program Files\Symantec\SMSMSE\5.0\UI 1.0.0.0 61,440 bytes
MGMT1 Microsoft.CDO.dll C:\Program Files\Symantec\SMSMSE\5.0\UI 1.0.0.0 61,440 bytes

So Even after verifying and re-verifying, Here's what's happening.

I have Two Separate OU's in the AD, (Call them Apples and Oranges for the sake of argument)

The User in the Apples OU Can Use their BB's quite nicely, Sending Calendar events from their BB's to Exchange without issue, However the Users in the Oranges OU cannot send Calendar event's FROM their BB's to Outlook, and that's the ONLY function they cannot do, everything else works perfectly.

Add to this, Moving a User from the Apples OU to the Oranges OU and Hey presto! Guess what no longer works, Move him back and the issue goes away. and the opposite holds true as well, Move a User from the Oranges OU to Apples and everything works nicely, Move him back to Oranges where he belongs and like a bad smell the Calendar breaks once again.

Any thoughts? I'm at a total loss here....

Thanks in advance...

Scratch

Well, this isn't a BES issue - looks like the BES is working great. It sounds like an AD permissions issue. Compare the permissions between the two different OU's. also look at any policies you may have set at the OU level.

That's what I figured,

I just thought that perhaps due to there being two separate Exchange Servers and the BES Server on top it might have some unforeseen quirks someone might have come across before...

Does anyone know of any issues surrounding the move of the BESAdmin Mailbox from One information store to another?

Right now the BESAdmin Mailbox is in the same store as the "Apples" (as in they have full funcality, I was wondering what would happen if I moved the BESAdmin account (Mailbox) from teh Apples to the Oranges, or even back to the Default Mail Store...


Thanks...

Scratch

Are the people in the Apple OU on one server and the people in the Orange OU on another? The BESadmin account needs permissions on all servers/SGs that have BES users. I don't see how moving that account from one storage group to another would make any difference. What is relevant is if it has the proper permissions.