Skip to main content

Removing duplicate objects from an set of objects

The question that I took this evening involved a user who has some functional PowerShell code.  The needed a way to filter out any duplicate objects.  They were looking at using several loops.  In my college days, that would have been the answer.  As my favorite professor, Dan Matthews, put it, “Never Reinvent the Wheel”

PowerShell has built in functionality to remove duplicate items by using the Sort-Object cmdlet.  You need to use the –Property parameter to tell PowerShell which proper of the object you are looking for duplicates on and also you need to use the –Unique parameter to tell PowerShell to only leave unique objects (remove duplicates).

Below is some sample code to generate a set of 11 objects.  Two of those objects will have a duplicate value in Prop1.

# Create a dynamic array to hold the test objects.

$Array = @()

 

# Create 10 objects in the dynamic array.

For ($X = 0;$X -lt 10;$X++)

{

    $Obj = New-Object PSObject

    $Obj | Add-Member -MemberType NoteProperty -Name "Prop1" -Value $X

    $Obj | Add-Member -MemberType NoteProperty -Name "Prop2" -Value $True

    $Obj | Add-Member -MemberType NoteProperty -Name "Prop3" -Value $False

 

    # Add the object to the array

    $Array += $Obj

}

 

# Add a duplicate to the array.  The duplication will be on the property

# Prop1 with a value of 3

$Obj = New-Object PSObject

$Obj | Add-Member -MemberType NoteProperty -Name "Prop1" -Value 3

$Obj | Add-Member -MemberType NoteProperty -Name "Prop2" -Value $True

$Obj | Add-Member -MemberType NoteProperty -Name "Prop3" -Value $False

 

# Add the object to the array

$Array += $Obj

 

# View the contents of the array.  Notice the duplicate value in Prop 1

$Array | FT –autosize

 

# Divider between the two sets of data.

Write-host "-----------------------------------------------------------"

 

# Use the -Unique parameter of the Sort-Object cmdlet.

# Note the duplicate object is gone.

$Array | Sort-Object -Property Prop1 -Unique | FT -autosize

 

This output will display two sets of data.  One set will show all 11 objects (including the duplicate).  The second set was filtered using Select-Object in the last line of the code.

Prop1 Prop2 Prop3

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

    0  True False

    1  True False

    2  True False

    3  True False

    4  True False

    5  True False

    6  True False

    7  True False

    8  True False

    9  True False

    3  True False

 

 

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

 

Prop1 Prop2 Prop3

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

    0  True False

    1  True False

    2  True False

    3  True False

    4  True False

    5  True False

    6  True False

    7  True False

    8  True False

    9  True False

Notice in the second set that was filtered with Sort-Object, the duplicate value of 3 in Prop1 has been removed.

Comments

JoeM said…
Thanks! Was helpful.

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 .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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...