This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Active Directory Service Interfaces
Active Directory Service Interfaces

Version management

Difference between version and

At line 1 added 29 lines
!!! Overview[1]
[{$pagename}] ([ADSI]) is a set of COM interfaces used to access the features of directory services from different network providers.
[{$pagename}] is used in a distributed computing environment to present a single set of [Microsoft Active Directory] interfaces for managing network resources.
Administrators and developers can use [{$pagename}] to enumerate and manage the resources in a [Microsoft Active Directory], no matter which network environment contains the resource.
[{$pagename}] enables common administrative tasks, such as adding new users, managing printers, and locating resources in a distributed computing environment.
!! More details[2]
[{$pagename}] works by abstracting the capabilities of [Directory Services] from different network providers to present a single set of interfaces for managing network resources in a distributed computing network.
ADSI provides a simple, open, functionally rich, and scriptable method for interfacing with any [Directory Services], independent of the vendor.
[{$pagename}] is built on the [Component Object Model] and consists of two types of [COM] objects (directory service [leaf] objects and directory service container objects) that clients can manipulate with interfaces.
[{$pagename}] providers are used to implement these objects and their interfaces. Each object in a given namespace is identified using a unique name. For example, file system objects can be specified using their absolute path, while directory objects are usually specified using their [X.500] address. However, [ADSI] is flexible enough to handle any naming system used by third-party vendors’ directory service implementations.
[ADSI] can be used by programmers and administrators to create directory-enabled applications using tools such as Microsoft Visual Basic or Microsoft Visual C++. ADSI supports the [Lightweight Directory Access Protocol] ([LDAP]) C API defined in Request for Comments (RFC) number 1823, which specifies a low-level interface for C language programming and provides support for the [Messaging Application Programming Interface] ([MAPI]) so that legacy [MAPI] applications will work with [Microsoft Active Directory].
None of the [ADSI] automation interfaces directly expose [LDAP controls|SupportedControl]. That means they cannot be utilized from VBScript. On the other hand, many of the controls, such as [Simple Paged Results Control] or [Subtree Delete Control], are wrapped within their own [ADSI] methods that can be used within VBScript.
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Active Directory Service Interfaces|https://msdn.microsoft.com/en-us/library/aa772170(v=vs.85).aspx|target='_blank'] - based on information obtained 2016-08-10
* [#2] - [Active Directory Service Interfaces (ADSI)|http://www.thenetworkencyclopedia.com/entry/active-directory-service-interfaces-adsi/|target='_blank'] - based on information obtained 2016-08-10
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop