Skip to Content

Changes for page Jobs

Last modified by Sabrina V. on 2026/10/07 08:19
From version 17.1
edited by Sabrina V.
on 2026/07/28 11:46
Change comment: There is no comment for this version
To version 19.1
edited by Sabrina V.
on 2026/10/07 08:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,12 +5,12 @@
5 5  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]](%%).
6 6  
7 7  {{aagon.infobox}}
8 -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"]].
8 +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||data-cmp-info="10" height="24" width="24"]] [[image:Ico_ClientType_Linux_Managed.png||data-cmp-info="10" height="24" width="24"]][[image:Ico_ClientType_MacOs_Managed.png||data-cmp-info="10" height="24" width="24"]].
9 9  {{/aagon.infobox}}
10 10  
11 11  = Types of jobs =
12 12  
13 -The task of a job depends fundamentally on its type. Since ACMP 6.8, a distinction is also made between the operating system family of the clients on which the job is to be executed. For this reason, there are jobs for clients with Windows operating systems and jobs for clients with Unix operating systems.
13 +The task of a job depends fundamentally on its type. Since acmp 6.8, a distinction is also made between the operating system family of the clients on which the job is to be executed. For this reason, there are jobs for clients with Windows operating systems and jobs for clients with Unix operating systems.
14 14  
15 15  == Windows jobs ==
16 16  
... ... @@ -48,21 +48,21 @@
48 48  1. Click the button //Execute//.
49 49  
50 50  {{aagon.infobox}}
51 -The console script of a Client Command is only executed when a job is pushed. In this case, it is executed with the rights with which the ACMPConsole.exe was started. The execution takes place on the console that triggered the command. The console script is executed first, and only if the execution was suClient Commandessful, the client script gets executed. The connection to the clients is established from the ACMP Server.
51 +The console script of a Client Command is only executed when a job is pushed. In this case, it is executed with the rights with which the ACMPConsole.exe was started. The execution takes place on the console that triggered the command. The console script is executed first, and only if the execution was suClient Commandessful, the client script gets executed. The connection to the clients is established from the acmp Server.
52 52  {{/aagon.infobox}}
53 53  
54 -[[Manual execution of jobs>>image:Jobs_Manuelle Ausführung.png||alt="Manuelle Ausführung von Jobs"]]
54 +[[Manual execution of jobs>>image:Jobs_Manuelle Ausführung.png||alt="Manuelle Ausführung von Jobs" data-cmp-info="10"]]
55 55  
56 56  == Execute a container job ==
57 57  
58 -A job or an entire Job Collection is attached to a container, which is started either repeatedly or once on the ACMP Agent.
58 +A job or an entire Job Collection is attached to a container, which is started either repeatedly or once on the acmp Agent.
59 59  
60 -If the server cannot reach the client, the client retrieves the jobs assigned to it. If the client is switched off, the job gets executed later when the ACMP Agent service is started. Unlike pushed jobs, no console script is executed for container jobs.
60 +If the server cannot reach the client, the client retrieves the jobs assigned to it. If the client is switched off, the job gets executed later when the acmp Agent service is started. Unlike pushed jobs, no console script is executed for container jobs.
61 61  
62 62  Jobs or job collections can be added to containers in the Container module:
63 63  
64 -1. In the ACMP Console navigation, navigate to //Client Management > Container.//
65 -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"]]..
64 +1. In the acmp Console navigation, navigate to //Client Management > Container.//
65 +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"]].
66 66  1. In the detail view of the container, click on the //Jobs// tab.
67 67  1. In the ribbon bar in the //Jobs// area, click on the //Add// button.
68 68  1. A wizard opens in which you can select the type of job (Client Command, Job Collections, Managed Software, Windows Update Collections or Unix Scripts).
... ... @@ -74,7 +74,7 @@
74 74  1. If necessary, define individual start conditions for the execution. Follow the instructions in the Start Conditions Wizard.
75 75  1. Click the //Finish// button.
76 76  
77 -[[Adding jobs to containers>>image:Container-Jobs.png||alt="Hinzufügen von Jobs zu Containern"]]
77 +[[Adding jobs to containers>>image:Container-Jobs.png||alt="Hinzufügen von Jobs zu Containern" data-cmp-info="10"]]
78 78  
79 79  == Set parameters for Client Command jobs ==
80 80  
... ... @@ -81,7 +81,7 @@
81 81  When you execute a Client Command job, you also have the option of editing parameter values. Each Client Command has parameters that you can customize. The parameter settings only apply to the selected Client Command.
82 82  
83 83  {{figure}}
84 -[[image:Feste Parameter.PNG||data-xwiki-image-style-alignment="center"]]
84 +[[image:Feste Parameter.PNG||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
85 85  
86 86  {{figureCaption}}
87 87  Fixed parameter values of the Client Command job
... ... @@ -124,12 +124,12 @@
124 124  |(% style="width:223px" %)//Install//|(% style="width:1216px" %)The software should be installed.
125 125  |(% style="width:223px" %)//Uninstall//|(% style="width:1216px" %)The software should be uninstalled.
126 126  |(% style="width:223px" %)//Repair//|(% style="width:1216px" %)The software should be repaired in case of a defect.
127 -|(% 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}}
127 +|(% 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}}
128 128  |(% style="width:223px" %)//Unpark//|(% style="width:1216px" %)The software is removed from the client on which it was previously stored.
129 129  
130 130  (% class="box infomessage" %)
131 131  (((
132 -[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt="“Note”" height="32" width="32"]] **Note: **
132 +[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt="“Note”" data-cmp-info="10" height="32" width="32"]] **Note: **
133 133  
134 134  These actions are only available for client commands that were generated independently or via the Package Wizard.
135 135  )))
... ... @@ -139,7 +139,7 @@
139 139  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.
140 140  
141 141  {{figure}}
142 -[[image:Parameter MSW.PNG||data-xwiki-image-style-alignment="center"]]
142 +[[image:Parameter MSW.PNG||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
143 143  
144 144  {{figureCaption}}
145 145  Fixed and variable parameter values of the MSW job
... ... @@ -186,7 +186,7 @@
186 186  {{/aagon.infobox}}
187 187  
188 188  {{aagon.versionierungsbox}}
189 -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.
189 +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.
190 190  {{/aagon.versionierungsbox}}
191 191  
192 192  
... ... @@ -244,7 +244,7 @@
244 244  
245 245  The condition description is now “From 11/21/2024 12:00 between 12:00 and 3:00 p.m. and wake up 10 minutes before.” Since the start time is before the start of the time window, the condition would not start until November 22, 2024, because it was moved forward by 10 minutes by waking up the computer and therefore no longer fits the condition.
246 246  
247 -[[Combined start conditions>>image:ACMP.68.ACMP-Solutions.Desktop Automation.Client Commands.Jobs ausführen.WebHome@68_Startbedingung_Kombination verschiedener Startbedingungen_845.png||alt="67_Startbedingung_Kombination verschiedener Startbedingungen_845.png"]]
247 +[[Combined start conditions>>image:ACMP.68.ACMP-Solutions.Desktop Automation.Client Commands.Jobs ausführen.WebHome@68_Startbedingung_Kombination verschiedener Startbedingungen_845.png||alt="67_Startbedingung_Kombination verschiedener Startbedingungen_845.png" data-cmp-info="10"]]
248 248  
249 249  In the shown sequence, the “Start time” condition is evaluated first. Only when this is fulfilled is the “Time window” condition checked. The additionally selected option //Wake up computer for job //(as well as all options not selected in the figure) always belong to the respective condition (“Time window”) and do not refer to the entire condition.
250 250  
... ... @@ -254,9 +254,9 @@
254 254  
255 255  == Scheduled Server Tasks ==
256 256  
257 -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.
257 +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.
258 258  
259 259  = Checking job executions =
260 260  
261 -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.
262 -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"]].
261 +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.
262 +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"]].
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community