(imported topic written by SystemAdmin)
I wrote a fixlet that adds a path to the PATH environment variable. (The script creates and runs a vbscript, which makes the change.) This works nicely, a look at the system environment variables or a newly-opened command prompt shows it worked.
Unfortunately the action always reports failed and the fixlet remains relevant until the next system restart. From my tests, it appears the BigFix client doesn’t see environment changes. I manually changed a system environment variable and BigFix still saw the old value.
Restarting the BESClient service doesn’t help. That surprised me, I assumed the client loads the environment when it starts and would load the new environment when the service restarted.
Is there a way to tell the client to update its environment without restarting the system?