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

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

Set up your Environment to utilize Invoke-GPUpdate

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

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more