Changes for page Jobs

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

From 12.1 to 13.1 From 16.1 to 17.1

From version 13.1

edited by Sabrina V.
on 2026/01/28 06:01

Change comment: There is no comment for this version

To version 16.1

edited by Steffi F
on 2026/06/15 13:11

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.SF

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.69.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.610.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.69.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.610.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.69.ACMP-Solutions.Client-Management.Container.Container verwalten.WebHome||anchor="HContainererstellen"]]..
++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="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).
@@ -186,7 +186,7 @@
  {{/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.69.ACMP-Solutions.Desktop Automation.Client Commands.Client Command erstellen.Client Commands neu hinzufügen.Client Command Editor.Menüleiste.Client Command Eigenschaften .WebHome||anchor="HAllgemein-1"]]; these are executed again once.
++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="HAllgemein-1"]]; these are executed again once.
  {{/aagon.versionierungsbox}}
@@ -224,6 +224,11 @@
  {{/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.
++{{/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}}
@@ -247,9 +247,9 @@
  == Scheduled Server Tasks ==
--The [[scheduled server tasks>>doc:ACMP.69.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.
++The [[scheduled server tasks>>doc:ACMP.610.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.69.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.69.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.69.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.610.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.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"]].