Limited properties with user objects using Get-QADUser

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
@{company='Example';division='Example'}

Thru WMI or something? ... and if you're willing to help please be specific
because I quite new with PS.

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
> @{company='Example';division='Example'}
>
> Thru WMI or something? ... and if you're willing to help please be specific
> because I quite new with PS.

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
> > @{company='Example';division='Example'}
> >
> > Thru WMI or something? ... and if you're willing to help please be specific
> > because I quite new with PS.

I found out that some one else got it working:
http://dmitrysotnikov.wordpress.com/...er-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
> > > @{company='Example';division='Example'}
> > >
> > > Thru WMI or something? ... and if you're willing to help please be specific
> > > because I quite new with PS.

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/...er-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
> > > > @{company='Example';division='Example'}
> > > >
> > > > Thru WMI or something? ... and if you're willing to help please be specific
> > > > because I quite new with PS.

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/...er-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
> > > > > @{company='Example';division='Example'}
> > > > >
> > > > > Thru WMI or something? ... and if you're willing to help please be specific
> > > > > because I quite new with PS.

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:

> 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/...er-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
> > > > > > @{company='Example';division='Example'}
> > > > > >
> > > > > > Thru WMI or something? ... and if you're willing to help please be specific
> > > > > > because I quite new with PS.

Ok. Now we made some progress. I'm running ver. 1.0.2.191! I'll get the
latest version of the extension and see what happens then.

-Kari

"Dmitry Sotnikov" wrote:

> 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:
>
> > 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/...er-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
> > > > > > > @{company='Example';division='Example'}
> > > > > > >
> > > > > > > Thru WMI or something? ... and if you're willing to help please be specific
> > > > > > > because I quite new with PS.

Uaargh... This is driving me nuts!

I'm trying to query all the user objects in AD but not all of them include
Company and division data. This is what happens:

PS H:\> Get-QADUser -includeallproperties | Select-Object
Name,LogonName,Company,division
Select-Object : Exception getting "Company": "The given key was not present
in the dictionary."
At line:1 char:50
+ Get-QADUser -includeallproperties | Select-Object <<<<
Name,LogonName,Company,division

If I query an object that has these values, there's no problem:
PS H:\> Get-QADUser "testuser" | Select-Object Name,LogonName,Company,division

Name LogonName Company
division
---- --------- -------
--------
Testuser Testuser Model
Division

Name LogonName
division
---- ---------
--------
Guest Guest
Select-Object : Exception getting "Company": "The given key was not present
in the dictionary."
At line:1 char:50
+ Get-QADUser -includeallproperties | Select-Object <<<<
Name,LogonName,Company,division
Administrator Administrator
Select-Object : Exception getting "Company": "The given key was not present
in the dictionary."
At line:1 char:50
+ Get-QADUser -includeallproperties | Select-Object <<<<
Name,LogonName,Company,division

"Kari" wrote:

> Ok. Now we made some progress. I'm running ver. 1.0.2.191! I'll get the
> latest version of the extension and see what happens then.
>
> -Kari
>
> "Dmitry Sotnikov" wrote:
>
> > 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:
> >
> > > 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/...er-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
> > > > > > > > @{company='Example';division='Example'}
> > > > > > > >
> > > > > > > > Thru WMI or something? ... and if you're willing to help please be specific
> > > > > > > > because I quite new with PS.

As PowerShell as more than enough ADSI power natively without the AD cmdlets

You can also use the native PowerShell method for this that works fine:

Function Get-AdUser ($name) {
(New-Object
System.DirectoryServices.DirectorySearcher("(&(CN=$name)(objectClass=User))")).findone().getdirectoryEntry()
}

PoSH> Get-AdUser foo | Select-Object Name,LogonName,Company,division

Name LogonName
Company divisio
---- ---------
------- -------
{foo} {}
{}

Greetings /\/\o\/\/

"Kari" wrote:

> Uaargh... This is driving me nuts!
>
> I'm trying to query all the user objects in AD but not all of them include
> Company and division data. This is what happens:
>
> PS H:\> Get-QADUser -includeallproperties | Select-Object
> Name,LogonName,Company,division
> Select-Object : Exception getting "Company": "The given key was not present
> in the dictionary."
> At line:1 char:50
> + Get-QADUser -includeallproperties | Select-Object <<<<
> Name,LogonName,Company,division
>
> If I query an object that has these values, there's no problem:
> PS H:\> Get-QADUser "testuser" | Select-Object Name,LogonName,Company,division
>
> Name LogonName Company
> division
> ---- --------- -------
> --------
> Testuser Testuser Model
> Division
>
> Name LogonName
> division
> ---- ---------
> --------
> Guest Guest
> Select-Object : Exception getting "Company": "The given key was not present
> in the dictionary."
> At line:1 char:50
> + Get-QADUser -includeallproperties | Select-Object <<<<
> Name,LogonName,Company,division
> Administrator Administrator
> Select-Object : Exception getting "Company": "The given key was not present
> in the dictionary."
> At line:1 char:50
> + Get-QADUser -includeallproperties | Select-Object <<<<
> Name,LogonName,Company,division
>
> "Kari" wrote:
>
> > Ok. Now we made some progress. I'm running ver. 1.0.2.191! I'll get the
> > latest version of the extension and see what happens then.
> >
> > -Kari
> >
> > "Dmitry Sotnikov" wrote:
> >
> > > 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:
> > >
> > > > 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/...er-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
> > > > > > > > > @{company='Example';division='Example'}
> > > > > > > > >
> > > > > > > > > Thru WMI or something? ... and if you're willing to help please be specific
> > > > > > > > > because I quite new with PS.