×

Loading...
Ad by
  • 最优利率和cashback可以申请特批,好信用好收入offer更好。请点链接扫码加微信咨询,Scotiabank -- Nick Zhang 6478812600。
Ad by
  • 最优利率和cashback可以申请特批,好信用好收入offer更好。请点链接扫码加微信咨询,Scotiabank -- Nick Zhang 6478812600。

NT的DOMAIN中也有ADSI,我从MSDN中贴了一篇文章,有兴趣就进来看看

本文发表在 rolia.net 枫下论坛Active Directory Services Interface (ADSI): Frequently Asked Questions
Microsoft Corporation

What is ADSI?

Active Directory Services Interfaces (ADSI) is a set of open interfaces that abstract the capabilities of directory services from different network providers to present a single view for accessing and managing network resources. Administrators and developers can use ADSI services to enumerate and manage resources in a directory service, no matter which network environment contains the resource. This can be an LDAP-based, NDS-based, or NTDS-based directory. It does not matter so long as a service provider is available for that directory service.

Which service providers will Microsoft deliver?

The ADSI SDK ships with providers for Microsoft® Windows NT®, Novell NDS, Novell 3x bindery and LDAP.

What problem is the ADSI initiative solving?

ADSI is solving four main problems:

Enabling single logon for client desktop to multiple directories.
Making it possible to write applications to one API but work with multiple directories.
Making it easier for end-users to find information with rich querying of directories.
Making it easier to manage multiple directories.
Which LDAP servers does it support?

ADSI will work against any LDAP server that supports, at a minimum, LDAP V2. We have tested the provider against the following LDAP servers:

Windows NT 4.0 PDC release (the Windows 2000 alpha release)
Netscape Directory Server 1.0
Exchange 5.0
Microsoft Commercial Internet System (MCIS) Address Book Server
University of Michigan SLAPD server
Novell’s LDAP-enabled NDS
When will it ship?

It shipped on 2/17/97 and is available as a free download from http://www.microsoft.com/ntserver/info/adsi.htm. It is also available in the Platform SDK.

How is ADSI different from OLE-DS?

ADSI is different from OLE-DS in two ways: First, as the API to the Active Directory, it reflects the name change of the Windows 2000 Directory Service to Active Directory and second, it offers full support for LDAP.

How does ADSI add 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 APIs are raw APIs which are somewhat difficult to write to. While Active Directory will offer full support for the LDAP C APIs we also felt it was critically important to make it easy to write to the Active Directory, or for that matter any directory service, including LDAP. As such, we offered ADSI to the industry in an open design review in 1995 and have now delivered on that specification. Additionally, ADSI supports multiple high-level languages. High-level languages, such as Visual Basic®, Perl, Rexx, as well as C/C++, can be used to develop directory service applications. This means that administrators and developers can use the tools they already know. Similarly, ADSI offers support for Java—ADSI objects provide easy access to directory services for Java applets and programs through Java COM.

How much functionality for each of the directories do I get with applications written to ADSI?

ADSI provides the same functionality you would have if you had written an application to the native protocol of a specific DS. So if an application were written to ADSI using all of the service providers delivered in the SDK (Windows NT, NDS, NetWare bindery, LDAP) then the client accessing these DSs via an application written to ADSI would have 100 percent functionality for each of the DSs.

Are there any performance hits using ADSI as opposed to writing to natively to a specific DS?

No. The ADSI routing layer, which handles the calls from the application to the service providers for each of the DSs, is extremely efficient. There is no noticeable performance degradation between writing to ADSI as opposed to the native API for specific DSs.

Is Microsoft working with the industry on ADSI?

