I have been moving towards DDL’s but get some push back as they cannot see who is in them.
Also, our OU’s are not as granular as the DL’s that they want. But I keep trying to move there.. ☺ Thanks, Alice From: [email protected] [mailto:[email protected]] On Behalf Of ccollins9 Sent: Monday, August 03, 2015 1:37 PM To: exchange Subject: Re: [Exchange] PS Script to see if specific DL has had members added recently to offset admins adding wrong people Speaking for the future process that the helpdesk uses, you should look into using Dynamic Distribution groups wherever possible. This would limit the requirement for anyone (even you) to have to manually place a user in a DG in the first place. You could base it on OU for example. So the new process going forward would be to add them to all the groups they need, but no distribution groups. Then let Exchange handle which distribution groups they are a part of based on their OU membership, for example. Just food for thought. http://johanveldhuis.nl/tutorials/exchange/dynamic-distribution-groups/ On Fri, Jul 31, 2015 at 7:53 PM, Alice Goodman <[email protected]<mailto:[email protected]>> wrote: Thanks all for the good suggestions. Between maybe creating a separate OU and doing some PowerShell, I think I can get this handled.. :) Appreciate all of the ideas. Alice -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Kurt Buff Sent: Friday, July 31, 2015 9:42 AM To: [email protected]<mailto:[email protected]> Subject: Re: [Exchange] PS Script to see if specific DL has had members added recently to offset admins adding wrong people Something like this might work for you: Send an email with Powershell http://powershell.com/cs/media/p/251.aspx Using the data gathered here: PS C:\BatchFiles> $Names = Get-ADGroupMember exadmins | select name PS C:\BatchFiles> $LastChanged = Get-ADGroup CriticalGroupName -properties WhenChanged | select (@{Name="LastChanged"; Expression={$_.WhenChanged.ToString("u")}}) $Names only contains the current members of the group(s) you select, but the second line will tell you when the group was last updated in some way. Kurt On Thu, Jul 30, 2015 at 6:28 PM, Alice Goodman <[email protected]<mailto:[email protected]>> wrote: > New hires are inadvertently getting added to distribution lists when > profiles are copied. Is there a way to stop this from happening on more > strictly controlled lists? (I know, stop hitting head against the wall…) > > This is becoming a BIG problem here. Does anyone know of some > PowerShell that we can run nightly or weekly against maybe 20 key DL’s > to see if anyone has been added to them in the past xx time? Or some other > solution? > > The issue is that the Admins in Help Desk create new users by copying > other users that “resemble’ the new hire. I know that using Templates > would be the best way, but that has never been implemented here. I > realize that I am looking for a solution to a bad practice. > > I looked at Owner Approval, but an Admin updating a DL does not cause > that to be triggered. Only end-users, using OWA. > > Thanks, > Alice > >
