sorry I forgot to add that this is only effecting domain admin users. They do not have the besadmin account with send as enabled in the permissions. Regular accounts seem ok. What i tried earlier was adding the besadmin, allowing send as, but the permission disappears. The KB article describes this as 'normal'. Its almost certainly a group membership issue.
I will follow your steps as soon as I get a chance, but probably not until next week sometime, since the only 'admin' user its affecting at the moment is myself. It is a new install and not rolled out yet for this reason, but now that i've gotten a regular user up and running, i can go ahead and order more licenses and move forward. Thanks for all the help, i'll update as i progress!
Originally Posted by gibson_hg
Just to be clear, you have verified that the user objects have the BESAdmin with Send As. You also didn't specify if this affects everyone or just certain users.
I'm not sure about the hot fix, I've never used and I haven't seen it work to be honest. I usually recommend using either Method 2 or 3 in the article to fix the issue if it has to do with group membership.
Here is the process I would follow:
1. Ensure that Send As is set at the domain level
2. Check individual users to see that they did indeed inherit the permission
3a. If they didn't check that inheritance is enabled and check group membership
b. If inheritance is not enabled then enable it and stop the BlackBerry Router service for 2 hours or restart the Inforamtion Store service(way faster) and the start the BlackBerry Router service
c. If group membership is the issue either remove the users from the affected groups if not needed or apply one of the work arounds in 817433 and then do the stop BB Router service process
4a. If it's not inheritance or group membership, try the Outlook test
b. Log into a Windows XP machine as the BESAdmin
c. Open Outlook and point the profile to one of affected users mailboxes, you should only see that users mailbox, and don't use Cached Exchange Mode
d. Compose and new email and send
e. If the email fails to send or doesn't get received then it's permissions. You may have to use DSACLS to force the permissions to write to the mailbox
Even though the permission is set it doesn't actually write to the mailbox and DSACLS can do that. There are articles from Microsoft as well to help with using that utility. I would give you instructions but I would do more harm then good.
You can thank Microsoft for this lovely issue. It targets the BESAdmin account perfectly.
Follow the above to narrow down the issue. Let us know what you find.