Changes for page Jobs

Last modified by Sabrina V. on 2026/01/28 06:01
From version 10.1
edited by jklein
on 2025/08/22 12:57
Change comment: There is no comment for this version
To version 13.1
edited by Sabrina V.
on 2026/01/28 06:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.jklein
1 +XWiki.SV
Content
... ... @@ -2,7 +2,7 @@
2 2  
3 3  Job Management allows you to manage tasks for clients and the server efficiently.
4 4  
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.68.ACMP-Solutions.Jobs.Job Collections.WebHome]](%%).
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.69.ACMP-Solutions.Jobs.Job Collections.WebHome]](%%).
6 6  
7 7  {{aagon.infobox}}
8 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"]].
... ... @@ -21,7 +21,7 @@
21 21  For Unix jobs, you can currently only execute Unix scripts as jobs.
22 22  
23 23  {{aagon.infobox}}
24 -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]]__.
24 +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]]__.
25 25  {{/aagon.infobox}}
26 26  
27 27  = Execution of jobs =
... ... @@ -62,7 +62,7 @@
62 62  Jobs or job collections can be added to containers in the Container module:
63 63  
64 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.68.ACMP-Solutions.Client-Management.Container.Container verwalten.WebHome||anchor="HContainererstellen"]]..
65 +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"]]..
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).
... ... @@ -124,7 +124,7 @@
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.
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" %)
... ... @@ -185,6 +185,11 @@
185 185  The start conditions //Specific time//, //As soon as possible// and //Start interval// cannot be set for jobs that should be executed once.
186 186  {{/aagon.infobox}}
187 187  
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.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.
190 +{{/aagon.versionierungsbox}}
191 +
192 +
188 188  |**Start condition**|**Explanation**
189 189  |Login|The condition is executed as soon as a user logs on to the system or terminal server.(((
190 190  * Example: The user logs on to the computer.
... ... @@ -242,9 +242,9 @@
242 242  
243 243  == Scheduled Server Tasks ==
244 244  
245 -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.
250 +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.
246 246  
247 247  = Checking job executions =
248 248  
249 -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.
250 -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"]].
254 +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.
255 +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"]].
© Aagon GmbH 2026
Besuchen Sie unsere Aagon-Community