G
Guest
Hi everyone,
We are looking to utilize our AD schema (win2000/Exchange2000 environment)
by recording additional attributes which an application will query to feed an
in-house application. We are trying to track employee id, badge number, and
perhaps 3 other attributes. I realize that employee Id and number already
exist and I plan to use those, my question is how to go about populating the
other 3 attributes. The way I see it, I have (at least) 3 options:
1. Modify the schema to add these attributes
2. Use existing unused attributes (such as phone #, manager, etc) and have
the application reference those.
3. This is the one I am most curious about. When we installed Exchange, it
appears that we have 15 Extension Attributes. I would like to use these if
possible, even though it does appear that we would have to reference them as
extensionattribute1, extensionattribute2, rather than modifying the name of
them. But (finally) here's my question. From the AD Users and Computers it
looks like I can see them in the GUI if the user is assigned an email
address. However, these users do not require an email address and I'd rather
not set one up if at all possible. I'm assuming that even if the user does
not have an emailaddress/Exchange mailbox, we could still programatically
read/write to these attributes just as if we were to programatically
read/write to something like fax #, address, etc? Or is it "against the
rules" to use these attributes if the user does not have an email address
tied to it?
Thank you,
Brian
We are looking to utilize our AD schema (win2000/Exchange2000 environment)
by recording additional attributes which an application will query to feed an
in-house application. We are trying to track employee id, badge number, and
perhaps 3 other attributes. I realize that employee Id and number already
exist and I plan to use those, my question is how to go about populating the
other 3 attributes. The way I see it, I have (at least) 3 options:
1. Modify the schema to add these attributes
2. Use existing unused attributes (such as phone #, manager, etc) and have
the application reference those.
3. This is the one I am most curious about. When we installed Exchange, it
appears that we have 15 Extension Attributes. I would like to use these if
possible, even though it does appear that we would have to reference them as
extensionattribute1, extensionattribute2, rather than modifying the name of
them. But (finally) here's my question. From the AD Users and Computers it
looks like I can see them in the GUI if the user is assigned an email
address. However, these users do not require an email address and I'd rather
not set one up if at all possible. I'm assuming that even if the user does
not have an emailaddress/Exchange mailbox, we could still programatically
read/write to these attributes just as if we were to programatically
read/write to something like fax #, address, etc? Or is it "against the
rules" to use these attributes if the user does not have an email address
tied to it?
Thank you,
Brian