Novell ZENworks 10 Configuration ManagementNovell ZENworks 11 Configuration Management
The ZCM Agent does not recognize changes to the environment table until a reboot, which causes some applications to not run as expected or simply not run at all. In the event of variables set in the login script, they may never be recognized.
For ZCM 11: This is fixed in version 11.2 for Non-Volatile Environment Variables - see KB 7010044 "ZENworks Configuration Management 11.2 - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7010044
With 11.2, Variables in "HKCU\Environment Volatile", such as login script variables, may not be detected. This is fixed in version 11.2.1 - see KB 7010042 "ZENworks Configuration Management 11.2.1 - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7010042
StatusReported to Engineering
The ZenUserDaemon.exe will inherit the Windows Environment table when it is started, but like any other Windows process, any changes to Windows variables will not be reflected in any currently running process. Any Process Spawned by ZCM will inherit the ZenUserdaemon's environment space, which could be different than the general Windows Environment space if it changed after ZenUserDaemon.exe started. ZCM 11.2 will now update it's own environment from Windows prior to various actions so that it's environment matches the current Windows environment.
Note: If Login Script Variables are not seen outside of ZCM either, then examine TID#7006517, though this TID will most likely not have any direct impact on ZCM's ability to see these variables.