Changes for page Agentenplaner

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

From 5.1 to 6.1 From 7.1 to 8.1

From version 6.1

edited by Sabrina V.
on 2026/05/21 05:43

Change comment: There is no comment for this version

To version 7.1

edited by Sabrina V.
on 2026/05/21 05:50

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -49,11 +49,12 @@
  - 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
++|Job and Config Scanner|(% 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.69.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.
  === Default - Unix ===
@@ -61,75 +61,24 @@
  |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.|
++|Job and Config 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}}
--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.
++When selecting an existing template, make sure that the operating system family is compatible with the intended use.
  {{/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"]]
--)))
++[[Create an agent planner template>>image:610_Agentenplaner Vorlageneinstellungen_892.png]]
--First, specify whether the task should be active or inactive. Select the //Enabled// checkbox if you want to change the start conditions.
++= Start conditions =
--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.
++To change the start conditions for a scanner in the Agent Tasks, click the desired scan job to open a dialog box.
--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.
++For more information on configuring start conditions and other details, see the [[Start conditions>>doc:ACMP.610.ACMP-Solutions.Jobs.WebHome||anchor="HStartconditions"]] section.
--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.