{"id":3220,"date":"2013-07-18T00:01:00","date_gmt":"2013-07-18T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2013\/07\/18\/use-powershell-to-set-ad-ds-users-display-names\/"},"modified":"2013-07-18T00:01:00","modified_gmt":"2013-07-18T00:01:00","slug":"use-powershell-to-set-ad-ds-users-display-names","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-powershell-to-set-ad-ds-users-display-names\/","title":{"rendered":"Use PowerShell to Set AD DS Users’ Display Names"},"content":{"rendered":"

Summary<\/strong>: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell to set the users’ display names in Active Directory Domain Services.<\/span>\n\"Hey, Hey, Scripting Guy! I have a number of user names that were hastily created. I thought at first they were going to be temporary workers, but it seems that temporary is hanging around a lot longer than previously anticipated. This is actually causing issues with some of our Active Directory queries, because empty strings return when we were expecting data. I am wondering if there is an easy way to populate the display name— it would be fine to make it the same as the user name. I just need to get this done, and I do not want to spend a lot of time with it. Can you help me?\n—HH\n\"Hey, Hello HH,\nMicrosoft Scripting Guy, Ed Wilson, is here. This afternoon, it has not rained. In fact, it has not rained for two days. It must be some sort of record. Anyway, I am sipping a cup of Gun Powder Green Tea with a spoonful of lemon grass, a crushed cinnamon stick, a spoonful of rose hips, and a spoonful of Jasmine flowers. I let it steep for four minutes, and it is a lovely, light, and refreshing flavor. The tea is the perfect companion for doing a little bit of Active Directory Domain Services (AD DS) work.<\/p>\n

Query AD DS<\/h2>\n

The first thing I always do is query AD DS to see what sort of data I have. This is easy to do when using Windows PowerShell and the Active Directory module. Here is the command I use to query for UserName<\/strong> and DisplayName<\/strong>:<\/p>\n

Get-ADUser -SearchBase ‘ou=testou,dc=iammred,dc=net’ -Filter * -Properties displayname | select name, displayname\nThe output is shown here:<\/span><\/p>\n

PS C:> Get-ADUser -SearchBase ‘ou=testou,dc=iammred,dc=net’ -Filter * -Properties di<\/p>\n

splayname | select name, displayname<\/p>\n

 <\/p>\n

name                                       displayname<\/p>\n

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

newtestuser70<\/p>\n

newtestuser71<\/p>\n

newtestuser72<\/p>\n

newtestuser73<\/p>\n

<truncated><\/p>\n

Set DisplayName<\/h2>\n

To set the DisplayName<\/strong> attribute to be the same as the user name, I can pipe the results from the Get-ADUser<\/strong> cmdlet to the Set-ADUser<\/strong> cmdlet. The thing that is great about this is that the Set-ADUser<\/strong> cmdlet has a parameter for DisplayName<\/strong>, and this it makes it really easy. Here is the command I tried first:<\/p>\n

Get-ADUser -SearchBase ‘ou=testou,dc=iammred,dc=net’ -Filter * -Properties displayname | Set-ADUser -DisplayName $_.name\nBut this command does not work, because the value of $_<\/strong> is null here. Therefore, when I use the Up arrow to check my results, it comes up empty as shown here:<\/p>\n

PS C:> Get-ADUser -SearchBase ‘ou=testou,dc=iammred,dc=net’ -Filter * -Properties di<\/p>\n

splayname | select name, displayname<\/p>\n

 <\/p>\n

name                                       displayname<\/p>\n

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

newtestuser70<\/p>\n

newtestuser71<\/p>\n

newtestuser72<\/p>\n

<truncated>\nWell, I decide to try it without the $_ t<\/strong>o see if the cmdlet is smart enough to pick up the Name<\/strong> property directly without the assistance of $_<\/strong>. So here is the command I use:<\/p>\n

Get-ADUser -SearchBase ‘ou=testou,dc=iammred,dc=net’ -Filter * -Properties displayname | Set-ADUser -DisplayName name\nNow I check the results, and they are exactly what I was afraid of the first time—I have a bunch of names. See for yourself:<\/p>\n

PS C:> Get-ADUser -SearchBase ‘ou=testou,dc=iammred,dc=net’ -Filter * -Properties di<\/p>\n

splayname | select name, displayname<\/p>\n

 <\/p>\n

name                                       displayname<\/p>\n

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

newtestuser70                              name<\/p>\n

newtestuser71                              name<\/p>\n

newtestuser72                              name<\/p>\n

newtestuser73                              name<\/p>\n

<truncated>\nSo I try one more time. I assume that this command will work, but I was hoping that I could directly pipe to the Set-ADUser<\/strong> cmdlet without slowing things down with a Foreach-Object<\/strong> cmdlet (%<\/strong> is the alias). Here is the command:<\/p>\n

Get-ADUser -SearchBase ‘ou=testou,dc=iammred,dc=net’ -Filter * -Properties displayname | % {Set-ADUser -Identity $_ -DisplayName $_.name}\nAs I expected, the command worked properly. Here are the results:<\/p>\n

PS C:> Get-ADUser -SearchBase ‘ou=testou,dc=iammred,dc=net’ -Filter * -Properties di<\/p>\n

splayname | select name, displayname<\/p>\n

 <\/p>\n

name                                       displayname<\/p>\n

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

newtestuser70                              newtestuser70<\/p>\n

newtestuser71                              newtestuser71<\/p>\n

newtestuser72                              newtestuser72<\/p>\n

newtestuser73                              newtestuser73<\/p>\n

<truncated>\nSo all-in-all…not bad. It took me like less than three minutes to perform this task. It would have taken even less time if I went with what I suspected would have been the command in the first place. But hey, that is how one learns (or at least the way I learn—I just try it and see what happens).\nHH, that is all there is to using Windows PowerShell to set the display names of all your users in a particular organizational unit to be the same as the user names. Join me tomorrow when I will talk about more cool Windows PowerShell stuff.\nI 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.\nEd Wilson, Microsoft Scripting Guy<\/strong> <\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell to set the users’ display names in Active Directory Domain Services.  Hey, Scripting Guy! I have a number of user names that were hastily created. I thought at first they were going to be temporary workers, but it seems that temporary is hanging […]<\/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,3,198,45],"class_list":["post-3220","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-active-directory","tag-scripting-guy","tag-users","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell to set the users’ display names in Active Directory Domain Services.  Hey, Scripting Guy! I have a number of user names that were hastily created. I thought at first they were going to be temporary workers, but it seems that temporary is hanging […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/3220","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=3220"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/3220\/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=3220"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=3220"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=3220"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}