I deliver a software package to some client PCs, and some are switched off. How do I have to configure the package (or the agent, or ?), so it will retry the delivery when the PCs are getting switched on? How many times will it retry?

Document ID : KB000025344
Last Modified Date : 14/02/2018
Show Technical Document Details

Question: 

I deliver a software package to some client PCs, and some are switched off. How do I have to configure the package (or the agent, or ?), so it will retry the delivery when the PCs are getting switched on? How many times will it retry?

 

Environment:                                          

CA Client Automation - All Versions

 

Answer: 

When you create a Job Container, the Setup Job window will allow you to specify the Job Timeout on the Job > Job Options tab.

At the bottom of the window you can specify the Job Timeout in days and hours.

The allowed values of this option is managed by the following configuration policies under DSM > software delivery > Manager:

  • Software job options: Minimum activation time

    This is the minimum number of hours you can set for the give-up time of an Item Procedure in the Job Options dialog when setting up a job.

    The default is 3.

  • Software job options: Maximum activation time

    This is the maximum number of hours you can set for the give-up time of an Item Procedure in the Job Options dialog when setting up a job.

    The default is 168 (7days).

When a package is Staged, the Scalability server will trigger the Agent every 10 minutes sending Wake-on-Lan packets (Unicast and broadcast by default as defined on the configuration policies under DSM > common components > CAF > Wake-on-Lan) and also try to establish a connection with the Agent.

The interval to trigger the Agent is defined by the following configuration policy under DSM > software delivery > Scalability Server:

  • Jobcheck: Wait between JobCheck triggers

    The time to wait until triggering a not responding agent again, measured in seconds. If a job has not started within this time, the jobcheck at the agent is triggered again to contact the server and start the job.

    The default is 600 (10 minutes).