how do I enable the Assistant and Division attributes in Active Directory

I can't seem to find any info on how do I enable the Assistant and Division attributes in Active Directory.

peterevisonAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NJComputerNetworksCommented:
Modifying the details templates takes a couple steps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;313962&Product=exch2k

See note in step 7 - it talks about the attribute requiring a MAPIID.  If
the attributes you're using don't have that attribute populated, you'll need
to add it.  It's a system-only property, which requires special procedures
to edit it that are described in MSDN.

I've asked MS in the past if there was a defined "safe range", and the
answer is no. Traditionally anything in the 0x8000 range is considered
"application defined" by MAPI. Given that there won't likely be any new AD
schema changes from the Exchange team in the next 2-3 years, picking a value
that's not currently used by a schema property should be relatively safe. It
also shouldn't be too hard to make adjustments to the chosen values in the
future even if schema changes do cause a conflict.
NJComputerNetworksCommented:
TheCleanerCommented:
Are you talking about being able to see these attributes in AD in the GUI?

You can try and follow the advice here:

http://www.petri.co.il/add_user_account_information_to_dsa.htm

but it requires some scripting and changes to AD.


I have done this the "ghetto AD" way before if you have extra attributes in the GUI you aren't using, and don't mind mentally mapping the attributes.

What I mean is:

Take for instance "organization".  If everyone is in the same organization what's the point of populating this?  Instead use it for "Division".

Same for "title" if not needed or similar....

Granted it's not the best way, but if only you or a few admins will ever see this attribute and it's just used for scripting or reporting purposes then it will work.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TheCleanerCommented:
Happy to help...thanks for the points.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.