Limited properties with user objects using Get-QADUser Kari 11.07.2007 13:56:02 Hi! I would need to create list of my users and I was planning to do it with Get-QADUser cmdlet. Unfortunately it seems that these objects have limited amount of properties so I can't select Division as one of the properties for my table (get-qaduser | select-object Name,LogonName,Company,division). Is there any way to query for the division information on each object in the pipeline? I know that Get-QADUser knows the object attribute division because I did a list on certain users just by querying the following: get-qaduser -seachroot 'myad.local' -objectattributes [ at ]{company='Example';division='Example'} Thru WMI or something? ... and if you're willing to help please be specific because I quite new with PS.

RE: Limited properties with user objects using Get-QADUser RichS 11.07.2007 15:38:05 You should be able to do what you want if you use the -IncludeAllProperties parameter I think -- Richard Siddaway Please note that all scripts are supplied "as is" and with no warranty Blog: http://richardsiddaway.spaces.live.com/ PowerShell User Group: http://www.get-psuguk.org.uk "Kari" wrote: [Quoted Text] > Hi! > > I would need to create list of my users and I was planning to do it with > Get-QADUser cmdlet. Unfortunately it seems that these objects have limited > amount of properties so I can't select Division as one of the properties for > my table (get-qaduser | select-object Name,LogonName,Company,division). > > Is there any way to query for the division information on each object in the > pipeline? > > I know that Get-QADUser knows the object attribute division because I did a > list on certain users just by querying the following: > get-qaduser -seachroot 'myad.local' -objectattributes > [ at ]{company='Example';division='Example'} > > Thru WMI or something? ... and if you're willing to help please be specific > because I quite new with PS.

RE: Limited properties with user objects using Get-QADUser Kari 12.07.2007 06:32:02 IcludeAllProperties is a parameter for Get-QADUser? It only returns an error with my console. PS H:\> Get-QADUser -SearchRoot myad.local/OU' -IncludeAllProperties | format-list Get-QADUser : A parameter cannot be found that matches parameter name 'IncludeAllProperties'. At line:1 char:62 + Get-QADUser -SearchRoot 'myad.local/OU' -IncludeAllProperties <<<< | format-list Am I doing this wrong or do I have an older version of the ActiveRoles Management Shell for AD (how often it is updated?). -Kari "RichS" wrote: [Quoted Text] > You should be able to do what you want if you use the -IncludeAllProperties > parameter I think > -- > Richard Siddaway > Please note that all scripts are supplied "as is" and with no warranty > Blog: http://richardsiddaway.spaces.live.com/ > PowerShell User Group: http://www.get-psuguk.org.uk > > > "Kari" wrote: > > > Hi! > > > > I would need to create list of my users and I was planning to do it with > > Get-QADUser cmdlet. Unfortunately it seems that these objects have limited > > amount of properties so I can't select Division as one of the properties for > > my table (get-qaduser | select-object Name,LogonName,Company,division). > > > > Is there any way to query for the division information on each object in the > > pipeline? > > > > I know that Get-QADUser knows the object attribute division because I did a > > list on certain users just by querying the following: > > get-qaduser -seachroot 'myad.local' -objectattributes > > [ at ]{company='Example';division='Example'} > > > > Thru WMI or something? ... and if you're willing to help please be specific > > because I quite new with PS.

RE: Limited properties with user objects using Get-QADUser Kari 12.07.2007 06:38:03 I found out that some one else got it working: http://dmitrysotnikov.wordpress.com/2007/06/28/get-a-list-of-all-user-properties/ .... so why can't I? "Kari" wrote: [Quoted Text] > IcludeAllProperties is a parameter for Get-QADUser? It only returns an error > with my console. > > PS H:\> Get-QADUser -SearchRoot myad.local/OU' -IncludeAllProperties | > format-list > Get-QADUser : A parameter cannot be found that matches parameter name > 'IncludeAllProperties'. > At line:1 char:62 > + Get-QADUser -SearchRoot 'myad.local/OU' -IncludeAllProperties <<<< | > format-list > > Am I doing this wrong or do I have an older version of the ActiveRoles > Management Shell for AD (how often it is updated?). > > -Kari > > "RichS" wrote: > > > You should be able to do what you want if you use the -IncludeAllProperties > > parameter I think > > -- > > Richard Siddaway > > Please note that all scripts are supplied "as is" and with no warranty > > Blog: http://richardsiddaway.spaces.live.com/ > > PowerShell User Group: http://www.get-psuguk.org.uk > > > > > > "Kari" wrote: > > > > > Hi! > > > > > > I would need to create list of my users and I was planning to do it with > > > Get-QADUser cmdlet. Unfortunately it seems that these objects have limited > > > amount of properties so I can't select Division as one of the properties for > > > my table (get-qaduser | select-object Name,LogonName,Company,division). > > > > > > Is there any way to query for the division information on each object in the > > > pipeline? > > > > > > I know that Get-QADUser knows the object attribute division because I did a > > > list on certain users just by querying the following: > > > get-qaduser -seachroot 'myad.local' -objectattributes > > > [ at ]{company='Example';division='Example'} > > > > > > Thru WMI or something? ... and if you're willing to help please be specific > > > because I quite new with PS.

