How to disable the execution of sdagent and amagent during CAF startup?


Article ID: 51216


Updated On:


CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER CA Server Automation CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager



When the CAF service is started (during machine boot or after caf start), the AM and SD Agents are automatically executed. It is possible to avoid this?


AMagent and SDagent are automatically started by Scheduled job "Registration refresh scheduled job" (caf register).
The type of this job is: now day random.
This job is executed at the startup of CAF service because it is of type "now".

Remove the "now" keyword from 'Caf Scheduler: Type of job' configuration policy under:
DSM/common components/CAF/Scheduler/Registration refresh scheduled job

<Please see attached file for image>

Figure 1

Remarks :

  • By default amagent is automatically executed:

    • At startup of caf (registration refresh scheduled job - type now)

    • Every day at 12pm + random of 90 minutes (registration refresh scheduled job - type day random)

    • Every day at 1am + random of 10 minutes (run the UAM agent - type day random)

    • Every hour + random of 10 minutes (Run the UAM agent in USD hint mode) but only software inventory is executed if a new SD job has been installed.

  • By default sdagent is automatically executed:

    • At startup of caf (registration refresh scheduled job - type now)

    • When receiving a SD trigger from the Scalability Server if a SD job must be executed.

  • For some SD packages the SD job is executed in 2 parts because a reboot is necessary during installation: first part, reboot, second part. A rerun signal is set in first phase in order to restart the SD job automatically at the next SD jobcheck. If we remove the "now" keyword from "registration refresh scheduled job", the rerun will not be executed after the reboot and so the second part may be delayed until the next Jobcheck will be triggered by the Scalability Server that keeps trigging the agents while there are still jobs to be executed. The interval to trigger agents with pending jobs is defined by the following configuration policy that by default has value of 600 (10 minutes):

    DSM/Software Delivery/Scalability Server/Job Check: Wait between JobCheck triggers


Release: UASIT.99000-11.2-Asset Intelligence


1558695284039000051216_sktwi1f5rjvs16myc.gif get_app