Link to home
Start Free TrialLog in
Avatar of Tymetwister
TymetwisterFlag for United States of America

asked on

User can't manage Distribution List even tho he's Owner

So I made someone the Owner of a particular distribution list that I want him to manage.  By going into the Properties of it from his own Outlook client, it allows you to Add and Remove members.  However, even though he is owner, when he tries is this way, we get an error saying "Changes to the distribution list membership cannot be saved.  You do not have sufficient permission to perform this operation on this object."

I made him the Owner!  What more would I have to do to give him permission to do this?

Thanks.
ASKER CERTIFIED SOLUTION
Avatar of Rajitha Chimmani
Rajitha Chimmani
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If the option is already selected please provide the Exchange and Outlook version.
Refer to this article to allow users to manage distribution groups.  Might have just missed a step on setting it up

http://sysadmin-talk.org/2010/06/omg-allowing-end-users-to-manage-distribution-group-membership-in-exchange-2010-2/
Agreed, the answer is in the link above, you need to create the "New-ManagementRoleAssignment" using powershell or using OWA/EMS. Both methods are provided in the link above, provided by NRhode.

Joel
Avatar of Tymetwister

ASKER

The link above is for Exchange 2010.  I should have mentioned that the end-user client is 2007 and we are using Exchange Server 07.  The link above says the process is completely different in 2010 and that's what they are describing it for...

The "allow manager to update" was NOT checked and I just now checked it.  Didn't work right away but I'm going to have him wait a little bit for replication, maybe log out and back in..
Yes, it should work once the changes are replicated and the user may try restart to Outlook.
Sorry for the late post but usually a simple restart of the information store service to get it going right away.  Otherwise setting permissions can take a little bit and not always work immediately