Client commands > Tools > Client command editor

	Save Saves the current Client Command.
	Project properties Opens the Properties dialog.
	Edit variables Opens the dialog for editing tags.
	File repository Opens the file repository (see File Repository).
	List view Alternates the command list between list and category view.

ClientCommandCenter_Commandlist1

The command list contains a quick access toolbar with the most important options as well as all available commands which you can use to generate a Client Command.

If you want to use a command, you have to move it with drag & drop to the appropriate position in the script section. Then a dialog through which you can control the exact function of the command is displayed. In a column on the left edge of the dialog various symbols are displayed:

Loop command

You can assign additional subordinate commands to this command, which will then run repeatedly.

Main command

Additional subordinate commands can be assigned to this command.

Compatibility

The various Windows icons indicate the version of the operating system with which the command is compatible.

The General tab is the same for (almost) all commands. Here the name of the command and its description can be adapted to the Client Command. Furthermore, there are additional options which can be set for the execution of the command within the Client Command.

ClientCommandCenter_CommandList2

General command information

In the section Options, you can state if the command is activated - in other words, if it is running - and if errors are to be ignored during execution. You can also specify the interval in milliseconds between the execution of one command and the execution of the next command.

In the Execution options, the context and executing unit can be specified as well. In Context you can state if the command is to run all the time, or if it is to run linked specifically to a user or machine.

User-based execution of the command is useful, for example, if software is installed specifically for one user and not for the entire system, or if the program has to resort to environment variables of the user. Machine-related execution of the command is useful if, for example, software is to be installed for the entire system with all users (updates, patches, etc.).

Note:

Note that some commands are always executed in the user context. This includes all commands in the category Dialogsand Lock manual input, Unlock manual input, Get idle time, Lock workstation, Get/Set default printer and If user is (not) in group.

These commands are not executed if no user is logged on to the client. Make sure that no user is logged in when you shut down the machine. It may also occur that no user is logged in when the client starts up.

Then there is the distinction between running the command as a service or as a user on the client/server. Commands should be run as a service, e.g., if administrator rights are required for an installation or if system-wide configurations are made (adjust environment variables, size of swap file, etc.). Commands executed as a user serve to make environment variables of the user available and to assign rights to the user, e.g. in a newly created folder. This option is also required when the user needs to interact with the command, e.g., in the installation dialog, progress bars or similar features.

The special settings of the individual commands will be explained in the following sections. In doing so, the commands will be be listed in these sections in the sequence in which they are assigned to the categories in the command list.

Note:

For all details of files, directories, numbers, or the like, a variable may be used instead of specific data in the matching input fields. All times and dates created by commands in variables are displayed in the format which has been configured in Windows (Control Panel => Regional and Language Options).

Last change on 02.03.2018