I have tried many kb articles recommendations and still the send as permissions disappear. This is required for Blackberry usage. We use Exchange 2003 R2 . Our store.exe is version 6.5.7654.12 We have set the besadmin send as permissions at the top of the domain. We have set the adminsdholder send as permissions as well. We have also set the inherit permissions as well Please help. David

You say these permissions are disappearing. Are they disappearing, or are they not working? If the latter, what groups is the BESAdmin account a member of? If it is a Domain Admin or an Exchange Admin, as I remember, the system also gives a Deny to the account at the organization level. If your grants are placed at a higher level than the denies, you will not have access to the mailboxes. If it's the former, I'm not 100% sure why it may be happening, but I remember a KB article that said that Exchange would remove permissions to accounts that are members of the Domain Admins group or some of the Exchange administrative groups, but I can't find that article.

Your Organization (Exhange) - Properties - Delegate control - Next, give your user the right to Exchange View Only Administrator.

Yes I have read the kb about protected groups (administrators , print operators etc.,) having this problem of not being able to put in the Send As permissions. I have followed the recommendations to put in the adminsdholder send as permissions as well. I have also activated the inherit permissions too . It just doesn't stick . Anyone knows how to make the Send As permissions stick ?. Without this , the blackberry just doesn't work . Thanks David

Is this account in one of those groups? Try removing it and see if you still have the problem.

I do not see users as being members of protected groups. However , I did remove them to test and the send as permission sticks. This does not settle the issue . We cannot remove users from groups because of BB send as permissions problem. These users still need the groups because of other needs and rights . There must be some way that we can block off this such that protected group or not , we can still make the send as permissions stick .