I've got some powershell scripts that are creating Active Directory user objects using powershell because we're trying to set some attributes that are not available in the get/set user information actions. Im running into a problem setting employeeID on the user objects as well as a few other attributes. So I've tried using the quest cmdlets as well as writing my own function that binds to user objects and setting the employeeid property of the user. For whatever reason, these attributes do not seem to allow me to set them.
Now if I execute the script in powershell outside of LPM, it works perfectly. Does anyone have any ideas on why this might happen?
Im wondering if LPM uses a specific older version of powershell or something to that effect.