3.4 Troubleshooting the Remote Execute Policy

An error occurs while executing a given script, binary, or Java program

Source: ZENworks 7.3 Linux Management; Policy Handlers; Remote Execute Policy
Possible Cause: The input parameters given in the policy are incorrect.
Action: If you have not defined your own script:
  1. Combine the inputs for the following fields as one line in the policy:

    InterpreterName InterpreterParameters ProgramName ProgramParameters
    
  2. On the managed device, execute the above statement from the command line.

  3. If there is an error, give the correct parameters for InterpreterName, InterpreterParameters, ProgramName, and ProgramParameters.

If you have defined your Own Script, perform the following:

  1. On the managed device, create a file containing the script you have specified in the policy.

  2. Execute the script file from the command line.

  3. If there is an error, give the correct parameters for InterpreterName, InterpreterParameters, ProgramName, and ProgramParameters.

  4. Copy the correct script to the policy.

Possible Cause: In the Binary or Java executable type, shell or redirection operators are specified in the parameters.
Action: If you want to use shell or redirection operators with a Binary or Java executable, perform the following:
  1. On the Remote Execute policy page, select Script as the Executable type.

  2. In Script to Run field, select Define Your Own Script.

  3. Combine the inputs for the following fields as one line in the policy:

    InterpreterName InterpreterParameters ProgramName ProgramParameters
    

Policy enforcement does not give the status of the launched program

Source: ZENworks 7.3 Linux Management; Policy Handlers; Remote Execute Policy
Possible Cause: The Maximum Waiting Time setting might not have the right value.
Action: On the Remote Execute policy page, in the Maximum Time to Wait field, select Wait Till the Program Completes the Execution.

Unable to install or enforce the available bundle or policy on the managed device according to the schedule when the ZENworks server is inactive

Source: ZENworks 7.3 Linux Management; Policy Handlers; Remote Execute Policy
Explanation: The assigned bundle or policy becomes available on the agent, gets installed at the configured scheduled time. However, during this period, if the ZMD goes to the normal sleep state because of its inactivity, or the ZENworks Linux Management services is down, then the bundle and policy capabilities or services cannot be processed from the inactive ZENworks Linux Management server on refreshing. The scheduled action data for the effective policy or bundle is not available with the agent to process the the required scheduled action.
Action: Ensure that all the ZENworks Linux Management services are active on the ZENworks server and are accessible from the agent.