Changes for page Jobs

Last modified by Sabrina V. on 2026/08/10 04:39

From 7.1 to 6.1

From version 18.1

edited by Sabrina V.
on 2026/08/10 04:39

Change comment: There is no comment for this version

To version 7.1

edited by jklein
on 2025/07/24 06:56

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

@@ -2,7 +2,7 @@
  Job Management allows you to manage tasks for clients and the server efficiently.
--Jobs can be used to distribute one-time or recurring tasks to manageable clients via the server. A job basically consists of two parts: the task itself and the start condition. Jobs can be created and executed individually or in a [[(% style="color:#3173b5" %)Job Collection>>doc:ACMP.610.ACMP-Solutions.Jobs.Job Collections.WebHome]](%%).
++Jobs can be used to distribute one-time or recurring tasks to manageable clients via the server. A job basically consists of two parts: the task itself and the start condition. Jobs can be created and executed individually or in a [[(% style="color:#3173b5" %)Job Collection>>doc:ACMP.68.ACMP-Solutions.Jobs.Job Collections.WebHome]](%%).
  {{aagon.infobox}}
  Jobs can only be executed on managed Clients, regardless of the operating system family. These Clients are marked aClient Commandordingly with the Client icons. [[image:Ico_ClientTypeService.png||height="24" width="24"]] [[image:Ico_ClientType_Linux_Managed.png||height="24" width="24"]][[image:Ico_ClientType_MacOs_Managed.png||height="24" width="24"]].
@@ -21,7 +21,7 @@
  For Unix jobs, you can currently only execute Unix scripts as jobs.
  {{aagon.infobox}}
--Please note that a working SICS connection is required to execute Unix jobs. For more info, see the section [[Unix Scripts>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Unix Scripts.WebHome]].
++Please note that a working SICS connection is required to execute Unix jobs. For more info, see the section __[[Unix Scripts>>doc:ACMP.68.ACMP-Solutions.Desktop Automation.Unix Scripts.WebHome]]__.
  {{/aagon.infobox}}
  = Execution of jobs =
@@ -62,7 +62,7 @@
  Jobs or job collections can be added to containers in the Container module:
 . In the ACMP Console navigation, navigate to //Client Management > Container.//
--1. Select an existing container. If you have not yet created a container, first read the section [[Creating a container>>doc:ACMP.610.ACMP-Solutions.Client-Management.Container.Container verwalten.WebHome||anchor="HCreatecontainer"]].
++1. Select an existing container. If you have not yet created a container, first read the section [[Creating a container>>doc:ACMP.68.ACMP-Solutions.Client-Management.Container.Container verwalten.WebHome||anchor="HContainererstellen"]]..
 . In the detail view of the container, click on the //Jobs// tab.
 . In the ribbon bar in the //Jobs// area, click on the //Add// button.
 . A wizard opens in which you can select the type of job (Client Command, Job Collections, Managed Software, Windows Update Collections or Unix Scripts).
@@ -117,23 +117,6 @@
  //Always save advanced log//
  )))|The advanced log is always saved, regardless of whether an error occurred during job execution or not.
--**//Actions//**
--
--These settings allow you to decide which action is applied when the Client Command is executed:
--
--|(% style="width:223px" %)//Install//|(% style="width:1216px" %)The software should be installed.
--|(% style="width:223px" %)//Uninstall//|(% style="width:1216px" %)The software should be uninstalled.
--|(% style="width:223px" %)//Repair//|(% style="width:1216px" %)The software should be repaired in case of a defect.
--|(% style="width:223px" %)//Park//|(% style="width:1216px" %)The software is copied and stored on the client in advance, but not installed. {{aagon.infobox}}The storage location is defined individually in the registry under HKLM\SOFTWARE\Aagon\ACMP, via the 'SoftwareDownloadPath' value. If nothing is entered, ACMP will use the automatic default path: C:\ProgramData\Downloads\<project ID>.{{/aagon.infobox}}
--|(% style="width:223px" %)//Unpark//|(% style="width:1216px" %)The software is removed from the client on which it was previously stored.
--
--(% class="box infomessage" %)
--(((
--[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt="“Note”" height="32" width="32"]] **Note: **
--
--These actions are only available for client commands that were generated independently or via the Package Wizard.
--)))
--
  == **Set parameters for Managed Software jobs** ==
  If you want to execute a Managed Software job, you must also add parameters to this job. Each software package has individual parameters that you can customize. The individual parameters only apply to the corresponding software package and are applied to all available versions.
