Well...
I can create an evironment variable into the machine without a problem:
Since department is a user based thing, the fastest way to create it is with a login script (which is user based).
It can't be added as part of the GM, snapshot, or as a machine startup script as all users use the same pool.
Unfortunately, this variable is not created quickly enough for PM to read it, or it just doesn't read it at all.
I have tried creating the variable in the USER and VOLATILE environment, but it seems PM has already loaded before it has been created by the login script (we run asynchronously). It can't be created in the SYSTEM environment, as the user will not have permissions at login script time to perform that action.
PM creates a folder called %department% in the profile area, rather than resolving the variable.
Ideally, it would be nice if the PM functionality could determine the AD attribute itself (your choice of attributes), and apply the variable to the volatile environment at login time. I might put in an enhancement request for this.... but if anyone has other suggestions in the mean time, I would appreciate a post.
