You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
22 lines
1.7 KiB
22 lines
1.7 KiB
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML DIR="LTR"><HEAD>
|
|
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">
|
|
<TITLE>Windows NT Provider Component Description</TITLE>
|
|
<style type="text/css">@import url(td.css);</style></HEAD>
|
|
<BODY TOPMARGIN="0">
|
|
<H1><A NAME="_windows_nt_provider_component_description"></A><SUP></SUP>Windows NT Provider Component Description</H1>
|
|
|
|
<P>This component is supplied by Active Directory Service Interfaces (ADSI) to provide communication with Microsoft Windows NT version 4.0 primary domain controllers and backup domain controllers. Administrators and developers can enumerate and manage the resources in a directory service by using Component Object Model (COM) interfaces exported by ADSI. These interfaces are compliant with Automation for name-bound controllers like Java, Microsoft Visual Basic, and Microsoft Visual Basic, Scripting Edition (VBScript). ADSI can also provide an interface that can optimize performance for interfaces that are not compliant with Automation, to use with language environments like C and C++. </P>
|
|
|
|
<P>The default ADSI Windows NT provider cannot be assumed to be completely thread-safe. Developers of multithreaded applications should take care to properly coordinate any access between threads through the proper use of synchronization objects such as semaphores, mutexes, and critical sections.</P>
|
|
|
|
<H1>Component Configuration</H1>
|
|
|
|
<P>There are no configuration requirements for this component.</P>
|
|
|
|
<H1>For More Information</H1>
|
|
|
|
<P>Documentation on Windows NT Provider can be found in the Platform SDK, the Directory Services section of the MSDN Library, and at http://adsi.</P>
|
|
|
|
</BODY>
|
|
</HTML>
|