Changes for page Client Commands

Last modified by Sabrina V. on 2025/11/27 12:17

From version 3.1
edited by Sabrina V.
on 2025/11/27 12:17
Change comment: There is no comment for this version
To version 2.1
edited by Steffi F
on 2025/05/12 11:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.SV
1 +XWiki.SF
Content
... ... @@ -24,7 +24,7 @@
24 24  
25 25  == Separate additional data ==
26 26  
27 -By using file repositories (see [[Distributed File Repositories>>path:/bin/view/ACMP/69/ACMP-Solutions/System/Verteilte%20File%20Repositories/]]), additional data from client commands, e.g. installation files, configuration files, etc., can be stored on different servers. This allows the network load to be balanced. When a client command is executed by a server/client, the actual client command data is queried from the ACMP server. The client command itself then instructs the server/client to reload the associated files from a file repository.
27 +By using file repositories (see [[Distributed File Repositories>>path:/bin/view/ACMP/68/ACMP-Solutions/System/Verteilte%20File%20Repositories/]]), additional data from client commands, e.g. installation files, configuration files, etc., can be stored on different servers. This allows the network load to be balanced. When a client command is executed by a server/client, the actual client command data is queried from the ACMP server. The client command itself then instructs the server/client to reload the associated files from a file repository.
28 28  
29 29  = Phases =
30 30  
... ... @@ -32,19 +32,19 @@
32 32  
33 33  == 1. Create ==
34 34  
35 -In the [[Create>>path:/bin/view/ACMP/69/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20erstellen/]] phase, Client Commands can be created, edited, versioned, and managed. Furthermore, the scripts of a Client Command and its version history can be viewed.
35 +In the [[Create>>path:/bin/view/ACMP/68/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20erstellen/]] phase, Client Commands can be created, edited, versioned, and managed. Furthermore, the scripts of a Client Command and its version history can be viewed.
36 36  
37 37  == 2. Test ==
38 38  
39 -In the [[Test>>path:/bin/view/ACMP/69/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20testen/]] phase, Client Commands can be tested on selected clients. The test clients must be directly connected to the ACMP Server.
39 +In the [[Test>>path:/bin/view/ACMP/68/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20testen/]] phase, Client Commands can be tested on selected clients. The test clients must be directly connected to the ACMP Server.
40 40  
41 41  == 3. Synchronize ==
42 42  
43 -In the [[Synchronize>>path:/bin/view/ACMP/69/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20synchronisieren/]] phase, any additional files of a Client Command are distributed to the various file repositories.
43 +In the [[Synchronize>>path:/bin/view/ACMP/68/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20synchronisieren/]] phase, any additional files of a Client Command are distributed to the various file repositories.
44 44  
45 45  == 4. Release ==
46 46  
47 -In the [[Release>>path:/bin/view/ACMP/69/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20freigeben/]] phase, any additional files of a Client Command are distributed to all file repositories (or at least some of them). The Client Command can now be released for use and is then available on the clients.
47 +In the [[Release>>path:/bin/view/ACMP/68/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20freigeben/]] phase, any additional files of a Client Command are distributed to all file repositories (or at least some of them). The Client Command can now be released for use and is then available on the clients.
48 48  
49 49  There is also the Execute option. Here, a log file can be viewed for each execution of a Client Command. This allows any problems that have occurred to be analyzed.
50 50  
... ... @@ -58,4 +58,4 @@
58 58  
59 59  == 5. Execute ==
60 60  
61 -In the [[Execute>>path:/bin/view/ACMP/69/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20ausf%C3%BChren/]] phase, all Client Commands that are ready for execution are displayed. You also receive information about Client Commands that have already been executed.
61 +In the [[Execute>>path:/bin/view/ACMP/68/ACMP-Solutions/Desktop%20Automation/Client%20Commands/Client%20Command%20ausf%C3%BChren/]] phase, all Client Commands that are ready for execution are displayed. You also receive information about Client Commands that have already been executed.
© Aagon GmbH 2026
Besuchen Sie unsere Aagon-Community