Skip to main content

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.

1

2

3

4

5

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

Popular posts from this blog

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.

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 .

Set up your Environment to utilize Invoke-GPUpdate

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