Changes for page Agentenplaner

Last modified by jklein on 2025/07/24 09:21

From version 1.1

edited by jklein
on 2024/08/13 08:28

Change comment: Imported from XAR

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 (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -1,7 +5,3 @@
--{{aagon.priorisierung}}
--80
--{{/aagon.priorisierung}}
--
  {{aagon.floatingbox/}}
  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.
@@ -8,217 +8,168 @@
  It is possible to create almost any number of Agent scheduler templates with their own start conditions for groups of computers.
--{{figure}}
--(% style="text-align:center" %)
--[[image:63_ClientManagement_Agentenplaner1351.png]]
++[[Overview of Agent Tasks>>image:Agentenplaner_Übersicht.png||alt="“Overview"]]
--{{figureCaption}}
--Agent Tasks
--{{/figureCaption}}
--{{/figure}}
++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.
--The Agent Scheduler is divided into two sections, Agent Tasks and Maintenance. The Agent Tasks section contains the scanners that read information from the Clients. The Maintenance section contains the scanners that enable Agent configurations. If you have many Clients in use, the settings in the Agent Tasks section are particularly important to avoid overloading the ACMP Server.
--
  {{aagon.infobox}}
--The scanners run serially and can only be run one after the other, not simultaneously. Take this into account when working as it may cause delays in execution.
++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.
  {{/aagon.infobox}}
--|**Agent Tasks**|**Description**|**Special Features**
--|Defender Scanner|Collects Microsoft Defender scan results and status information
--\\Examples:
--- Quarantine information
--- Signature version and signature age
--- Event log items of Defender|The Defender Scanner collects various info about the installed Windows Defender. The Defender Scanner is activated when you go through and exit the First Step Wizard of Defender Management. In addition, you can configure which Event types are to be inventoried. By default, "Information" is disabled because the database would otherwise grow unnecessarily due to the many event messages.
--|File Scanner|Searches your Clients for files
--\\File types:
++= Scanners and configuration profiles =
++
++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.
++
++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]]).
++
++=== Default - Windows ===
++
++|**Agent Tasks**|(% style="width:351px" %)**Description**|(% style="width:894px" %)**Special features**
++|File Scanner|(% style="width:351px" %)Searches your Clients for files(((
++File types:
  - .exe
  - .dll
  - .sys
--- .jar|With the file scanner it is possible to read out software on the Clients that has not been installed in the classical way (e.g. in-house developments). You can then use this, for example, in License Management. You will find configuration options for this under the [[settings>>doc:ACMP.65.ACMP-Solutions.System.Einstellungen.ACMP Agent.WebHome||anchor="HACMPTask"]].
--|Hyper-V Scanner|Scans your Clients for Hyper-V Guests|With the help of the scanner, the guests are read from the Hyper-V host. The difference criterion for unique identification can be made in the settings (Verlinkung). In addition, guests can be excluded via a block list.
--|Managed Software Scanner|Scans your Clients for Managed Software|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 version and the available version that the Client has installed.
--|Rule Scanner|Checks the rules assigned to the Clients|You can use the Rule Scanner to find specific files, registry keys and values on the Client. Please note that a search of an entire drive may take a long time for the scanner to complete.
--|Security Scanner|Scans the Windows Security Center|The data of the Windows Security Center ("Windows Security") is read out and passed on to ACMP. Here you can display the info as to whether the settings, parameters and antivirus solutions are still up to date.
--|Software Scanner|Scans MSI / setup software and store apps and, if required, user-specific software|The scanner reads out the installed software listed under "Control Panel and Programs". The scan function gives you exact details about what software is installed on the Clients. You can specify under the [[settings >>doc:ACMP.65.ACMP-Solutions.System.Einstellungen.ACMP Agent.WebHome||anchor="HACMPTask"]]which items are to be ignored by the software scanner. User-specific software can also be read out. Note that Updates and System Components are disabled by default, as this would cause many items to be read out for the Clients.
--|System Scanner|Scans hardware information of the machine
++- .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.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.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.
++|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.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
  - Computer domain
--- Hard disk allocation
--- Network cards|This is relevant, for example, if you 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 computer scanner has run through.
--|Vulnerability Scanner|Scans the Client for existing vulnerabilities|The vulnerability scanner updates the vulnerability definition file. The file is used to check whether vulnerabilities exist on the Client.
--|Windows Updates Scanner|Scans already installed and pending Windows Updates of the machine|The Windows Update Scanner scans the Clients for already installed and pending Windows Updates.
--|**Maintenance**| |
--|ACMP Agent Update/installation time frame|Agents are allowed to install ACMP Updates during this time window.|The time window can be used to configure when an Update can be installed for the Agent.
--| | |
--
--{{aagon.infobox}}
--We recommend that you do not change this setting, as the default setting guarantees a 24/7 update/installation window and an incorrect configuration may prevent an update and thus disrupt the communication between the ACMP Server and the ACMP Agent. Please note that the Agent update can also be performed during normal business hours without any problems.
--{{/aagon.infobox}}
--
--|Restart ACMP Agent|Restarts the ACMP Agent|This maintenance option allows you to restart the ACMP client service. Also note that this job triggers the start condition "ACMP Agent Start".
--|Settings Watch|Updates the Client Task Settings for the Client|Updates the scan intervals of the Agent Tasks and the file repositories. If you change the conditions of the scanners in the Agent Tasks (e.g. the conditions of a point in time), the settings are updated after the defined interval.
--|Update Defender Configuration Profiles|Sets the settings of the Defender Configuration on the Clients and updates them if necessary.|The Defender Scanner applies or updates the configurations according to assigned configuration profiles.
--|Update Jobs & Configuration Profiles|(((
--Queries the ACMP Server for the Jobs unassigned to it.
++- Hard disk usage
++- Network cards
++- 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" %)
++|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
--)))|During the execution of the Job Scanner, all Jobs assigned to the Client and pending are determined. This includes the 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 prompt execution of pushed Jobs.
++- Container jobs
++- 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.
--In front of each setting you can see whether it is an active task ([[image:image-20220519131909-1.png]]) or an inactive task ([[image:grafik.png]]).
++=== Default - Unix ===
--ACMP comes with a default template. If you do not assign a custom template via the container, the default template will be used. You can create and configure as many templates as you like; the assignments to Clients are made via the Containers. You can also create Client-specific templates that are based on individual Agent Scheduler templates for a single Client. For example, you can use different templates to map the settings and requirements of mobile devices and fixed workspaces on the local network.
++|**Agent Tasks**|**Description**|**Special features**
++|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 Scanner|Collects information about linked and  jobs that are still to be executed. Also executed when the agent starts.|
--To switch between different templates, you can use the pull-down menu and select the required template.
++= Manage templates =
--= Manage templaes =
++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.
--The ribbon bar allows you to add ([[image:image-20220519131940-3.png]]), rename ([[image:clock-edit.png||alt="grafik.png" height="16" width="16"]]) or delete ([[image:image-20220519131940-5.png||height="16" width="16"]]) templates. Settings can be taken from a template to be selected.
++= Start conditions =
--{{figure}}
--(% style="text-align:center" %)
--[[image:ACMP_63_Agentenplaner_Vorlage_erstellen_%971.PNG]]
++(% 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.
--{{figureCaption}}
--Create a new template
--{{/figureCaption}}
--{{/figure}}
++{{aagon.infobox}}
++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}}
++|(((
++[[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"]]
++)))
--== Configururing templates ==
++First, specify whether the task should be active or inactive. Select the //Enabled// checkbox if you want to change the start conditions.
--If you want to change the settings of the different start conditions in the Agent Tasks, double-click on the desired job and a dialogue window opens.
++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.
--{{figure}}
--(% style="text-align:center" %)
--[[image:ACMP_63_Agentenplaner_Einstellungen_ändern_%820.PNG]]
++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.
--{{figureCaption}}
--Start condition
--{{/figureCaption}}
--{{/figure}}
--
--= Start conditions =
--
--First specify whether the task should be active or inactive. Check the //Activated// checkbox if you want to change the start conditions.
--
--In addition to the activated start conditions, you can also define the network connection options. Using the network connection options, you can also define whether the scanner should take metered connections into account and therefore not start the scanner. Next, find the start condition you want the scanner or maintenance to follow.
--
--The start conditions specify when the job is to be executed. For some conditions you can specify specific dates, for others you can define the specific actions while working on the service.
--
  Recurring elements:
--* **Execute only within the time window**: Here you can define a self-specified time window in which the task is to be carried out. The time window allows you to specify both hours and minutes.
++* **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 checkbox "Execute once" is no longer available in ACMP from version 6.3.
++Please note that the “Execute once” checkbox is no longer available in ACMP version 6.3 and higher.
  {{/aagon.versionierungsbox}}
  |**Start condition**|**Explanation**
--|ACMP Agent start|- Executions are executed when the ACMP Agent is started (manually via service management or restarting the machine).
--\\- The condition is also executed via the maintenance option "Restart ACMP Agent".(((
--* Example: The cumputer is restarted.
++|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.
  )))
--|As soon as possible|- With the settings, the task is executed as soon as possible.
--- Note that this start condition implies a single execution!
--|Date interval|- Dynamically calculated times can be defined during execution.(((
++|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.
  )))
--|Day of month|- The condition is executed on all the days you specify in the month. Executions are only executed in months with the selected days.
--|Day of week|- Executions are started when you specify one or more days of the week. In addition, there is the option that every nth day of a month should be taken into account.
--|Last day of every month (deprecated)|- The scanner is executed on the last day of each month.
--Please note that this is a deprecated start condition. We recommend that you use the "Date inverval" setting instead.
--|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.
++|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).
  )))
