Client commands are scripts that can run on the console as well as on a client. Accordingly, Client Commands consist of consoles and/or client scripts, which depends entirely on the application of the Client Commands. Client Commands are in principle used to install software, to set configurations or to interact with the system. Client Commands always consist of several individual commands/actions.
Client Commands are made up to console scripts and client scripts. Both scripts or even just one of the two scripts can be created - depending on which tasks the Client Command should have. In doing so, the console script is executed on the computer on which the console has been opened. Once the console script has run successfully, the client script is started on the client. The console script is mainly used for the dynamic configuration of the client script.
With the use of file repositories (see Distributed File Repositories), additional data from Client Commands, such as installation, configuration files, etc., can be saved on different servers. This makes it possible to compensate for the network load. If a Client Command is performed by a server/client, the actual Client Command data are queried from the ACMP servers. The Client Command itself then causes the server/client to load the associated files from a file repository.
Last change on 10.03.2014