Custom scipts converted from ZENworks 7 not running in ZENworks 10 Configuration Management

  • 7000366
  • 13-May-2008
  • 30-Apr-2012


Novell ZENworks 10 Configuration Management


Example: a converted application object from ZEN 7 has the following script in the "run after distribution" portion of the distribution script:


The script engine location is defined as:


When launching the application, it gives an error that CMD cannot be found.


Modify the ZCM version to have the script engine be CMD.exe instead.
The current ZCM behavior for run script is that the engine is searched for in the paths available in the PATH variable, if the full path to the engine is not already specified.
For this to happen, the engine name should be complete, along with the extension. For example, giving the engine name as 'python.exe' may work if the path to it is added to the agent PATH variable; however, just setting 'python' as the engine will not work in ZCM.
This is different from traditional ZENworks 7 where the name of the executable is enough.
This difference in behaviour is a known issue. Currently, there is no simple fix or workaround to overcome this issue for migrated bundles and the manual change to append the extension to the engine may be the only way out.