Hi, I have already read the article, but I am unable to make the approach work. Have you tried it out? /Michael -----Original Message----- From: Rechenberg, Andrew Sent: ma 02-07-2001 21:52 To: Michael Schacht Hansen; openldap-software@OpenLDAP.org Cc: Subject: RE: Custom Schema and MS ADSI I think the information for which you search is in this MSKB Article: http://support.microsoft.com/support/kb/articles/Q251/1/95.ASP It describes "How to Use ADSI to Query a Third-Party LDAP Server." Hope this helps. Regards, Andrew Rechenberg Network Team, Sherman Financial Group arechenberg@shermanfinancialgroup.com Phone: 513.677.7809 Fax: 513.677.7838 -----Original Message----- From: Michael Schacht Hansen [ mailto:msh@cursum.com] Sent: Monday, July 02, 2001 6:44 AM To: openldap-software@OpenLDAP.org Subject: Custom Schema and MS ADSI Hi, I have been able to follow several threads where people have tried to access custom classes and attributes with Microsoft ADSI. I have not seen any solution to the problem yet. I have tried almost every possible combination. My questions are: 1. Is there anybody who has actually accessed custom attributes and classes from ADSI (for instance with VB)? 2. How do you get ADSI to discover the schema? In my case all my custom classes are missing, but also classes who are not in the core schema, like inetOrgPerson. 3. As I have understood it, OpenLDAP 2.0 exposes the schema as described in LDAP v3; I am able to browse the schema and custom classes with other clients like "gq". So who is violating the protocol? Is it the ADSI or is it OpenLDAP? 4. Is it possible to define the schema in the registry of the client machine? If so, could somebody point to a description of how this is done? I would really like to hear from anyone who has been able to read custom attributes through VBScript and ADSI. If they would send me a pointer to some example code, it would make my day. Thanks in advance, /Michael Schacht Hansen
<<winmail.dat>>