RE: Limited properties with user objects using Get-QADUser Dmitry Sotnikov 13.07.2007 11:10:01 Kari, Are you sure you need "division" and not "Department"? It could be that the division attribute is simply not set. PS C:\> get-qaduser "Dmitry Sotnikov" | select-object Name,LogonName,Company,Department Name LogonName Company Department ---- --------- ------- ---------- Dmitry Sotnikov DSotniko Quest Software BU - CTO -- Dmitry Sotnikov http://dmitrysotnikov.wordpress.com "Kari" wrote: [Quoted Text] > I found out that some one else got it working: > http://dmitrysotnikov.wordpress.com/2007/06/28/get-a-list-of-all-user-properties/ > > ... so why can't I? > > "Kari" wrote: > > > IcludeAllProperties is a parameter for Get-QADUser? It only returns an error > > with my console. > > > > PS H:\> Get-QADUser -SearchRoot myad.local/OU' -IncludeAllProperties | > > format-list > > Get-QADUser : A parameter cannot be found that matches parameter name > > 'IncludeAllProperties'. > > At line:1 char:62 > > + Get-QADUser -SearchRoot 'myad.local/OU' -IncludeAllProperties <<<< | > > format-list > > > > Am I doing this wrong or do I have an older version of the ActiveRoles > > Management Shell for AD (how often it is updated?). > > > > -Kari > > > > "RichS" wrote: > > > > > You should be able to do what you want if you use the -IncludeAllProperties > > > parameter I think > > > -- > > > Richard Siddaway > > > Please note that all scripts are supplied "as is" and with no warranty > > > Blog: http://richardsiddaway.spaces.live.com/ > > > PowerShell User Group: http://www.get-psuguk.org.uk > > > > > > > > > "Kari" wrote: > > > > > > > Hi! > > > > > > > > I would need to create list of my users and I was planning to do it with > > > > Get-QADUser cmdlet. Unfortunately it seems that these objects have limited > > > > amount of properties so I can't select Division as one of the properties for > > > > my table (get-qaduser | select-object Name,LogonName,Company,division). > > > > > > > > Is there any way to query for the division information on each object in the > > > > pipeline? > > > > > > > > I know that Get-QADUser knows the object attribute division because I did a > > > > list on certain users just by querying the following: > > > > get-qaduser -seachroot 'myad.local' -objectattributes > > > > [ at ]{company='Example';division='Example'} > > > > > > > > Thru WMI or something? ... and if you're willing to help please be specific > > > > because I quite new with PS.

