> objectclass: ou Oops, strike that last response. The other responder is of course correct, ou is not even an objectClass. Of course, if it were, my answer would have been correct. :-)