Using .CMD file as an "executable" passes batch file path as first parameter

  • 7010349
  • 02-Jul-2012
  • 10-Jun-2013

Environment

Novell ZENworks Configuration Management 11.1 Bundles
Novell ZENworks Configuration Management 11.2 Bundles

Situation

If a bundle contains a "Launch Executable" action, where a .CMD file is specified as the executable, the first parameter (%1) used in the .CMD may contain the path to the .CMD file, and the first parameter passed to the .CMD file is actually %2

Resolution

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

Additional Information

The problem is always seen if the name of the .CMD file is longer than 8 characters, but may also happen if the path is all in lower-case (e.g., "c:\mycmd.cmd")

Feedback service temporarily unavailable. For content questions or problems, please contact Support.