Patch for Windows, powered by Shavlik

Creating a New Asset Task

An asset task is used to define how and when the target machines will be scanned to determine their software and hardware assets. If you do not create an asset task, then no asset scanning will be performed by agents that are assigned this policy. For background information about the asset management feature, see Asset Management Overview.

You can create multiple asset tasks for one agent policy. Each task can be expanded and collapsed using the Hide/Show triangle () that resides on the task title bar. This enables you to view just the task you are working on at any one time.

While there is no theoretical limit to the number of asset tasks you can create for an agent policy, there is a practical limit.  For example, it may become difficult to track and manage a policy if it contains too many asset tasks.

You configure agent asset tasks on the Asset tab. You can edit an existing asset task, or you can create a new task by clicking Add an Asset Task. Be sure to give the task a descriptive name because this is the name the users will see from within the client program. The results of an agent-based asset scan are reported to the console and viewable using Machine View.

 

Asset Scan Template

You must specify the template to use when an agent performs an asset scan. The asset scan template dictates exactly what will be scanned for and what will be ignored during a scan. The list of templates available for selection will include the predefined template (Full Asset Scan) plus any custom templates you've already defined. You can also do the following:

New: Enables you to create a new asset scan template from scratch.

Edit: Enables you to edit an existing, custom asset scan template. The predefined template cannot be edited. If you edit and save a template that is currently being used by an agent policy, the agents using that policy will be updated the next time they check in with the console.

If you click New or Edit, the Asset Scan Template dialog is displayed. See Creating a New Asset Scan Template for details on configuring the template.

Schedule Area

The asset schedule specifies how often the task will run on a target machine. It allows you to regularly run the task at a specific time or using a specified recurrence pattern. A built-in scheduler will be provided for each agent. The scheduler will check for new asset data immediately before starting a scheduled asset task.

The agent scheduler will serialize executions of the same agent engine.  For example, if you define a policy with two asset tasks that both start at 1:00 AM, they will not both start at 1:00; rather, they will be serialized (run back-to-back). If you have an asset task and a patch task both scheduled for 1:00 AM, however, they will both be started at 1:00 AM as they use different agent engines.

Use schedule

If enabled, the task will run on agent machines on a recurring basis according to the schedule settings. If not enabled, the schedule settings are ignored and the task must be started manually either from the console or on the agent machine.

Hourly

 

Allows you to schedule the task to be run on an hourly basis.

Run every hh hours: You can specify exactly how many hours there should be between scans. Valid values are from 1 - 100 hours.

Starting at this time: The first scan will begin at the specified time. Subsequent scans will be performed at the interval specified on Run every hh hours.

Daily

 

Indicates that the task will be run on the specified days, at the time of your choosing. For example, using this option a scan could be run every night at midnight, or every Saturday at 9:00 pm, or at 1:00 am the first Sunday of every month, etc.

You can also use the Daily option to schedule a task in conjunction with a regular monthly event such as Microsoft's Patch Tuesday. For example, you might schedule a monthly asset scan to occur the day after Patch Tuesday by specifying The Second Tuesday and then using the Add delay (days) option to delay the task by one day.

Randomize scheduled time (minutes)

Staggers the exact time the task will be performed so as not to overtax the console or designated distribution server with simultaneous requests to download data files, engine components, etc.

Run on boot if schedule missed

If a scheduled task is missed while a target machine is powered off, this option enables you to force the task to automatically run whenever the machine is restarted. The task will run immediately unless you enable the Delay after boot (minutes) check box, in which case the execution will be delayed by the specified number of minutes.

Save and update Agents

Saves all changes to the policy file and stores it on the console. Also updates any agent machines that are currently assigned this policy as follows:

If an agent machine is online and configured to listen for policy updates, the updated policy will be pushed out to that machine immediately.

If an agent machine is online but is not configured to listen for policy updates, the updated policy will be pushed out the next time the agent checks in with the console.

If an agent machine is not currently online, the updated policy will be pushed out the next time the agent checks in with the console.

The Agent Policy Editor will be closed.

Cancel

Indicates you want to exit the Agent Policy Editor without saving your most recent changes. A "Do you want to save your changes?" prompt will appear that gives you a second chance to save your changes. If you click Yes the policy will be saved and the associated agents updated (the same as Save and Update Agents).  If you click No the Agent Policy Editor will be closed without saving your changes.


Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other