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

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

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 .

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog