Custom AD/LDAP Attribute (in the User Schema)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

We have a legacy application that requires a custom Enrionment Variable
to be set. And this PC environment variable is on a "per user
basis".... basically it is a form of their userid with some extra
chars, etc.

We are looking at putting this attribute as an addition to our AD
schema, and trying to set the environment variable on the PC (in a
login script or something) when a person logs into the workstation.

We have applied for our X.500 OID (just to be sure our schema attribute
is "unique"), and I have read through several documents and tutorials
describing the proper and improper ways to add an attribute to the
schema. It looks like the best way is to add a new custom attribute,
and then create a new custom auxillary class, and then associate that
new attribute with the class, and then associate the new custom class
with the "user" class in AD.

Ok, so we have that all done, and we can now edit the new custom value
for each user in our test AD environment. So, what would be the
best/easiest (trying to avoid using client side vbscript, etc) to set
an environment variable (say, call it: %CUSTOMUSERNAME%) on the PC when
someone logs in?

Any ideas?

Thanks!

.

Relevant Pages

  • Re: storage of arbitrary attributes and their names
    ... Assume we have something called an Item with an ItemType and an Owner. ... If a customer wants to associate "arbitrary custom information" to an item, ... thought is to create a well-defined "standard" schema, ...
    (microsoft.public.sqlserver)
  • Re: Assign Schemas dynamically at receive pipelines
    ... I do completey agree with the idea of deploying and do realise its ... My custom component will then use this xsl. ... Having separate client assemblies, using assembly namespaces, using xml ... Having a schema dumped in directory, will have its own versioning issues. ...
    (microsoft.public.biztalk.general)
  • RE: Deriving from built-in DataGrid control
    ... IDE is the design-time xml schema warning. ... And for our custom controls, since there is no schema associated with them, ...
    (microsoft.public.dotnet.framework.aspnet.webcontrols)
  • Re: Help with planning large AD structure and schema modifications
    ... You may want to look into indexing attributes though or putting your custom attributes into the PAS depending on how you use them. ... it extends the Schema to have customAttributes you could use right away. ... The storagemight increase depending on what where you extend the schema and what objects use your custom attributes. ... Think of Exchange for example - it adds a lot of new attributes to all kinds of existing objects... ...
    (microsoft.public.windows.server.active_directory)
  • WCF w/ Custom DataSets
    ... System.Data.DataSet when the schema actually specifies my own custom ... After carefully weighing the non-SOA practice of having a service expose ... I've already got a reference to the class I'm after. ...
    (microsoft.public.dotnet.framework.webservices)