Use PowerShell to discover all computer objects in AD

I’m sitting in my classroom while my class is doing a lab and answering some questions from PowerShell.com. This scripter needs to discover all the computer objects in Active Directory with an empty description and provide a setting for it.

Import-Module ActiveDirectory # For PowerShell V2 Compatibility

$Desc = "New Description String"

Get-ADComputer -Filter * -Properties Description |

Where-Object {$_.Description -eq $Null} |

Set-ADComputer -Description $Desc

Line 1 imports the Active Directory module into this session. You can omit this line if you are running PowerShell V3 or V4 and have the PowerShell ActiveDirectory module installed locally.

Line 2 is used to provide the new description property value.

Line 3 gets all the computer objects from Active Directory. I was not able to get a filter for a description that is NULL. Hence the reason for line 4 which uses Where-Object to filter on the NULL Description property. Normally I would aviod using Where-Object whenever possible.

Line 5 sets the new property value.

Asking my class, we have an average of 500 clients per student. We timed this task to take approximately 8 seconds per client to perform this operation manually using Active Directory Users and Computers. Non-stop and without errors, this operation would take just over an hour to complete. In our test environment, this process took 12 seconds to complete the change on 500 clients. Not bad for a simply script.

Comments

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.

Jason Yoder, MCT

Search This Blog