@@ -185,55 +185,43 @@
  The start conditions //Specific time//, //As soon as possible// and //Start interval// cannot be set for jobs that should be executed once.
  {{/aagon.infobox}}
--{{aagon.versionierungsbox}}
--Please note that some start conditions include the option "One-time execution". In this case, the job is only executed once per client. This information is stored locally on the client. If the client drops out of the container and is reassigned, the job will not be executed again! An exception to this are Client Commands with an [[increased level>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Client Commands.Client Command erstellen.Client Commands neu hinzufügen.Client Command Editor.Menüleiste.Client Command Eigenschaften .WebHome||anchor="HGeneral"]]; these are executed again once.
--{{/aagon.versionierungsbox}}
--
--
--
--|(% style="width:201px" %)**Start condition**|(% style="width:1491px" %)**Explanation**
--|(% style="width:201px" %)As soon as possible|(% style="width:1491px" %)With these settings, the task will be executed as soon as possible.{{aagon.infobox}}Please note that this start condition implies a one-time execution!{{/aagon.infobox}}
--|(% style="width:201px" %)At a specific time|(% style="width:1491px" %)The condition is executed daily at a specific time that you can set.
--|(% style="width:201px" %)At a specified start time|(% style="width:1491px" %)Execution begins at the start time, which you can specify. You can also set a finish date; once that date is reached, the data will no longer be subject to auto refresh.
--|(% style="width:201px" %)During shutdown|(% style="width:1491px" %)The start condition is executed when the client is shut down. To do this, the user is first logged out, and only then are the jobs executed.(((
--* Note: Commands that run in the user context are not executed (e.g., all commands in the Dialogs 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).
++|**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.
  )))
