Skip to main content

How to list all members of a Distribution group and their emails with PowerShell

This question came from the need of a user who needed to extract the following information:

Distribution Group Name | Group Email | Group Member | Member’s Email

 

Function Get-DistributionEmail

{

 

    # Get a list of all the distribution groups in the domain.

    $Groups = Get-ADGroup -Filter 'GroupCategory -eq "Distribution"' -Properties Mail

 

    # Create a dynamic array to hold the objects for the output.

    $Obj = @()

   

    # Loop through each group.

    ForEach ($Group in $Groups)

    {

        # Enumerate all the members of the group.

        $Members = Get-ADGroupMember -Identity $Group.name

       

        # Collect the data for the output.

        ForEach ($Member in $Members)

        {

            $GroupObj = New-Object PSObject

            $GroupObj | Add-Member `

             -MemberType NoteProperty `

             -Name "Group" `

             -Value $Group.Name

           

            $GroupObj | Add-Member `

             -MemberType NoteProperty `

             -Name "GroupEmail" `

             -Value $Group.Mail

 

            $GroupObj | Add-Member `

             -MemberType NoteProperty `

             -Name "User" `

             -Value $Member.Name

           

            $User = get-ADuser -filter 'Name -eq $Member.name' -Properties Mail

 

            $GroupObj | Add-Member `

             -MemberType NoteProperty `

             -Name "UserEmail" `

             -Value $User.Mail

 

             # Transfer the object to the dynamic array.

             $Obj += $GroupObj

        }

    }

    # Wrtie the contents of the array to the PowerShell pipeline.

    Write-Output $Obj | FT -AutoSize

<#

.SYNOPSIS

Gather all user accounts and email addresses of Distribution Group members.

 

.DESCRIPTION

Gather all user accounts and email addresses of Distribution Group members.

 

.EXAMPLE

Get-DistributionEmail

 

Group  GroupEmail      User  UserEmail    

-----  ----------      ----  ---------    

Group1 Group1@Indy.com User1 User1@Indy.com

Group1 Group1@Indy.com User2 User2@Indy.com

Group2 Group2@indy.com User3 User3@indy.com

Group2 Group2@indy.com User4 User4@indy.com

 

.NOTES

Requires the Active Directory module to be available.

#>

}

Comments

Biller said…
Cool ! I like it.

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.