Skip to main content

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

By
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
Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more