As with all schema objects, ADSI architecture defines the LDAP schema container object in the root node. For example, if you use a browser that can bind to a schema object, such as adsvw.exe, you would bind to the schema container object in the following way:
Under the LDAP implementation, you must already know the name of the LDAP server to which you want to bind. You cannot browse through a list of all the LDAP servers on the network because there is no underlying network call that supports that information.
Binding to this example LDAP schema object, you can display the list of more than a hundred schema class objects, hundreds of property objects, and a dozen or so syntax objects. The following figure shows the beginning of the expanded list of schema class objects. The right pane highlights the IADsClass::OptionalProperties property selection, displaying its contents as a Property Value.
