Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
ADSI Service Providers

ADSI Service Providers

ADSI includes the service providers listed in the following table.

Service providerDescriptionFor more information


Namespace implementation compatible with Lightweight Directory Access Protocol.

ADSI LDAP Provider


Namespace implementation compatible with Windows.

ADSI WinNT Provider


Namespace implementation compatible with Novell NetWare Directory Service.

ADSI NDS Provider


Namespace implementation compatible with Novell NetWare 3.x.



Other service providers are included as part of products other than ADSI. The following are the ADSI service providers implemented by Microsoft.

Service providerFor more information


IIS ADSI Provider Architecture


The methods and property methods exposed by ADSI interfaces are not supported by every service provider. Because different directory services vary in the types of objects and properties stored, use different protocols, and authentication, ADSI is designed to work seamlessly with supported service providers. Thus, there are interfaces, methods, and property methods that work with one service provider, such as LDAP, that may not work on another, such as WinNT.

This section contains provider-specific information, such as the ADsPath format, a listing of ADSI objects used for that service provider, and data type and syntax information for the service providers included with ADSI. There is also a summary description of ADSI interfaces supported by each provider included with ADSI.

In ADSI, different providers are associated with different DLLs. The LDAP provider is associated with Adsldp.dll, Adsldpc.dll, and Adsmsext.dll. WinNT is associated with Adsnt.dll, NDS with Adsnds.dll, and NWCOMPAT with Adsnw.dll. ROUTER is associated with Activeds.dll.

Note  Do not assume that default ADSI providers are thread-safe. Multithreaded application developers should coordinate access between threads through the proper use of synchronization objects such as semaphores, mutexes, critical sections, and so on.

For more information about ADSI service providers, see ADSI Router and Provider Support of ADSI interfaces.



© 2015 Microsoft