Changes for page Jobs

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

From 15.1 to 16.1

From version 16.1

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

Change comment: There is no comment for this version

To version 18.1

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

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.SF
++XWiki.SV

Content

@@ -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="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="HCreatecontainer"]].
 . 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,34 +186,36 @@
  {{/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="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="HGeneral"]]; these are executed again once.
  {{/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.
++
++|(% 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).
  )))
--|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" %)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.
  )))
--|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).
++|(% 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.
--* Example: The computer is restarted.
++* Example: The user logs on to the computer.
  )))
--|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.
++|(% 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.
  Finally, save your changes so that the scanners or maintenance tasks can start under the new start conditions.
@@ -252,9 +252,9 @@
  == Scheduled Server Tasks ==
--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.
++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.
  = 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="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"]].
++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"]].