Active Directory Service Interface (ADSI): frequently asked Questions

Active Directory Service Interface (ADSI): frequently asked Questions
Microsoft Inc.
What is ADSI?
The Active Directory Service Interface (ADSI) is a class of open interfaces that extract directory services from different networks to provide a single view of network resource access and management. Regardless of which network environment contains these resources, system administrators and developers can use ADSI's capabilities to enumerate and manage resources in a directory service. This directory can be an LDAP based directory, or it can be based on NDS or an NTDS based directory. As to which is not related, as long as the service provider provided by the directory service is valid.
What service packages will Microsoft release?
It is an ADSI SDK that supports Microsoft®windows NT®, Novell NDS, Novell 3x Integration, and LDAP.
What problems does ADSI initially solve?
ADSI solves four aspects of the problem:
Making it possible for a single customer to log on to multiple directories.
Makes it possible to write applications to only one API and work in multiple directories.
makes it easier for end users to find rich directory query information.
Make multiple directory management easier.
What kind of LDAP server does ADSI support?
ADSI will support all LDAP servers that can be supported, but at least for LDAP V2. We have tested the following LDAP servers:
Windows NT 4.0 PDC version (that is, NT 5 a Beta)
Netscape Directory Server 1.0
Exchange 5.0
Microsoft Commercial Internet System (MCIS) Address Book Server
SLAPD Server, University of Michigan
Novell ' s ldap-enabled NDS
When will ADSI be released?
It was released on February 17, 1997 and can be downloaded freely from the http://www.microsoft.com/ntserver/info/adsi.htm site or from the MSDN Library, including the MSDN libraries, SDK Documentation, Platform SDK, Active Directory SDK.
What is the difference between ADSI and ole-ds?
ADSI differs from Ole-ds in two ways: first, as an API for the Active Directory, it reflects the NT 5 directory service function for the Active Directory name change, and second, it fully supports LDAP.
How does ADSI add a value to LDAP?
ADSI adds value to LDAP in two ways: it is a higher level API set than LDAP, and it is easier to use than LDAP. The LDAP C API is the original API and it is difficult to communicate with it. When the Active Directory fully supports the LDAP C API, it is very important to communicate with the Active Directory or any directory services (including LDAP). In fact, we made ADSI available to the industry in 1995 as an open design review, and we have now released detailed instructions. In addition, ADSI supports a variety of high-level languages. These high-level languages, including visual basic®, Perl, Rexx, and the languages that can be used to develop directory service applications. This means that administrators and developers can use the tools they are familiar with. Similarly, ADSI supports JAVA-ADSI objects to provide an accessible directory service to Java programs through Java COM.