When it comes to the dreaded Send As issue check the following:
1. Send As is set in AD at the root or OU level
2. Ensure that users have inherited the permission, kind of pointless if they don't have it
3. If not, make sure that no users, or the BESAdmin, are in any protected groups
- Administrators
- Account Operators
- Server Operators
- Print Operators
- Backup Operators
- Domain Admins
- Schema Admins
- Enterprise Admins
- Cert Publishers
4. If so, remove the user or besadmin, enable inheritance and make sure that Send As is set for the user
5. Stop the BB Router service for 2 hours, unless you set the reg on Exchange for it to clear the mailbox every 20 minutes. Or you can restart the information store as well.
6. Start the BB Router service and test
A good test as well if the permission is set for a user but can't send is this:
1. Log into a Windows XP machine as BESAdmin
2. Create an Outlook/MAPI profile for the affected user, without Cached Exchange Mode enabled
3. Open Outlook and you should see the users mailbox
4. Try sending an email to anyone
If the test fails then the permission has not yet written to the mailbox and you should try clearing the mailbox cache again or contact Microsoft about using DSACLS to forcefully write the permission to the mailbox.
|