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

I need to add some attributes to the user class in Active Directory.

I see that to do this it is either possible to add the attributes directly to the user class, or to create an auxiliary class containing my attributes, and then attach the auxiliary class to user.

What are the pros and cons of the two approaches? I read somewhere that using an auxiliary class is recommended, but I could not find out why.

share|improve this question
up vote 5 down vote accepted

Using an auxiliary class means that your private extensions are contained within this class and can be handled as one entity, and it is separated from the standard user class, avoiding conflicts. As this has no drawbacks and might avoid potential problems down the road, I can't think of a single reason why anyone would even consider to extend the user class instead of using an aux class.

share|improve this answer
Thanks, for sure I will go for the auxiliary class. What kind of conflicts could there be? – Paolo Tedesco Jan 17 '14 at 12:00
I can't think of a specific issue at the moment, but I know from experience that you should never alter something as ubiquitous as an AD default schema if you can avoid it, as all kind of things expect it to be in a certain state and maybe don't work well if this state is altered in any way. These issues will pop up in places you expect them least and are usually difficult to debug. – Sven Jan 17 '14 at 13:52

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.