Thanks for the information - good work with the re-engineering and
scripting. It's seems a shame and more than a little inconsistent that MS
would take such a different approach with the ActiveDirectory PSProvider by
not exposing attributes and using the DistinguishedName instead of the Name
as the pipeline input to Get-ChildItem -Path parameter. It would be nice to
have a unified approach for accessing the file system, registry, DBMSs,
"Chris Dent" <chris@newsgroup> wrote in message
> The MS AD provider does not expose that property I'm afraid, nor does it
> expose a way to get arbitrary properties it seems.
> That leaves converting the ADObject into a DirectoryEntry, back to
> old-fashioned ADSI.
> You know the property structure is officially undocumented don't you?
> Admittedly I have a map of it on my blog here:
> And there's a script which reads it here:
> Of course, you should feel free to write your own property converters if
> you wish
> SPC wrote:
>> How does one retrieve the dnsRecord attribute from a Dns-Node
>> objectCategory in Active Directory using the ActiveDirectory PSProvider
>> on version 2.0 PowerShell with ADWS installed on the AD server and an
>> "AD:" PSDrive configured?
>> "Get-Item 'AD:\DC=a,DC=b.com,CN=MicrosoftDNS,CN=System,DC=b,DC=com' |
>> Get-Member" does not appear to return a method for listing entries.