Changes for page Konfigurationsmöglichkeiten für Managed Software
Last modified by Sabrina V. on 2026/09/24 12:49
From version 2.1
edited by Sabrina V.
on 2026/09/24 12:49
on 2026/09/24 12:49
Change comment:
There is no comment for this version
To version 1.1
edited by Sabrina V.
on 2026/09/24 09:08
on 2026/09/24 09:08
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,7 +4,7 @@ 4 4 5 5 = Jobs and Tasks = 6 6 7 -Managed Software requires server jobs and tasks to run smoothly. These jobs are designed, among other things, to check for software versions that are already installed or available on a client, or that are required (Agent Tasks). Server tasks, among other things, download new versions or update the software catalog. You can assign a [[start condition>>doc:ACMP.610.ACMP-Solutions.Jobs.WebHome||anchor="HStart conditions"]] to both the Agent Tasks job and the server tasks, which you can customize based on your environment. The jobs and tasks run at intervals and sequentially, one after the other. You can check the sequence in the monitors (including the Job, Client, and Server Monitors).7 +Managed Software requires server jobs and tasks to run smoothly. These jobs are designed, among other things, to check for software versions that are already installed or available on a client, or that are required (Agent Tasks). Server tasks, among other things, download new versions or update the software catalog. You can assign a [[start condition>>doc:ACMP.610.ACMP-Solutions.Jobs.WebHome||anchor="HStartbedingungen"]] to both the Agent Tasks job and the server tasks, which you can customize based on your environment. The jobs and tasks run at intervals and sequentially, one after the other. You can check the sequence in the monitors (including the Job, Client, and Server Monitors). 8 8 9 9 **[[Agent Tasks>>doc:ACMP.610.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]]** (//Client Management// > //Agent Task//s) 10 10 ... ... @@ -15,7 +15,7 @@ 15 15 Please note that the job is available only in the agent planner templates for the Windows operating system. 16 16 {{/aagon.infobox}} 17 17 18 -**[[Scheduled Server Tasks>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="H ScheduledServerTasks"]]** (//System// > //Settings //> //acmp// //Server// > //Scheduled Server Tasks//)18 +**[[Scheduled Server Tasks>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HGeplanteServeraufgaben"]]** (//System// > //Settings //> //acmp// //Server// > //Scheduled Server Tasks//) 19 19 20 20 |**Server Task**|**Description**|**Recommended Start Condition** 21 21 |Managed Software cleanup|The server task deletes the Managed Software versions that are no longer needed, thereby freeing up storage space|Start every day ... ... @@ -35,7 +35,7 @@ 35 35 36 36 = Track Managed Software Jobs in the Monitors = 37 37 38 -Once you have created jobs in Managed Software, you can view the current status and results of finished jobs in the monitors. This info is available specifically through the [[Job monitor>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HJob Monitor"]]. To do so, filter by the content “Managed Software.”38 +Once you have created jobs in Managed Software, you can view the current status and results of finished jobs in the monitors. This info is available specifically through the [[Job monitor>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HJobmonitor"]]. To do so, filter by the content “Managed Software.” 39 39 40 40 If, on the other hand, you want to check the status of a specific software package, you can do so via the //Tests// tab in the open Managed Software window. To do this, select the desired software package and version number. A details window will now open on the right-hand side, displaying a table that lists all jobs in which the current software version was executed on a Client within a test ring. 41 41 ... ... @@ -61,10 +61,10 @@ 61 61 |(% style="width:153px" %)[[image:1790152023904-355.png]] Failed|(% style="width:1539px" %)The job was executed, but the defined actions could not be completed successfully due to one or more errors. 62 62 |(% style="width:153px" %)[[image:1790152059056-472.png]] Successful|(% style="width:1539px" %)The job was executed, and the defined actions were successfully completed. 63 63 |(% colspan="1" rowspan="2" style="width:153px" %)[[image:1790152081055-539.png]] Skipped|(% style="width:1539px" %)((( 64 -The job was executed and no error occurred; however, the defined actions were skipped because the intended target of the action already exists. Thus, while it would be possible to perform the action, it is not necessary. 64 +The job was executed and no error occurred; however, the defined actions were skipped because the intended target of the action already exists. Thus, while it would be possible to perform the action, it is not necessary (see: [[Software Package Parameters>>path:/bin/view/ACMP/69/ACMP-Solutions/Patch%20Management/Managed%20Software/Managed%20Software%20verteilen/#HParameterderSoftwarepaketekonfigurieren]]). 65 65 ))) 66 66 |(% style="width:1539px" %)((( 67 -**Example: **For a software package, the action //Install or Update// is specified in the parameters. This job is then executed and finished. However, the result displayed is not //Successful// but //Skipped//. The reason for this is that the intended goal of the action -in this case, “**The software package is installed on the Client in its current version**”-has already been met. Therefore, there is no error with the //Install or Update// actions; rather, they could have been executed successfully if the action’s target had not already been met.67 +**Example: **For a software package, the action //Install or Update// is specified in the parameters. This job is then executed and finished. However, the result displayed is not //Successful// but //Skipped//. The reason for this is that the intended goal of the action—in this case, “**The software package is installed on the Client in its current version**”—has already been met. Therefore, there is no error with the //Install or Update// actions; rather, they could have been executed successfully if the action’s target had not already been met. 68 68 ))) 69 69 |(% style="width:153px" %)[[image:1790152039995-689.png]] Without a License|(% style="width:1539px" %)The job was executed, but the defined actions could not be completed successfully because those actions require one or more specific acmp licenses that you do not have. 70 70

