Wiki source code of Agentenplaner

Last modified by jklein on 2025/07/24 09:21
Show last authors
1 {{aagon.floatingbox/}}
2
3 The Agent Tasks configure all the scanning and maintenance options for working on the ACMP Clients. Here you can define the intervals at which the scanners should run. You can also change the start conditions and enable/disable settings. The Client Actions can also be used to push individual scanners to the Agent independently of the selected start interval.
4
5 It is possible to create almost any number of Agent scheduler templates with their own start conditions for groups of computers.
6
7 [[Overview of Agent Tasks>>image:Agentenplaner_Übersicht.png||alt="“Overview"]]
8
9 The Agent Tasks templates are divided into two areas: the //Agent Tasks //area and the //Maintenance// area. The //Agent Tasks //area lists the scanners that read the information on the client. The //Maintenance //area lists the scanners that enable the agent configurations. If you have many Clients in use, the settings in the Agent Tasks are particularly relevant to prevent possible overloading of the ACMP Server.
10
11 {{aagon.infobox}}
12 The scanners run serially and can therefore only be executed one after the other and not simultaneously. Please take this into account during your work, as it may cause delays in execution.
13 {{/aagon.infobox}}
14
15 = Scanners and configuration profiles =
16
17 Depending on the operating system family, different scanners and configuration profiles are available in the various agent planner templates. If you do not assign a template you have created yourself via the containers, the standard templates will be used. You can create and configure as many templates as you like; they are assigned to clients via the containers. You can also create client-specific templates that refer back to individual agent planner templates for a single client. Using different templates, you can, for example, map the settings and requirements of mobile devices and fixed workstations in the local network.
18
19 Before making the respective settings, you can see whether it is an active task ([[image:image-20220519131909-1.png]]) or an inactive task ([[image:grafik.png]]).
20
21 === Default - Windows ===
22
23 |**Agent Tasks**|(% style="width:351px" %)**Description**|(% style="width:894px" %)**Special features**
24 |File Scanner|(% style="width:351px" %)Searches your Clients for files(((
25 File types:
26 - .exe
27 - .dll
28 - .sys
29 - .jar
30 )))|(% style="width:894px" %)With the file scanner, it is possible to read software on the clients that has not been installed in the traditional way (e.g., in-house developments). You can then use these in License Management, for example. You can find configuration options for this under [[Settings>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Agent.WebHome]].
31 |Defender Scanner|(% style="width:351px" %)Collects Microsoft Defender scan results and status information
32 \\Examples:
33 - Quarantine information
34 - Signature version and signature age
35 - Event log entries of Defender|(% style="width:894px" %)The Defender Scanner collects various information about the installed Windows Defender. The Defender Scanner is activated when you go through and exit the First Step Wizard from Defender Management. In addition, you can configure which event types are to be inventoried. By default, “Information” is disabled, as the database would otherwise grow unnecessarily due to the large number of event messages.
36 |Hyper-V Scanner|(% style="width:351px" %)Scans your Clients for Hyper-V guests|(% style="width:894px" %)The scanner reads the guests from the Hyper-V host. The distinguishing criterion for unique identification can be set in the [[Settings>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HVirtualisierung"]] menu. Guests can also be excluded via a block list.
37 |Managed Software Scanner|(% style="width:351px" %)Scans your Clients for Managed Software|(% style="width:894px" %)The Managed Software Scanner scans the Managed Software installed on the Client. With the scan function, the ACMP Server determines a possible deficit between the installed and available version that the Client has installed.
38 |Rule Scanner|(% style="width:351px" %)Checks the rules assigned to the Clients|(% style="width:894px" %)With the Rule Scanner, you can find specific files, registry keys, and values on the Client. Please note that searching an entire drive may result in a long execution time for the scanner.
39 |Vulnerability Scanner|(% style="width:351px" %)Scans the client for existing vulnerabilities|(% style="width:894px" %)The Vulnerability Scanner ensures that the vulnerability definition file is updated. The file is used to check whether vulnerabilities exist on the client.
40 |Security Scanner|(% style="width:351px" %)Scans the Windows Security Center|(% style="width:894px" %)The data from the Windows Security Center (“Windows Security”) is read and forwarded to ACMP. Here you can display information on whether the settings, parameters, and antivirus solutions are still up to date.
41 |Software Scanner|(% style="width:351px" %)Scans MSI / Setup software and Store apps and, if necessary, user-specific software|(% style="width:894px" %)The scanner reads the installed software listed under “Control Panel and Programs”. The scan function provides you with detailed information about the software installed on the Clients. Under [[Settings>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Agent.WebHome||anchor="HAgentTask"]] you can specify which elements should be ignored by the software scanner. User-specific software can also be read. Please note that Updates and System components are disabled by default, as this would result in many entries being read for the client.
42 |System Scanner|(% style="width:351px" %)Scans hardware information of the machine
43 \\Examples:
44 - Computer name
45 - Computer domain
46 - Hard disk usage
47 - Network cards
48 - Operating system and BitLocker information|(% style="width:894px" %)This is relevant, for example, if you need to change the computer name during operation and it has not yet been updated in ACMP. The new name would only be recorded and displayed after the system scanner has run.
49 |Windows Updates Scanner|(% style="width:351px" %)Scans the machine for already installed and pending Windows Updates|(% style="width:894px" %)The Windows Update Scanner scans the Clients for already installed and pending Windows Updates.
50 |**Maintenance**|(% style="width:351px" %) |(% style="width:894px" %)
51 |Defender Configuration watch|(% style="width:351px" %)Sets the settings of the Defender configuration on the client and updates them if necessary|(% style="width:894px" %)The Defender Scanner applies the configurations according to the assigned configuration profile or updates them.
52 |Update Jobs & Configuration Profiles|(% style="width:351px" %)Queries the ACMP Server for the jobs assigned to it
53 \\Examples:
54 - Container jobs
55 - Pending pushed jobs|(% style="width:894px" %)During execution, all jobs assigned to the client and [[pending jobs>>doc:ACMP.68.ACMP-Solutions.Jobs.WebHome||anchor="HAusfFChrungenvonJobs"]] are determined. This includes jobs that have been linked via a container, but also those that have been pushed to the client but not yet received. For clients that are in the home office and cannot be reached by the ACMP Server, we recommend using a short interval. This enables timely execution of pushed jobs. BitLocker configurations are also updated.
56
57 === Default - Unix ===
58
59 |**Agent Tasks**|**Description**|**Special features**
60 |Software Scanner|Scans Unix applications|The scanner reads the installed software. The scan function provides you with detailed information about the software installed on the clients.
61 |System Scanner|Scans the operating system and hardware information of the machine (e.g., computer name, domain, hard disk usage, network cards, operating system information)|This is relevant, for example, if you need to change the computer name during operation and it has not yet been updated in ACMP. The new name would only be recorded and displayed after the system scanner has run.
62 |**Maintenance**| |
63 |Job Scanner|Collects information about linked and jobs that are still to be executed. Also executed when the agent starts.|
64
65 = Manage templates =
66
67 The ribbon bar allows you to add templates ([[image:image-20220519131940-3.png]]), rename them ([[image:clock-edit.png||alt="“grafik.png”" height="16" width="16"]]) or delete them ([[image:image-20220519131940-5.png||template.pngalt="“Create" height="“16”" width="16"]]). In the second step, the settings can be transferred from an existing template. You can customize these settings.
68
69 = Start conditions =
70
71 (% id="cke_bm_691951S" style="display:none" %) (%%)If you want to change the start conditions of a scanner in the Agent Tasks, double-click on the desired scan job and a dialog window will open.
72
73 {{aagon.infobox}}
74 There are currently fewer start conditions available for scan and maintenance jobs for the Unix operating system family than for the Windows operating system family.
75 {{/aagon.infobox}}
76
77 |(((
78 [[Start conditions Windows operating system family>>image:Agentenplaner_Startbedingungen Windows.png||alt="“Start" data-xwiki-image-style-alignment="“center”" height="567" width="600"]]
79 )))|(((
80 [[Start conditions for the Unix operating system family>>image:Agentenplaner_Startbedingungen Unix.png||alt="“Start" data-xwiki-image-style-alignment="“center”" height="566" width="600"]]
81 )))
82
83 First, specify whether the task should be active or inactive. Select the //Enabled// checkbox if you want to change the start conditions.
84
85 In addition to the activated start conditions, you can also define the network connection options. The network connection options also allow you to specify whether the scanner takes metered connections into account and therefore does not start the scanner. Then find the desired start condition according to which the scanner or maintenance should be performed.
86
87 The start conditions specify when the job should be executed. For some conditions, you can specify specific dates, while for others you can define specific actions to be performed while working on the service.
88
89 Recurring elements:
90
91 * **Execute only within the time window**: Here you can specify a time window in which the task should be executed. The time window can be specified in hours and minutes.
92
93 {{aagon.versionierungsbox}}
94 Please note that the “Execute once” checkbox is no longer available in ACMP version 6.3 and higher.
95 {{/aagon.versionierungsbox}}
96
97 |**Start condition**|**Explanation**
98 |Login|The condition is executed as soon as a user logs on to the system or terminal server.(((
99 * Example: The user logs on to the computer.
100 )))
101 |Specific time|The condition is executed daily at a specific time that you can specify.
102 |Specific date|You can only run the scanner on a specific date by specifying a date.
103 |Date interval|Dynamically calculated times can be defined during execution.(((
104 * Example: The first day of the month.
105 )))
106 |Shutdown|The start condition is executed when the client is shut down. To do this, the user is first logged off and only then are the jobs executed.(((
107 * Special feature: Commands that run in the user context are not executed (e.g., all commands in the Dialog category, as well as Lock manual input, Unlock manual input, Get idle time, Lock workstation, Get/Set default printer, and If user is (not) in group).
108 )))
109 |Last day of each month (deprecated)|The scanner is executed on the last day of each month.{{aagon.infobox}}This is a deprecated start condition. We recommend that you use the “Date interval” setting instead.{{/aagon.infobox}}
110 |As soon as possible|With this setting, the task is executed as soon as possible.{{aagon.infobox}}This start condition implies a one-time execution!{{/aagon.infobox}}
111 |Start of agent|The execution is performed when the agent starts (manually via the service management or by restarting the machine).(((
112 * Example: The computer is restarted.
113 )))
114 |Start time|Execution begins at the start time you specify. You can also specify a finish date, which means that the data will not be automatically refreshed when that date is reached.
115 |Start interval|Within the start condition, you can define an interval (minutes, hours, days) at which the task should always start. {{aagon.infobox}}The start behavior of random time windows is only available for the interval setting “Days”.{{/aagon.infobox}}
116 |Day of the week|Execution starts when you specify one or more days of the week. There is also the option of including every nth day of a month.
117 |Day of the month|The condition is executed on all days of the month that you specify. The execution is only carried out in months with the selected days.
118 |Time window|A specific time window with a start and end time can be specified.
119
120 Finally, save your changes so that the scanners or maintenance tasks can start under the new start conditions.
121
122 === Special behavior of the start conditions ===
123
124 {{aagon.infobox}}
125 Please note a special behavior for the “Time window” option. If you use this in combination with the start conditions “Day of the week,” “Day of the month,” or “Specific date” and the time window extends beyond one day (e.g., 10:00 p.m. – 2:00 a.m.), the client task would only be executed on that specific date. This also applies if the time window extends into the next day. Therefore, always check the date first and then the time window. For example, if you only want to execute a scanner in the evening, it would run until 11:59 p.m., but not until the actual end of the specified time window.
126 {{/aagon.infobox}}
127
128 {{aagon.infobox}}
129 In the start conditions “Start interval” and “Time window,” there is the option “Start at a random time within the time window.” We recommend that you use this start condition. This ensures that the scan data is sent to the server at different times. If a large amount of scan data is sent at the same time, the import may be delayed.
130 {{/aagon.infobox}}
131
132 = Assigning an agent planner template via containers =
133
134 If you have already created a container, you can also assign an agent planner template to it via the detail view. You can find the currently assigned agent planner template in the category of the same name //Agent Tasks//. This can be changed either via the buttons in the ribbon bar or the context menu.
135
136 Depending on which operating system family the container is assigned to, only agent scheduler templates with the same operating system family can be linked. Also note that the priority determines which template is used by the client. If the client is located in multiple containers, the template from the container with the highest priority is always used. This must be taken into account during assignment and, if necessary, customized in the priority of the container.
137
138 [[Linking an agent planner template in a container>>image:Agentenplaner_Container-Verknüpfung.png||alt="“Linking"]]
139
140 {{aagon.infobox}}
141 When multi tenancy is enabled, global containers have a higher weighting than client containers.
142 {{/aagon.infobox}}
143
144 = Individual agent scheduler template via the Client Details =
145
146 Via the Client Details, you can enable an individual agent template that applies specifically to the selected client. The template has the highest priority and takes precedence over assignments via containers. Navigate to the menu item //Software > Computers > Agent Tasks //in the Client Details and select the //Enable client-specific template// checkbox to make individual changes to the template.
147
148 Once you have activated and configured the template, save the changes and the agent will be taken into account during the next update.
149
150 [[Use client-specific agent scheduler template>>image:Agentenplaner_Clientspezifische Verknüpfung.png||alt="“Use"]]
151
152 = Option to check execution =
153
154 Using the supplied query //ACMP Agent Statuses//, you can check when a scanner last ran and whether the inventoried data has been updated. To do this, click on the small arrow displayed to the left of the client name in the results list of the executed query. This opens the detailed view of the scanner data.
155
156 [[Check execution of scanner jobs>>image:Agentenplaner_Ausführung überprüfen.png||alt="“Check"]]
157
158 = Customize system settings for the Agent Tasks =
159
160 In the system settings, you can configure the settings for the software and file scanner for the Agent Tasks. To do this, navigate to //System// > //Settings// > //ACMP// //Agent// > //Agent// //Task// in the ACMP Console.
161
162 [[Settings for software and file scanners >>image:Einstellungen Scanner.png||alt="“Settings"]]
163
164 {{aagon.infobox}}
165 Please note that updates and system components generate many entries in the database. If this information is not required, we recommend that you leave the default settings unchanged.
166
167 {{/aagon.infobox}}
168
169 {{aagon.infobox}}
170 You can customize the hard disk usage so that you can continue working on the computer during the scan.
171 {{/aagon.infobox}}
© Aagon GmbH 2025
Besuchen Sie unsere Aagon-Community