>
>> The only difference is the last entry. Your custom objectClass makes the
>> object not a user but a custom object to ADUC.
>
> That's interesting, since as far as I've been lead to understand there's
> no inherent ordering to attribute values in LDAP.
>
> --
> Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
You are correct, generally there is no order to multi-valued attributes. But
there is an objectClass hierarchy. The objectClass attribute is the only one
with ordered values. The first value is at the top of the hierarchy, the
last is the most derived class, which is the class the object is an instance
of. The Class method exposed by the IADs interface returns one value. For
example:
user objects:
objectCategory=person; objectClass=top,person,organizationalPerson,user;
Class=user
computer objects:
objectCategory=computer;
objectClass=top,person,organizationalPerson,user,c omputer; Class=computer
contact objects:
objectCategory=person; objectClass=top,person,organizationalPerson,contac t;
Class=contact
If you filter on objects of class "user" (either with objectClass=user or
with the Filter method of IADs), you get both user and computer objects. If
you retrieve all objects with objectCategory=person, you get user and
contact objects.
From the documentation I find that classes can be structural, abstract, or
auxiliary. Only structural class can be instantiated. Auxiliary classes just
add attributes the object can have. Abstract classes are templates to derive
new classes.
--
Richard Mueller
MVP Directory Services
Hilltop Lab -
http://www.rlmueller.net
--