Of course you can drop environmental variables changes out to users/systems
via AD.Your vehicle for this, as with all client system configs, is Group
Policy.
You can create an ADM file that makes the required registry changes.
Or ,more commonly, use a log on script specified by a GPO to set these
variables.
Check out
http://windows.about.com/od/tipsarchive/l/bltip419.htm
as a launching point.
Unfortunately this is probably not as real time as you would like it to be,
but without a clearer statement of the problem its the best answer I can
give right now.
Paul, no offense, but I just do not understand what you are talking about
with extending the schema and how that would be used to address this
question. The schema is your definition of objects and attributes in the AD
database and has no connection to environmental variables that I am aware
of.
In any case, MS recommends not to touch the schema unless you have a really
good, well defined reason.
--
Manny Borges
MCSE NT4-2003 (+ Security)
MCT, Certified Cheese Master
The pen is mightier than the sword, and considerably easier to write with.
-- Marty Feldman