Yes. Microsoft has had a very open process and solicited feedback the ADSI APIs, beginning with the first open design review in the summer of 1995 through the AdMETAstration Workshop held in February of 1997. 40+ vendors attended this preview, including Active Voice, Cabletron Systems, Inc., CI Partners, Compaq Computer Corporation, Computer Associates, CompuWare, Control Data Systems, Inc., Digital Equipment Corporation, FastLane Technologies, Inc., Installshield, IntraSoft, Linkage, LLC, Mission Critical Software, NetMagic Systems, Inc., NetPro, NetVision, Novell, Octopus Technologies, Inc., OpenVision Technologies, QueriSoft, Siemens-Nixdorf, Symantec Corporation, World Talk, Zoomit International.

Are there any applications that are being written to ADSI?

Yes. There are currently applications being written to ADSI by several companies, including QueriSoft, NetVision, and NetMagic. There will be more to follow in the coming months. Also, all BackOffice applications will be written to support ADSI so that they can access/leverage the Active Directory.更多精彩文章及讨论,请光临枫下论坛 rolia.net
Report

Replies, comments and Discussions:

  • 工作学习 / IT杂谈 / 有没有人听说TELNET到WINDOWS 2000/NT的程序?我影像是TELNET只在UNIX上用,
    • If I remember correctly, Win2000 Server has a telnet server option under network that you can install.
    • start->programs->Administrative Tools->telnet Administration->4 To start the telnet Serverce.
      Or you can go to start->programs->Administrative Tools->services to start service manually.
      • Remember to install it first, I remember it's an option.
    • I think you means the terminal service of Windows 2000 .
      Windows NT 4.0 only provide the command "telnet" to telnet other computer such as Unix Host coz it merely is a client tool.

      Now windows 2000 can provide the terminal function like Unix that support user to telnet Windows 2000 or XP and run the application from the client. This is a server-end service and it merely is bundled in the Windows 2000 server version, but not in windows 2000 personal version.
      • 领导叫我写一个利用NTLM的AUTHENTICATION程序利用WIN 2000上的用户数据库!那位高手做过?程序要在UNIX上运行,C,JAVA都可以。
        • sorry, I am confused by your question. What do your project want to implement ?
          Is the application running on unix to access windows User DB by using NTLM Authentication?
          • Yap!Any suggestion?
            Samba?
            • yes, it might be a resolution...but to my personal opinion, I think ADSI is the first choice...
              sorry, I am not familiar with Java, so couldn't give you any piont on this.
        • ldap + adsi
          • 谢谢,我们还没升级到AD.以后应该会.不过为什么用ADSI,用JNDI不是JAVA更方便?
            • I think you are right, in Java should be JNDI.
            • NT的DOMAIN中也有ADSI,我从MSDN中贴了一篇文章,有兴趣就进来看看
              本文发表在 rolia.net 枫下论坛Active Directory Services Interface (ADSI): Frequently Asked Questions
              Microsoft Corporation

              What is ADSI?

              Active Directory Services Interfaces (ADSI) is a set of open interfaces that abstract the capabilities of directory services from different network providers to present a single view for accessing and managing network resources. Administrators and developers can use ADSI services to enumerate and manage resources in a directory service, no matter which network environment contains the resource. This can be an LDAP-based, NDS-based, or NTDS-based directory. It does not matter so long as a service provider is available for that directory service.

              Which service providers will Microsoft deliver?

              The ADSI SDK ships with providers for Microsoft® Windows NT®, Novell NDS, Novell 3x bindery and LDAP.

              What problem is the ADSI initiative solving?

              ADSI is solving four main problems:

              Enabling single logon for client desktop to multiple directories.
              Making it possible to write applications to one API but work with multiple directories.
              Making it easier for end-users to find information with rich querying of directories.
              Making it easier to manage multiple directories.
              Which LDAP servers does it support?

              ADSI will work against any LDAP server that supports, at a minimum, LDAP V2. We have tested the provider against the following LDAP servers:

              Windows NT 4.0 PDC release (the Windows 2000 alpha release)
              Netscape Directory Server 1.0
              Exchange 5.0
              Microsoft Commercial Internet System (MCIS) Address Book Server
              University of Michigan SLAPD server
              Novell’s LDAP-enabled NDS
              When will it ship?

              It shipped on 2/17/97 and is available as a free download from http://www.microsoft.com/ntserver/info/adsi.htm. It is also available in the Platform SDK.

              How is ADSI different from OLE-DS?

              ADSI is different from OLE-DS in two ways: First, as the API to the Active Directory, it reflects the name change of the Windows 2000 Directory Service to Active Directory and second, it offers full support for LDAP.

              How does ADSI add 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 APIs are raw APIs which are somewhat difficult to write to. While Active Directory will offer full support for the LDAP C APIs we also felt it was critically important to make it easy to write to the Active Directory, or for that matter any directory service, including LDAP. As such, we offered ADSI to the industry in an open design review in 1995 and have now delivered on that specification. Additionally, ADSI supports multiple high-level languages. High-level languages, such as Visual Basic®, Perl, Rexx, as well as C/C++, can be used to develop directory service applications. This means that administrators and developers can use the tools they already know. Similarly, ADSI offers support for Java—ADSI objects provide easy access to directory services for Java applets and programs through Java COM.

              How much functionality for each of the directories do I get with applications written to ADSI?

              ADSI provides the same functionality you would have if you had written an application to the native protocol of a specific DS. So if an application were written to ADSI using all of the service providers delivered in the SDK (Windows NT, NDS, NetWare bindery, LDAP) then the client accessing these DSs via an application written to ADSI would have 100 percent functionality for each of the DSs.

              Are there any performance hits using ADSI as opposed to writing to natively to a specific DS?

              No. The ADSI routing layer, which handles the calls from the application to the service providers for each of the DSs, is extremely efficient. There is no noticeable performance degradation between writing to ADSI as opposed to the native API for specific DSs.

              Is Microsoft working with the industry on ADSI?

              Yes. Microsoft has had a very open process and solicited feedback the ADSI APIs, beginning with the first open design review in the summer of 1995 through the AdMETAstration Workshop held in February of 1997. 40+ vendors attended this preview, including Active Voice, Cabletron Systems, Inc., CI Partners, Compaq Computer Corporation, Computer Associates, CompuWare, Control Data Systems, Inc., Digital Equipment Corporation, FastLane Technologies, Inc., Installshield, IntraSoft, Linkage, LLC, Mission Critical Software, NetMagic Systems, Inc., NetPro, NetVision, Novell, Octopus Technologies, Inc., OpenVision Technologies, QueriSoft, Siemens-Nixdorf, Symantec Corporation, World Talk, Zoomit International.

              Are there any applications that are being written to ADSI?

              Yes. There are currently applications being written to ADSI by several companies, including QueriSoft, NetVision, and NetMagic. There will be more to follow in the coming months. Also, all BackOffice applications will be written to support ADSI so that they can access/leverage the Active Directory.更多精彩文章及讨论,请光临枫下论坛 rolia.net
              • Good Tip, this article is worthy reading.......Thanks!
              • 不错的建议不过我看了一下,JAVA+ADSI必须用MS的JAVA SDK和Virtual Machine. MS早就说不支持JAVA了,这样的VM相当于SUN什么版本的JVM?MS的JAVA VM 里SERVLET能不能正常运行还是个疑问。
    • I used it before.
      1.On w2K Server: (1) install the terminal service then start this service.
      (2)create the client software (need 2 floopy disk )
      2.On Client(W2k professional, NT4 workstation,win98...):install the client software then run it
      So you can use it.
      Note: There has a different between w2k server and WinXP.Two or more person can connect to W2k Server at the same time.But only one person can connect to WinXP at the same time.
      • 是不是所有的用户都可以LOGIN?
        • It's configurable.
          • 有没有人写过JAVA 的WRAPPER把这个TELNET WRAP起来(只好在PC上搞了).看样子我只能找个办法应付一下.以后还不知道是不是该成LDAP.先过年关.
      • it's more powerful than telnet, and can't be used on unix box.