About Me

My photo
TsooRad is a blog for John Weber. John is a Skype for Business MVP (2015-2018) - before that, a Lync Server MVP (2010-2014). My day job is titled "Technical Lead, MS UC" - I work with an awesome group of people at CDW, LLC. I’ve been at this gig in one fashion or another since 1988 - starting with desktops (remember Z-248’s?) and now I am in Portland, Oregon. I focus on collaboration and infrastructure. This means Exchange of all flavors, Skype, LCS/OCS/Lync, Windows, business process, and learning new stuff. I have a variety of interests - some of which may rear their ugly head in this forum. I have a variety of certifications dating back to Novell CNE and working up through the Microsoft MCP stack to MCITP multiple times. FWIW, I am on my third career - ex-USMC, retired US Army. I have a fancy MBA. One of these days, I intend to start teaching. The opinions expressed on this blog are mine and mine alone.


DL Management from Outlook

Exchange admins typically add/remove members from distribution lists.  However, as the organization grows in numbers and complexity, this situation needs addressing.

You would think that simply adding the appropriate user to the DL manager as shown would work, but that is not the case.


You will also need to do a little add-adpermission tweaking like this (the line may wrap):

add-adpermission -identity: “DL Group1” -User:domain\joe.tester -accessrights readproperty, writeproperty -properties ‘member’

you can add a group to this also:

add-adpermission -identity: “DL Group1” -User:”display name of permissions group” -accessrights readproperty, writeproperty -properties ‘member’

After this, the user should be able to open the DL from the outlook address book and modify the member list.  If you have a multiple domain scenario and this does not work, you have a global catalog issue.

My thanks to http://knicksmith.blogspot.com/2007/04/delegating-distribution-group.html for pointing me in the right direction to remember what I had forgotten.  Thanks Nick!

No comments:

SfB vNext will have SE

You read it here second… Here is the first:  http://www.teamsadmin.com/2018/02/08/no-standard-edition-front-end-role-skype-business-2019vnex...