--|(% style="width:201px" %)On a specific date|(% style="width:1491px" %)You can run the scanner only on a specific date by specifying a date.
--|(% style="width:201px" %)On specific days of a month|(% style="width:1491px" %)The condition will be executed on all the days you specify each month. The execution will only be performed in months that include the selected days.
--|(% style="width:201px" %)On specific days of a week|(% style="width:1491px" %)The execution will run if you specify one or more days of the week. You also have the option to include every nth day of the month.
--|(% style="width:201px" %)On the last day of every month (deprecated)|(% style="width:1491px" %)The scan is executed on the last day of each month. {{aagon.infobox}}Please be aware that this is a deprecated start condition. Instead, we recommend using the “date interval” setting.{{/aagon.infobox}}
--|(% style="width:201px" %)Upon Agent start|(% style="width:1491px" %)(((
--The execution is performed when the agent starts (either manually via the Services management console or when the machine is restarted).
--
--* Example: The machine is restarted.
++|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 for execution.(((
++* Example: The first day of the month.
  )))
--|(% style="width:201px" %)Upon user login|(% style="width:1491px" %)(((
--The condition is executed as soon as a user logs on to the system or terminal server.
++|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 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}}Please note that this is a deprecated start condition. We recommend that you use the “Date interval” setting instead.{{/aagon.infobox}}
++|As soon as possible|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 ACMP Agent is started (manually via the service management or by restarting the machine).
--* Example: The user logs on to the computer.
++* Example: The computer is restarted.
  )))
--|(% style="width:201px" %)Within a date range|(% style="width:1491px" %)When executing the process, dynamically calculated dates can be defined.  Example: The first day of the month.
--|(% style="width:201px" %)Within a start interval|(% style="width:1491px" %)In the start condition, you can define an interval (minutes, hours, days) specifying when the task should always begin.{{aagon.infobox}}Please note that the start behavior for random time windows is only available when the interval is set to “days.”{{/aagon.infobox}}
--|(% style="width:201px" %)Within a time frame|(% style="width:1491px" %)You can specify a specific time window with a start and end time.
--|(% style="width:201px" %)Within Maintenance Windows|(% style="width:1491px" %)Jobs with this start condition are executed at the beginning of a maintenance window.
++|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 is started 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 start conditions** ==
++== **Besonderes Verhalten der Startbedingungen** ==
  {{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.
++Bitte beachten Sie ein besonderes Verhalten bei der Option „Zeitfenster“. Sollten Sie dieses in Kombination mit den Startbedingungen „Tag der Woche“, „Tag des Monats“ oder „Bestimmtes Datum“ verwenden und sich das Zeitfenster über einen Tag hinausstreckt (z.B. 22:00 Uhr – 02:00 Uhr), so würde der Client Task nur an diesem bestimmten Datum ausgeführt. Dies gilt auch dann, wenn das Zeitfenster sich noch bis in den nächsten Tag erstreckt. Überprüfen Sie deshalb zunächst immer das Datum und erst anschließend das Zeitfenster. Wenn Sie also beispielsweise einen Scanner nur abends ausführen wollen, würde dieser bis 23:59 Uhr laufen, aber nicht bis zum eigentlichen Ende des festgelegten Zeitfensters.
  {{/aagon.infobox}}
  {{aagon.infobox}}
--Within the ‘Within a time period’ option, you can also select the ‘Check start condition before execution’ setting. This option ensures that a job’s start condition is checked again immediately before it is executed. The client monitors the start conditions of all known jobs. As soon as the defined start condition is met, the relevant job is added to the execution queue.
--However, the actual execution of the job may be delayed, for example due to jobs already running or other system activities. If the situation changes during the waiting period such that the original start condition is no longer met before the actual execution, the job will not be executed if this option is activated.
++In den Startbedingungen „Startintervall“ und „Zeitfenster“ gibt es die Option „An einem zufälligen Zeitpunkt innerhalb des Zeitfensters starten“. Wir empfehlen Ihnen diese Startbedingung zu nutzen. Dadurch wird gewährleistet, dass die Scan-Daten zeitlich versetzt zum Server gesendet werden. Bei vielen gleichzeitig gesendeten Scan-Daten kann der Import unter Umständen nur zeitverzögert durchgeführt werden.
  {{/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}}
--
  == Processing combined start conditions ==
  Depending on which start condition you have selected, it is possible to combine several conditions. These start conditions are evaluated and processed one after the other. This means that start conditions that build on another or follow each other can only be processed if the prior condition is met. Only then the following condition can be checked.
@@ -254,9 +254,9 @@
  == Scheduled Server Tasks ==
--The [[scheduled server tasks>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HScheduledServerTasks"]], which you can set and start under //System > Settings > ACMP Server//, are also jobs. However, these jobs only affect the ACMP Server and are based exclusively on recurring start conditions.
++The [[scheduled server tasks>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HGeplanteServeraufgaben"]], which you can set and start under //System > Settings > ACMP Server//, are also jobs. However, these jobs only affect the ACMP Server and are based exclusively on recurring start conditions.
  = Checking job executions =
--After you have started your jobs, you can view them in the [[Job Monitor>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HJobMonitor"]]. You will receive information about which jobs are pending on the clients, have already been successfully executed or have failed.
--You can also view all jobs that are still being executed by one or more clients, have already been successfully executed or have failed from the client's perspective in the [[Client Monitor>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HClientMonitor"]] from the client's perspective. You can check the execution of server jobs in the [[Server Monitor>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HServerMonitor"]].
++After you have started your jobs, you can view them in the [[Job Monitor>>doc:ACMP.68.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HClientmonitor"]] . You will receive information about which jobs are pending on the clients, have already been successfully executed or have failed.
++You can also view all jobs that are still being executed by one or more clients, have already been successfully executed or have failed from the client's perspective in the [[Client monitor>>doc:ACMP.68.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HClientmonitor"]] from the client's perspective. You can check the execution of server jobs in the [[Server Monitor>>doc:ACMP.68.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HServermonitor"]].