Changes for page Agentenplaner

Last modified by Sabrina V. on 2026/06/09 09:06

From 4.1 to 3.1

From version 8.1

edited by Sabrina V.
on 2026/06/09 09:06

Change comment: There is no comment for this version

To version 4.1

edited by jklein
on 2025/07/24 09:21

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.SV
++XWiki.jklein

Content

@@ -4,7 +4,7 @@
  It is possible to create almost any number of Agent scheduler templates with their own start conditions for groups of computers.
--[[Overview of Agent Tasks>>image:610_Agentenplaner Übersicht_1622.png||alt="“Overview"]]
++[[Overview of Agent Tasks>>image:Agentenplaner_Übersicht.png||alt="“Overview"]]
  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.
@@ -27,19 +27,18 @@
  - .dll
  - .sys
  - .jar
--)))|(% 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.610.ACMP-Solutions.System.Einstellungen.ACMP Agent.WebHome]].
++)))|(% 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]].
  |Defender Scanner|(% style="width:351px" %)Collects Microsoft Defender scan results and status information
  \\Examples:
  - Quarantine information
  - Signature version and signature age
  - 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.
--|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.610.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HVirtualisierung"]] menu. Guests can also be excluded via a block list.
++|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.
  |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.
--|Optional Features Scanner|The scanner checks your Clients for optional Windows features that are activated on the system.|The scanner checks only for features that are actually present and have already been installed.
  |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.
  |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.
  |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.
--|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.610.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.
++|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.
  |System Scanner|(% style="width:351px" %)Scans hardware information of the machine
  \\Examples:
  - Computer name
@@ -49,12 +49,11 @@
  - 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.
  |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.
  |**Maintenance**|(% style="width:351px" %) |(% style="width:894px" %)
--|Job and Config Scanner|(% style="width:351px" %)Queries the ACMP Server for the jobs assigned to it
++|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.
++|Update Jobs & Configuration Profiles|(% style="width:351px" %)Queries the ACMP Server for the jobs assigned to it
  \\Examples:
  - Container jobs
--- Pending pushed jobs|(% style="width:894px" %)During execution, all jobs assigned to the client and [[pending jobs>>doc:ACMP.610.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.
--|Update BitLocker Configuration Profiles|(% style="width:351px" %)Applies BlitLocker Configuration Profiles|(% style="width:894px" %)Will also be executed at Agent start.
--|Update Defender Configuration Profiles|Sets the settings of the Defender configuration on the client and updates them if necessary|The Defender Scanner applies the configurations according to the assigned configuration profile or updates them.
++- 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.
  === Default - Unix ===
@@ -62,24 +62,75 @@
  |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.
  |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.
  |**Maintenance**| |
--|Job and Config Scanner|Collects information about linked and  jobs that are still to be executed. Also executed when the agent starts.|
++|Job Scanner|Collects information about linked and  jobs that are still to be executed. Also executed when the agent starts.|
  = Manage templates =
  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.
++= Start conditions =
++
++(% 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.
++
  {{aagon.infobox}}
--When selecting an existing template, make sure that the operating system family is compatible with the intended use.
++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.
  {{/aagon.infobox}}
--[[Create an agent planner template>>image:610_Agentenplaner Vorlageneinstellungen_892.png]]
++|(((
++[[Start conditions Windows operating system family>>image:Agentenplaner_Startbedingungen Windows.png||alt="“Start" data-xwiki-image-style-alignment="“center”" height="567" width="600"]]
++)))|(((
++[[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"]]
++)))
--= Start conditions =
++First, specify whether the task should be active or inactive. Select the //Enabled// checkbox if you want to change the start conditions.
--To change the start conditions for a scanner in the Agent Tasks, click the desired scan job to open a dialog box.
++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.
--For more information on configuring start conditions and other details, see the [[Start conditions>>doc:ACMP.610.ACMP-Solutions.Jobs.WebHome||anchor="HStartconditions"]] section.
++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.
++Recurring elements:
++
++* **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.
++
++{{aagon.versionierungsbox}}
++Please note that the “Execute once” checkbox is no longer available in ACMP version 6.3 and higher.
++{{/aagon.versionierungsbox}}
++
++|**Start condition**|**Explanation**
++|Login|The condition is executed as soon as a user logs on to the system or terminal server.(((
++* Example: The user logs on to the computer.
++)))
++|Specific time|The condition is executed daily at a specific time that you can specify.
++|Specific date|You can only run the scanner on a specific date by specifying a date.
++|Date interval|Dynamically calculated times can be defined during execution.(((
++* Example: The first day of the month.
++)))
++|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.(((
++* 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).
++)))
++|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}}
++|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}}
++|Start of agent|The execution is performed when the agent starts (manually via the service management or by restarting the machine).(((
++* Example: The computer is restarted.
++)))
++|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.
++|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}}
++|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.
++|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.
++|Time window|A specific time window with a start and end time can be specified.
++
++Finally, save your changes so that the scanners or maintenance tasks can start under the new start conditions.
++
++=== Special behavior of the start conditions ===
++
++{{aagon.infobox}}
++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.
++{{/aagon.infobox}}
++
++{{aagon.infobox}}
++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.
++{{/aagon.infobox}}
++
  = Assigning an agent planner template via containers =
  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.
@@ -86,7 +86,7 @@
  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.
--[[Linking an agent planner template in a container>>image:610_Container Agentenplaner Ansicht_1713.png||alt="“Linking"]]
++[[Linking an agent planner template in a container>>image:Agentenplaner_Container-Verknüpfung.png||alt="“Linking"]]
  {{aagon.infobox}}
  When multi tenancy is enabled, global containers have a higher weighting than client containers.