{"id":3999,"date":"2013-03-20T00:01:00","date_gmt":"2013-03-20T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2013\/03\/20\/use-powershell-to-find-non-default-user-properties-in-ad\/"},"modified":"2013-03-20T00:01:00","modified_gmt":"2013-03-20T00:01:00","slug":"use-powershell-to-find-non-default-user-properties-in-ad","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-powershell-to-find-non-default-user-properties-in-ad\/","title":{"rendered":"Use PowerShell to Find Non-Default User Properties in AD"},"content":{"rendered":"

Summary<\/strong>: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell and the Active Directory module provider to find non-default AD DS user properties.<\/p>\n

\"Hey, Hey, Scripting Guy! I need to find information about users such as office location, and phone number that is not returned by the Active Directory module provider by default. How do I do this?<\/p>\n

—DP<\/p>\n

\"Hey, Hello DP,<\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. Today is what is officially called the calm after the storm. Massive thunderstorms ripped through Charlotte last night, knocking out power and phones. Hey, that is OK; but dude, I lost my Internet connection in the process. Major bummer. With battery backups, a generator, and what-not, I can handle bad weather—as long as it does not knock out my Internet connection. I do not have a backup ISP provider. Hey, where I live, I was lucky to get the one I have. Oh, well.<\/p>\n

Guess what? I was just told that Windows PowerShell MVP and honorary Scripting Guy<\/a>, Sean Kearney<\/a>, will be presenting at Microsoft TechEd in New Orleans and in Madrid. Way to go Sean! By the way, there are two more days until the $300 discount expires<\/a>.<\/p>\n

Note<\/strong>   This is the third in a series of blog postings about using the Active Directory module provider. The first blog is an overview called Playing with the AD: Drive for Fun and Profit<\/a>. <\/em>The second blog is Find Active Directory User Information with the PowerShell Provider<\/a>, <\/em>in which I talk about how to use the Windows PowerShell provider to find user information in Active Directory.<\/p>\n

Quick review<\/span><\/h3>\n

To create the Charlotte: PSDrive (points to the Charlotte organizational unit or OU), I ran the following commands. (Obviously, you need to change the commands to point to an OU and a domain that exist on your system.)<\/p>\n

PS C:\\> ipmo activedirectory<\/p>\n

PS C:\\> New-PSDrive -Name charlotte -PSProvider activedirectory -Root “AD:\\ou=charlot<\/p>\n

te,dc=iammred,dc=net”<\/p>\n

 <\/p>\n

Name           Used (GB)     Free (GB) Provider      Root<\/p>\n

—-           ———     ——— ——–      —-<\/p>\n

charlotte                              ActiveDire… \/\/RootDSE\/ou=charlotte,dc=ia…<\/p>\n

 <\/p>\n

PS C:\\> sl charlotte:<\/p>\n

PS charlotte:\\><\/p>\n

Getting properties of the user<\/h2>\n

I might think that to easily see all of the information associated with the Ed Wilson user, I can pipe the output to the Format-List<\/strong> (fl<\/strong> is an alias) cmdlet as shown here.<\/p>\n

PS charlotte:\\> dir | ? name -match ‘ed wilson’ | fl *<\/p>\n

The command and the output associated with the command are shown in the image that follows.<\/p>\n

\"Image<\/a><\/p>\n

The problem with this approach is that only four properties of the user return. The four default properties are DistinguishedName<\/strong>, Name<\/strong>, ObjectClass<\/strong>, and ObjectGUID<\/strong>. However, a quick look in Active Directory Users and Computers reveals that there are many more attributes and values available. This is shown here.<\/p>\n

\"Image<\/a><\/p>\n

What about Get-ADUser?<\/h2>\n

Due to performance reasons, the Get-ADUser<\/strong> cmdlet does not return all properties of a user object. It returns the following properties:<\/p>\n

PS C:\\> Get-ADUser ‘cn=ed wilson,ou=charlotte,dc=iammred,dc=net’ | select -expand propertynames<\/p>\n

DistinguishedName<\/p>\n

Enabled<\/p>\n

GivenName<\/p>\n

Name<\/p>\n

ObjectClass<\/p>\n

ObjectGUID<\/p>\n

SamAccountName<\/p>\n

SID<\/p>\n

Surname<\/p>\n

UserPrincipalName<\/p>\n

Therefore, if I want to access additional attributes and their associated values, I need to specifically request the attributes I desire. Unfortunately, the attribute names bear little relationship to the names that appear in Active Directory Users and Computers. The best way to find the required attributes is to use ADSI Edit. In modern versions of ADSI Edit, there is a view that shows only attributes that contain values.
Consequently, it is fairly easy to match the actual name of the Active Directory attribute and the name that appears in Active Directory Users and Computers.<\/p>\n

Note <\/strong>  In my Windows PowerShell 3.0 Step by Step<\/a> book, I have a chapter that includes screenshots that map the Active Directory Users and Computers interface to the actual AD Attribute names.<\/p>\n

The ADSI Edit property sheet for the Ed Wilson user object is shown here.<\/p>\n

\"Image<\/a><\/p>\n

Use Get-ItemProperty to get other attributes<\/h2>\n

So what is the trick to obtaining additional attributes from the user object beyond the four default properties returned by Get-Item<\/strong>? One approach is to use the Get-ItemProperty<\/strong> cmdlet. This technique is shown here where I retrieve the city (lower case L) attribute for the user.<\/p>\n

PS charlotte:\\> Get-ItemProperty -Path ‘.\\CN=ed wilson’ -Name l<\/p>\n

l            : Charlotte<\/p>\n

PSPath       : Microsoft.ActiveDirectory.Management\\ActiveDirectory::\/\/RootDSE\/CN=ed<\/p>\n

                wilson,ou=Charlotte,DC=Iammred,DC=net<\/p>\n

PSParentPath : Microsoft.ActiveDirectory.Management\\ActiveDirectory::\/\/RootDSE\/ou=Ch<\/p>\n

               arlotte,DC=Iammred,DC=net<\/p>\n

PSChildName  : CN=ed wilson<\/p>\n

PSDrive      : charlotte<\/p>\n

PSProvider   : Microsoft.ActiveDirectory.Management\\ActiveDirectory<\/p>\n

Use Get-Item to get other attributes<\/span><\/h2>\n

I do not have to use the Get-ItemProperty<\/strong> cmdlet to retrieve other attributes from a user object. I can use the Get-Item<\/strong> cmdlet and type in an array of attributes in the Properties<\/strong> <\/em>parameter. This technique is shown here where I add in the city (l<\/strong>) and the phone number (telephoneNumber<\/strong>) to the command.<\/p>\n

PS charlotte:\\> get-item -Path “cn=ed wilson” -Properties l, telephonenumber<\/p>\n

 <\/p>\n

PSPath             : Microsoft.ActiveDirectory.Management\\ActiveDirectory::\/\/RootDSE<\/p>\n

                     \/cn=ed wilson,ou=charlotte,dc=iammred,dc=net<\/p>\n

PSParentPath       : Microsoft.ActiveDirectory.Management\\ActiveDirectory::\/\/RootDSE<\/p>\n

                     \/ou=charlotte,dc=iammred,dc=net<\/p>\n

PSChildName        : cn=ed wilson<\/p>\n

PSDrive            : charlotte<\/p>\n

PSProvider         : Microsoft.ActiveDirectory.Management\\ActiveDirectory<\/p>\n

PSIsContainer      : True<\/p>\n

distinguishedName  : cn=ed wilson,ou=charlotte,dc=iammred,dc=net<\/p>\n

l                  : Charlotte<\/p>\n

name               : ed wilson<\/p>\n

objectClass        : user<\/p>\n

objectGUID         : bb10b5a2-58d7-4f8a-ab10-2ee84fc7cb58<\/p>\n

telephoneNumber    : 555-555-1212<\/p>\n

PropertyNames      : {distinguishedName, l, name, objectClass…}<\/p>\n

AddedProperties    : {}<\/p>\n

RemovedProperties  : {}<\/p>\n

ModifiedProperties : {}<\/p>\n

PropertyCount      : 7<\/p>\n

Use Get-Item and retrieve all of the attributes<\/h2>\n

I can also use a wildcard character (*<\/strong>) to retrieve all of the attributes for my user object. The command is shown here.<\/p>\n

PS charlotte:\\> get-item -Path “cn=ed wilson” -Properties *<\/p>\n

The command and its associated output are shown in the following image.<\/p>\n

\"Image<\/a><\/p>\n

DP, that is all there is to using the Active Directory module provider to find information about users. Active Directory Week will continue tomorrow when I will talk about modifying user attributes.<\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/strong> <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell and the Active Directory module provider to find non-default AD DS user properties.  Hey, Scripting Guy! I need to find information about users such as office location, and phone number that is not returned by the Active Directory module provider by default. How do […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[7,414,3,4,303,45],"class_list":["post-3999","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-active-directory","tag-providers","tag-scripting-guy","tag-scripting-techniques","tag-searching","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell and the Active Directory module provider to find non-default AD DS user properties.  Hey, Scripting Guy! I need to find information about users such as office location, and phone number that is not returned by the Active Directory module provider by default. How do […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/3999","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=3999"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/3999\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=3999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=3999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=3999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}