-->

Friday, October 28, 2016

Exchange 2016 Distribution Group Owners Can't Edit Members In Resource Forest

In my Exchange 2016 Resource Forest, for some reason Distribution Group Owners could not add or remove members of those groups from within Outlook.

They would get the following error:

"Changes to the public group membership cannot be saved. You do not have sufficient permissions to perform this operation on this object."

Outlook Ditstro Change Error

Real descriptive error

We tried several different things such as:

Enable AD Full Control permissions for the owner - didn't work
Enable AD "Manager can update membership list" - didn't work
Enable AD "Write Members" - didn't work

Finally what did work (and is totally counterintuitive as I'll show later) was enabling the "Distribution group memberships" setting in the Default Role Assignment Policy.

In the EAC, navigate to permissions > user roles

Double-click the Default Role Assignment Policy

**Note** If you have created other role assignment policies, you'd choose that one

In the Policy mark the checkbox for "Distribution group memberships"

Default Role Assignment Policy

Give it some time for replication and check that owners can edit their distro group memberships from Outlook.

**Note** They might have to close and reopen Outlook for changes to take effect.

The counterintuitive part: even though we enabled a setting that says "the role enables users to view and modify their membership in groups" it actually does not allow them to do so...bug? I dunno, but Exchange 2016 is filled with 'em.

5 comments:

  1. Is your Distribution group set to Universal? We are using O365 and are having the same issues.
    I'll probably have to talk to Microsoft on this one, though at the same time another website mentioned that Distro groups have to be set to Universal, could you verify that?

    ReplyDelete
    Replies
    1. Hey Kyle, yeah I only use Universal Groups. The solution above is from a MS support call...it was the only thing they could come up with :)

      Delete
  2. Searched high and low, and you just figure it out. Thank you!!!

    ReplyDelete
  3. This comment has been removed by the author.

    ReplyDelete
  4. I´m in O365 as well, and this also solved the issue for me.

    PS this is the only article I have found with this solution - so THANKS:-)

    ReplyDelete