Sign in
 
HomeLibraryLearnDownloadsRepositoryCommunityForumsBlog
Script Center >
> 
> 
Get-Aduser cmdlet does not give you all the attributes like the way the quest cmdlet get-qaduser does...

Answered Get-Aduser cmdlet does not give you all the attributes like the way the quest cmdlet get-qaduser does...

  • Thursday, March 07, 2013 10:52 PM
     
     
    Sign In to Vote
    0
    Is there a way to get all the attributes ( ALL ) using get-aduser
     

All Replies

  • Thursday, March 07, 2013 10:56 PM
    Moderator
     
     Answered Has Code
    Sign In to Vote
    1

    Do you mean like

    get-aduser username -properties *

    ?

    Bill

     
  • Friday, March 08, 2013 1:56 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    In addition, you can specify any attribute by LDAPDisplayName in the -Properties parameter. The help for Get-ADUser only documents the aliases available. I explain all properties available in the AD module cmdlets in this Wiki article:

    http://social.technet.microsoft.com/wiki/contents/articles/12031.active-directory-powershell-ad-module-properties.aspx

    which has a link to another Wiki article for more detail on the Get-ADUser cmdlet (the default and extended properties available).

    Richard Mueller - MVP Directory Services

     
  • Friday, March 08, 2013 8:36 AM
     
     
    Sign In to Vote
    0

    Yes exactly Bill.. Infact there is an interesting article which shows the differences between MS Get-aduser cmdlet and Quest Get-Qaduser cmdlet

    http://msmvps.com/blogs/richardsiddaway/archive/2012/03/25/attributes-returned-by-the-cmdlets.aspx

    Is there a way we can get MS cmdlet to show all the attributes of a user (extensionattributes1..etc..and other attributes... ) without having to feed it via properties..

     
  • Friday, March 08, 2013 8:38 AM
     
     
    Sign In to Vote
    0
    I did read through your articles Richard.. :-) Infact the first place I used to go to a while ago was the hilltop lab :-)
     
  • Friday, March 08, 2013 3:18 PM
    Moderator
     
     
    Sign In to Vote
    0
    Is there a way we can get MS cmdlet to show all the attributes of a user (extensionattributes1..etc..and other attributes... ) without having to feed it via properties..

    I'm not sure I understand the question. Why does it matter? What's provoking the question?

    Bill

     
  • Sunday, March 10, 2013 6:55 PM
     
     
    Sign In to Vote
    0

    So I'm part of a consolidation project and we are dealing with 9 different forest. Before consolidation we are trying to compare the attributes used in different forests. So when I run

    Get-aduser -filter * -searchscope subtree -Searchbase "dc=domainname,dc=com" -properties * | export-csv C:\users.csv

    My out  file does not show extensionattributes1.. 15 and a few other attributes that may have values... When I do the same Quest cmdlets , Get-Qaduser the output has each and every attribute ( populated or empty ) against the user.

    Question: Is there a way I can get the same output with MS cmdlets?

     
  • Monday, March 11, 2013 3:13 PM
    Moderator
     
     
    Sign In to Vote
    0

    The different cmdlets are going to behave differently as they were developed independently.

    If you need the same output, use the same cmdlet in both cases.

    Bill

     
  • Tuesday, March 12, 2013 6:51 AM
     
     
    Sign In to Vote
    0

    Customer does not want to install Quest cmdlets... I tried this in my test lab with quest cmdlets.. unfortunately I had to get this working by specifying each attribute that I needed.

    Thanks

     
  • Tuesday, March 12, 2013 2:11 PM
    Moderator
     
     
    Sign In to Vote
    0

    In that case I would use the AD cmdlets in your test lab to replicate what you're doing on the customer side.

    Bill