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

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.

How to run GPResult on a remote client with PowerShell

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.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the