Exchange 2010: Send As Permission for group mailbox...

Our helpdesk has a shared mailbox used for users to submit issues.  Up until a week ago, all of the helpdesk techs could send-as the shared mailbox.  Now when they attempt to send as the shared mailbox via Outlook they get the error "You do not have the permission to send the message on behalf of the specified user.".  When I attempt to manage send as permission via EMC (using an account with Domain Admin privileges) I've found that the list of users who can send as is blank.  When I attempt to add send as permissions via EMC I get the error below:


Active Directory operation failed on DC1.xxxxxx.local. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521E1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

The user has insufficient access rights.
Click here for help...

Exchange Management Shell command attempted:
Add-ADPermission -Identity 'CN=account,DC=xxxxxx,DC=local' -User 'domain\username' -ExtendedRights 'Send-as'

Elapsed Time: 00:00:00

Anyone have any advice to fix this issue?

Thanks in advance for your help.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nick RhodeIT DirectorCommented:
Seems like the user lost their inherited permissions.  Open up active directory > Select the target user account > properties > Security Tab > advanced button.  If you cannot see the Security tab you have to go to view > advanced features

On the Permissions tab put a check mark in Allow inheritable permissions from the parent and click ok

What was recently done on the server or was there an upgrade on exchange etc?  I typically see this issue occurring after a migration of some sort like Exchange 2007 - 2010 etc.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
reuniontitleAuthor Commented:
Nothing has changed in our Exchange environment lately, but your suggestion fixed the issue!  Much thanks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.