Changes for page Jobs

Summary

• Page properties (2 modified, 0 added, 0 removed)

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).
...	...	@@ -117,6 +117,23 @@
117	117	//Always save advanced log//
118	118	)))|The advanced log is always saved, regardless of whether an error occurred during job execution or not.
119	119
	120	+**//Actions//**
	121	+
	122	+These settings allow you to decide which action is applied when the Client Command is executed:
	123	+
	124	+|(% style="width:223px" %)//Install//|(% style="width:1216px" %)The software should be installed.
	125	+|(% style="width:223px" %)//Uninstall//|(% style="width:1216px" %)The software should be uninstalled.
	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}}
	128	+|(% style="width:223px" %)//Unpark//|(% style="width:1216px" %)The software is removed from the client on which it was previously stored.
	129	+
	130	+(% class="box infomessage" %)
	131	+(((
	132	+[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt="“Note”" height="32" width="32"]] **Note: **
	133	+
	134	+These actions are only available for client commands that were generated independently or via the Package Wizard.
	135	+)))
	136	+
120	120	== **Set parameters for Managed Software jobs** ==
121	121
122	122	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.
...	...	@@ -168,6 +168,11 @@
168	168	The start conditions //Specific time//, //As soon as possible// and //Start interval// cannot be set for jobs that should be executed once.
169	169	{{/aagon.infobox}}
170	170
	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	+
171	171	|**Start condition**|**Explanation**
172	172	|Login|The condition is executed as soon as a user logs on to the system or terminal server.(((
173	173	* Example: The user logs on to the computer.
...	...	@@ -195,14 +195,14 @@
195	195
196	196	Finally, save your changes so that the scanners or maintenance tasks can start under the new start conditions.
197	197
198		-== **Besonderes Verhalten der Startbedingungen** ==
	220	+== **Special behavior of start conditions** ==
199	199
200	200	{{aagon.infobox}}
201		-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.
	223	+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.
202	202	{{/aagon.infobox}}
203	203
204	204	{{aagon.infobox}}
205		-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.
	227	+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.
206	206	{{/aagon.infobox}}
207	207
208	208	== Processing combined start conditions ==
...	...	@@ -225,9 +225,9 @@
225	225
226	226	== Scheduled Server Tasks ==
227	227
228		-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.
229	229
230	230	= Checking job executions =
231	231
232		-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.
233		-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"]].