--|Shut down|- The start condition is executed when the Client is shut down. For this purpose, 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 of the category Dialogs, 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.
  )))
--|Specific date|- You can only run the scanner on a specific date by specifying a date.
--|Specific time|- The condition is executed daily at a specific time that you can set.
--|Start interval|- Within the start condition you can define an interval (minutes, hours, days) when the task should always start.
--- Note that the start behavior of random time windows is only available with the interval setting "days"
--|Start time|- Executions begin with the start date, which you can specify. You can also specify a finish date, which means that there is no automatic refresh of the data when the date is reached.
--|Time frame|- A specific time slot with a start and end time can be set.
++|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. Note that the start conditions are updated on the Client when the scanner has run through "Update settings".
++Finally, save your changes so that the scanners or maintenance tasks can start under the new start conditions.
--== Special behaviour of the start conditions ==
++=== Special behavior of the start conditions ===
  {{aagon.infobox}}
--Please note a special behaviour for the "Time Window" option. If you use this in combination with the start conditions "Day of week", "Day of month" or "Specific date" and the time window extends beyond one day (e.g. 22:00 - 02:00), the Client Task would only be executed on this specific date. This also applies if the time window still extends into the next day. Therefore, always check the date first and only then the time window. For example, if you want to execute a scanner only in the evening, it would run until 23:59, but not until the actual end of the specified time window.
++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 frame" 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 a staggered time. If many scan data are sent at the same time, the import may only be carried out with a time delay.
++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 =
--= Assigning an Agent Scheduler template from a Container =
++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.
--If you have already created a container, you can also assign an Agent Scheduler template to it from the details view. You can find the currently assigned Agent Scheduler template via the //Agent Tasks// category of the same name. This can be changed using either the ribbon buttons or the context menu.
++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.
--Note that priority determines which template is used by the Client. If the Client is in more than one Container, the template from the Container with the highest priority will always be used. This has to be taken into account when assigning and, if necessary, adjusted in the priority of the container.
++[[Linking an agent planner template in a container>>image:Agentenplaner_Container-Verknüpfung.png||alt="“Linking"]]
--{{figure}}
--(% style="text-align:center" %)
--[[image:ACMP_63_Agentenplaner_Container_%.PNG]]
--
--{{figureCaption}}
--Unassigned Agent Planner Template
--{{/figureCaption}}
--{{/figure}}
--
  {{aagon.infobox}}