RE: Limited properties with user objects using Get-QADUser Kari 13.07.2007 11:18:00 I'm sure it is division. We have a IDM software that has been written so that the division attribute is filled with all the user objects. I double-checked it with ADSi edit. Why doesn't the includeallproperties work with my PS? :( -K "Dmitry Sotnikov" wrote: [Quoted Text] > Kari, > > Are you sure you need "division" and not "Department"? It could be that the > division attribute is simply not set. > > PS C:\> get-qaduser "Dmitry Sotnikov" | select-object > Name,LogonName,Company,Department > > Name LogonName Company > Department > ---- --------- ------- > ---------- > Dmitry Sotnikov DSotniko Quest Software > BU - CTO > > -- > Dmitry Sotnikov > http://dmitrysotnikov.wordpress.com > > > "Kari" wrote: > > > I found out that some one else got it working: > > http://dmitrysotnikov.wordpress.com/2007/06/28/get-a-list-of-all-user-properties/ > > > > ... so why can't I? > > > > "Kari" wrote: > > > > > IcludeAllProperties is a parameter for Get-QADUser? It only returns an error > > > with my console. > > > > > > PS H:\> Get-QADUser -SearchRoot myad.local/OU' -IncludeAllProperties | > > > format-list > > > Get-QADUser : A parameter cannot be found that matches parameter name > > > 'IncludeAllProperties'. > > > At line:1 char:62 > > > + Get-QADUser -SearchRoot 'myad.local/OU' -IncludeAllProperties <<<< | > > > format-list > > > > > > Am I doing this wrong or do I have an older version of the ActiveRoles > > > Management Shell for AD (how often it is updated?). > > > > > > -Kari > > > > > > "RichS" wrote: > > > > > > > You should be able to do what you want if you use the -IncludeAllProperties > > > > parameter I think > > > > -- > > > > Richard Siddaway > > > > Please note that all scripts are supplied "as is" and with no warranty > > > > Blog: http://richardsiddaway.spaces.live.com/ > > > > PowerShell User Group: http://www.get-psuguk.org.uk > > > > > > > > > > > > "Kari" wrote: > > > > > > > > > Hi! > > > > > > > > > > I would need to create list of my users and I was planning to do it with > > > > > Get-QADUser cmdlet. Unfortunately it seems that these objects have limited > > > > > amount of properties so I can't select Division as one of the properties for > > > > > my table (get-qaduser | select-object Name,LogonName,Company,division). > > > > > > > > > > Is there any way to query for the division information on each object in the > > > > > pipeline? > > > > > > > > > > I know that Get-QADUser knows the object attribute division because I did a > > > > > list on certain users just by querying the following: > > > > > get-qaduser -seachroot 'myad.local' -objectattributes > > > > > [ at ]{company='Example';division='Example'} > > > > > > > > > > Thru WMI or something? ... and if you're willing to help please be specific > > > > > because I quite new with PS.

RE: Limited properties with user objects using Get-QADUser Dmitry Sotnikov 13.07.2007 11:36:01 Which version of the cmdlets are you using? Could you run the following to check? (get-command (get-pssnapin Quest.ActiveRoles.ADManagement).ModuleName).FileVersionInfo.ProductVersion Should tell you 1.0.3.249 if you are on the latest version. -- Dmitry Sotnikov http://dmitrysotnikov.wordpress.com "Kari" wrote: [Quoted Text] > I'm sure it is division. We have a IDM software that has been written so that > the division attribute is filled with all the user objects. I double-checked > it with ADSi edit. > > Why doesn't the includeallproperties work with my PS? :( > > -K > > "Dmitry Sotnikov" wrote: > > > Kari, > > > > Are you sure you need "division" and not "Department"? It could be that the > > division attribute is simply not set. > > > > PS C:\> get-qaduser "Dmitry Sotnikov" | select-object > > Name,LogonName,Company,Department > > > > Name LogonName Company > > Department > > ---- --------- ------- > > ---------- > > Dmitry Sotnikov DSotniko Quest Software > > BU - CTO > > > > -- > > Dmitry Sotnikov > > http://dmitrysotnikov.wordpress.com > > > > > > "Kari" wrote: > > > > > I found out that some one else got it working: > > > http://dmitrysotnikov.wordpress.com/2007/06/28/get-a-list-of-all-user-properties/ > > > > > > ... so why can't I? > > > > > > "Kari" wrote: > > > > > > > IcludeAllProperties is a parameter for Get-QADUser? It only returns an error > > > > with my console. > > > > > > > > PS H:\> Get-QADUser -SearchRoot myad.local/OU' -IncludeAllProperties | > > > > format-list > > > > Get-QADUser : A parameter cannot be found that matches parameter name > > > > 'IncludeAllProperties'. > > > > At line:1 char:62 > > > > + Get-QADUser -SearchRoot 'myad.local/OU' -IncludeAllProperties <<<< | > > > > format-list > > > > > > > > Am I doing this wrong or do I have an older version of the ActiveRoles > > > > Management Shell for AD (how often it is updated?). > > > > > > > > -Kari > > > > > > > > "RichS" wrote: > > > > > > > > > You should be able to do what you want if you use the -IncludeAllProperties > > > > > parameter I think > > > > > -- > > > > > Richard Siddaway > > > > > Please note that all scripts are supplied "as is" and with no warranty > > > > > Blog: http://richardsiddaway.spaces.live.com/ > > > > > PowerShell User Group: http://www.get-psuguk.org.uk > > > > > > > > > > > > > > > "Kari" wrote: > > > > > > > > > > > Hi! > > > > > > > > > > > > I would need to create list of my users and I was planning to do it with > > > > > > Get-QADUser cmdlet. Unfortunately it seems that these objects have limited > > > > > > amount of properties so I can't select Division as one of the properties for > > > > > > my table (get-qaduser | select-object Name,LogonName,Company,division). > > > > > > > > > > > > Is there any way to query for the division information on each object in the > > > > > > pipeline? > > > > > > > > > > > > I know that Get-QADUser knows the object attribute division because I did a > > > > > > list on certain users just by querying the following: > > > > > > get-qaduser -seachroot 'myad.local' -objectattributes > > > > > > [ at ]{company='Example';division='Example'} > > > > > > > > > > > > Thru WMI or something? ... and if you're willing to help please be specific > > > > > > because I quite new with PS.