header1   header
header
header Register : : Login header
header
connector   connector
menuleft menuright
submenu   submenu
left
Access methods of Registry, WMI and ADSI
Last Post 01 Sep 2010 04:56 AM by Marco Shaw (MVP). 1 Replies.
Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
GyKosaUser is Offline
New Member
New Member
Posts:4
Avatar

--
01 Sep 2010 04:23 AM

    Hi,
    I'm new to PowerShell and would like to understand the motivation behind the differences in accessing the Registry, WMI and ADSI directory.

    The Registry can be accessed as e.g.:
    >Set-Location HKLM:\Software

    WMI can be accessed as e.g.:
    >Get-WmiObject Win32_ComputerSystem -Namespace "root\CIMV2" -ComputerName "."

    ADSI/LDAP can be accessed (bound) as e.g.:
    >$objADSI = [ADSI]"LDAP://DC=nwtraders,DC=msft”

    Aren't they supported by the same PowerShell Provider framework? If they are, why are these differences? As far as I know, Providers allow us to work with data stores as if they were mounted drives.

    Thank you!

    Marco Shaw (MVP)User is Offline
    Veteran Member
    Veteran Member
    Posts:1641
    Avatar

    --
    01 Sep 2010 04:56 AM
    Not *everything* is exposed as a provider. In some cases, like WMI for example, it is a completely different team that develops their own PowerShell functionality.

    There is an AD provider with Windows Server 2008 R2.
    Marco

    *Microsoft MVP - Windows PowerShell
    https://mvp.support.microsoft.com/profile/Marco.Shaw
    *Co-Author - Sams Windows PowerShell Unleashed 2nd Edition
    *Blog - http://marcoshaw.blogspot.com
    You are not authorized to post a reply.


    Active Forums 4.3
    right
    footer   footer
    footer Sponsored by Quest Software • SAPIEN Technologies • Compellent • Microsoft Windows Server 2008 R2 footer
    footer   footer