--When Multi-Tenancy is enabled, the Global Containers have a higher weighting than the Client Containers.
++When multi tenancy is enabled, global containers have a higher weighting than client containers.
  {{/aagon.infobox}}
--= Individual Agent Planer Template via the Client Details =
++= Individual agent scheduler template via the Client Details =
--Via the Client Details, you can enable an individual agent template that specifically applies only to the selected Client. The template has the highest priority and takes effect before assignments via containers. Navigate to the //Software// > //Computer// > //Agent// //Tasks// menu item under the Client Details and check the Enable //Client-Specific Template// checkbox to make individual changes to the template.
++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.
--Once you have enabled the template and configured it appropriately, save the changes and the agent will reflect the custom agent scheduler template after the "Update Settings" scanner is executed.
++Once you have activated and configured the template, save the changes and the agent will be taken into account during the next update.
--{{figure}}
--(% style="text-align:center" %)
--[[image:ACMP_63_Agentenplaner_Client_Details_%.PNG]]
++[[Use client-specific agent scheduler template>>image:Agentenplaner_Clientspezifische Verknüpfung.png||alt="“Use"]]
--{{figureCaption}}
--Client specific template
--{{/figureCaption}}
--{{/figure}}
++= Option to check execution =
--= Ability to check Executions =
++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.
--Using the "ACMP Agent Statuses" Query, you can check when a scanner last ran and whether the inventoried data has been updated.
++[[Check execution of scanner jobs>>image:Agentenplaner_Ausführung überprüfen.png||alt="“Check"]]
--{{figure}}
--(% style="text-align:center" %)
--[[image:ACMP Agent Statuses.PNG]]
++= Customize system settings for the Agent Tasks =
--{{figureCaption}}
--ACMP Agent Statuses
--{{/figureCaption}}
--{{/figure}}
++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.
--= Customize System Settings for Agent Tasks =
++[[Settings for software and file scanners >>image:Einstellungen Scanner.png||alt="“Settings"]]
--In the System Settings you can adjust the settings for the software and file scanner for the Agent Tasks. To do this, navigate in the ACMP Console to //System// > //Settings// > //ACMP// //Agent// > //Agent// //Task//.
--
--{{figure}}
--(% style="text-align:center" %)
--[[image:63_SystemEinstellungen_ACMPTask_Scanner_748.png]]
--
--{{figureCaption}}
--Scanner settings
--{{/figureCaption}}
--{{/figure}}
--
  {{aagon.infobox}}
--Please note that Updates and System Components create many items in the database. Unless this information is needed, we recommend that you leave the default configurations set.
++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.
++
  {{/aagon.infobox}}
  {{aagon.infobox}}
--You can customize the hard disk usage to allow the computer to continue working during the scan.
++You can customize the hard disk usage so that you can continue working on the computer during the scan.
  {{/aagon.infobox}}