Leveraging WMI Scripting: Using Windows Management Instrumentation to Solve Windows Management Problems

There are three Active Directory providers, as shown in Table 3.49.
| Provider Name | to Provider Namespace | Class Provider | Instance Provider | Method Provider | Property Provider | Event Provider | Event Consumer Provider | Support Get | Support Put | Support Enumeration | Support Delete | Windows Server 2003 | Windows XP | Windows 2000 Server | Windows 2000 Professional | Windows NT 4.0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Active Directory LDAP Providers | ||||||||||||||||
| MicrosoftDSLDAPCIassAssociafionsProviderV1.0 | Root/directory/LDAP | X | X | X | X | X | X | X | ||||||||
| MicrosoftDSLDAPCIassProviderV1.0 | Root/directory/LDAP | X | X | X | X | X | X | X | ||||||||
| MicrosoftDSLDAPInstanceProviderV1.0 | Root/directory/LDAP | X | X | X | X | X | X | X | X | X |
To work with these providers, it is best to have an understanding of the Active Directory Schema, since WMI reflects its logical structure. All classes provided by the Active Directory class provider are mapped from the Active Directory schema classes. By accessing the Root\Directory\LDAP namespace, it is possible to reference any class and object in the Active Directory. Basically, we can say that the Active Directory providers mirror classes and instances from the Active Directory into this specific CIM repository namespace. To perform this mapping, the Active Directory Service providers follow naming rules to preserve the relationships that exist between the Active Directory classes and instances. Two...