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

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

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

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

Sticky Key problem between Windows Server 2012 and LogMeIn

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