Skip to main content

Active Directory Module Filter/Hash compatibility issues Between V2 and V3

While assisting another IT Professional with a PowerShell issue, we came across a syntax difference between PowerShell V2 and V3 with regards to using a hash with the Get-ADUser cmdlet.  I was utilizing PowerShell V3 while the other individual was on V2.  Here is the code that worked on V3:
$ADHash = @{Filter = '(Surname -eq $Last) -and (GivenName -eq $First)';
SearchBase = $($OU.DistinguishedName)}           
Get-ADUser @ADHash
 
In this example, a hash is being created for the Get-ADuser cmdlet.  Both a value for the Filter and another for the SearchBase parameters were being created.  The problem came down to the filter.  In PowerShell V3, a complex filter is allowed.  That is, a filter that is using a logical operator such as –as or –or.  Here is the same code, but codded for V2.
Get-ADUser -filter * -SearchBase "$($OU.DistinguishedName)" |
Where-Object {($_.GivenName -eq $First) -and ($_.Surname -eq $Last)}
 
Utilizing any filtering capability that a cmdlet provides is much more efficient than piping objects to Where-Object.  In this case though, the Get-ADUser cmdlet provided with the ActiveDirectory Module on Windows Server 2008 R2 did not have this functionality.  Below is the error that the other IT Pro was receiving when he attempted to use the V3 code on a V2 domain controller.
Ge-AtDUser : The search filter cannot be recognized
At C:\BadgeUpdate1.ps1:18 char:11
+ Get-ADUser <<<<  @ADHash |
    + CategoryInfo          : NotSpecified: (:) [Get-ADUser], ADException
    + FullyQualifiedErrorId : The search filter cannot be recognized,Microsoft.ActiveDirectory.Management.Commands.Get
   ADUser

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.