Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Browsing an AD LDAP Database, I noticed that some employees registered twice: once as objectClass=Person, and another one as objectClass=Persond and objectClass=User.

In other words, two records in the AD LDAP database belong to one employee, or one employee has different distinguished names, so that the search on this person gives two results.

How it could happen? Is it an error in our database?

share|improve this question
up vote 0 down vote accepted

Directory servers that follow the directory information model have no restrictions on whether an attribute can appear twice in the database. Distinguished Names, however, must be unique. Some directory servers have a notion of attribute uniqueness, which, if enabled, would enforce the uniqueness of certain configured attributes, meaning that when such enforcement is configured, for example, for the attribute employeeNumber, the following could not occur (in the same database):




The above is a clumsy attempt to make an employee a member of two organizations. If uniqueness of the employeeNumber attribute (which in this case is a component of the distinguished name) is not enforced, then the above DNs become possible, though hardly advisable since better methods exist to establish membership of organizations.

There is nothing to prevent employees from being stored twice in your database, and this is a common occurrence and depends entirely on the data model used by the organization.

share|improve this answer
Thank you very much, that's clear! – mtm Aug 18 '11 at 11:28

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.