How to configure the DSM Asset Management Agent plugin and Collect Tasks scheduling?

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

Description:

The frequency in which the agent collects the inventory data may need to be adjusted from its default of once per day to more often or less often.

How can this be configured?

Solution:

There are two parameters to review when managing the execution schedule of the collect tasks invoked by the Asset Management Agent plug-in:

  • The scheduling of the Asset Management Agent plug-in itself.

  • The particular scheduling of each Collect Task it invokes during its execution.
  1. The scheduling of the Asset Management Agent plug-in is configurable through the DSM configuration policies.

    It can be accessed from within DSM Explorer under Control panel > Configuration > Configuration Policy > Default Computer Policy > DSM > common components > CAF > Scheduler > Run the UAM agent as shown in the image.

    Figure 1

    By default, it runs once a day. When it runs, it uploads the inventory data to the sector where it is picked up by the engine scalability collect job and stored into the MDB.

    So, if you stick to the default, the inventory data for an asset should not be older than one day.

  2. The scheduling of the Collect Task (or tasks) the DSM Asset Management Agent plugin runs.

    It can be accessed from within DSM Explorer under All Computers > {Group details}> Configuration > Collect Tasks. Then in the right pane right click the Collect Task (or any other collect ask) and select Scheduling.

    Figure 2

    In the Scheduling tab and in the Conditions tab is where you can specify how often that particular task needs to be executed.

    Figure 3

    Figure 4

    For instance, specifying via configuration policy that the Asset Management Agent plug-in needs to run 4 times a day but the scheduling of a particular collect task is restricted to once a day, then the Asset Management Agent plug-in will run 4 times but only one time the collect task will be invoked. The other 3 times it will be skipped.