Skip to main content

Great example of Using PowerShell to modify AD properties

Today in class I took a question from the Active Directory Forums on PowerShell.com where I am a moderator.  The user had an Excel spreadsheet containing the first and last names of his users, and a field for their pager numbers.  He needed a way to test to see if the pager value in the spreadsheet matched the one in active directory.  If not, he needed the number changed.  Here is what I sent him:

Import-Module ActiveDirectory

 

ForEach ($User in (Import-CSV -Path C:\PS\Users.CSV))

{

    $Last = $User.Last

    $First = $User.first

    Get-ADUser -Filter '(Surname -eq $Last) -and (GivenName -eq $First)' |

    ForEach {If ($User.OtherPager -ne $_.Pager)

    {

        $_ |Set-ADObject -Replace @{OtherPager="$($User.OtherPager)"}

    }

    }

}

 

Assuming that he was using PowerShell V2, I had him import the PowerShell module for Active Directory.

 

I then had him load the excel spreadsheet (which was saved as a CSV file) and then cycle through each record one at a time.

 

Using the Get-ADUser cmdlet, I utilized its filtering capability to find a user in AD that match the first and last name of the record being searched.

 

If a match is found, I then compared the OtherPager property in AD to the one in the CSV.  If the matched, then nothing was done.  If they did not, the value from the CSV was applied to the object in AD.

 

The user said that he was supporting 1000 users.  My class estimated that without breaks, interruptions or mistakes, this short script would save this administrator 3.3 hours every time it was used. Not back for a little script.

Comments

Chris Childerhose said…
Nice to see my example being used as a real world example.

Chris Childerhose
McMillan LLP
You question came at a good time. I was glad that we could help.

Jason

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