Skip to main content

How to Extract the Username of the ManagedBy property of an Organizational Unit

By

This morning in my PowerShell class, we looked at creating calculated properties.  Fortunately for us, I found one of our fellow IT professionals on PowerShell.com that needed a little bit of help that involved calculated properties.  This individual was attempting to enumerate all of the Organizational Units in their Active Directory domain and extract the username in the MangedBy property.  The thing is, the ManagedBy property gives you the distinguished name of the user, not the user name.

Get-ADOrganizationalUnit -filter * |

Select-Object -Property Name, ManagedBy 

Groups                                                                                         

Printers                                                                                       

Printers                                         CN=James,CN=Users,DC=Adatum,DC=com            

Printers                                                                          

By using calculated properties and controlling the order of operation, we can perform an extra step and extract the username using the distinguished name.

1

2

3

4

Get-ADOrganizationalUnit -filter * |

Select-Object -Property Name,

@{N="ManagedBy";E={Get-ADUser -Identity $_.ManagedBy |

Select -expandProperty SamAccountName}}

Line 1 gathers all Organizational Unit objects in Active Directory

Line 2 selects out the Name property and leaves a comma so we can continue on the next line.

Line 3 starts our calculated property.  We give new our property the name ManagedBy. The value, or expression, of this property is actual the result of the PowerShell command Get-ADUser and the result of line 4.  The expression in line 3 gets the User object for whom ever is in the Organizational Unit’s ManagedBy property.  It then sends that object to Select-Object to extract out the actual SamAccountName.  The SamAccountName is the actual value of our calculated property.

Comments

Post a Comment

Popular posts from this blog

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?

By
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. ...
Post a Comment
Read more

Sticky Key problem between Windows Server 2012 and LogMeIn

By
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 .
6 comments
Read more

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more