Commandlist
The Command List contains all the available functions for creating a Client Command. These are generally organized into categories, but can also be displayed as a list. To use a function, simply drag it into the script.
| Saves the current Client Command. |
| Opens the Properties dialog box. |
| Opens the dialog box for editing variables. |
| Opens the file repository. |
| Toggles the command list between list view and category view. |
In the Command List, you’ll find a quick-selection bar with the most important Options, as well as all available commands that you can use to create a Client Command. Compatibility ( |
|
The General tab is identical for (almost) all commands. Here, you can customize the command’s name and description within the Client Command. There are also additional Options that can be set for executing the command within the Client Command. In the Options section, you can specify whether the command is enabled—that is, whether it will be executed—and whether errors during execution should be ignored. You can also specify how many milliseconds to wait after executing the Command before executing the next one. In the Execution Options, you can then specify the context and the executing entity. Under Context, you can specify whether the Command should be executed always, or whether it should be executed on a per-user or machine related basis. User-specific execution of the Command is useful, for example, when software is installed specifically for a single user rather than for the entire system, or when the user’s environment variables must be accessed. Machine related execution of the Command is useful, for example, when software is installed for the entire system and all users (Updates, patches, etc.). | ![]() Allgemeine Command Informationen |
There is also a distinction to be made between whether the command is executed as a service or as a user on the client/server. Commands should be executed as a service if, for example, administrator privileges are required for an installation or if system-wide configurations are being made (customizing environment variables, changing the size of the paging file, etc.). Commands executed as a user serve to make the user’s environment variables accessible and to assign the user’s rights to, for example, a newly created folder. This option is also necessary whenever the user needs to interact with the command, such as during installation dialogs, progress bars, or similar scenarios.
The specific settings for each command are discussed in the following chapters. In these chapters, the commands are listed in the order in which they are assigned to categories in the command list.
Using Short Usernames
Using usernames that consist of only 2 characters can lead to errors, which we explain below.
In Windows operating systems, there is a function that resolves such usernames to the SID of system users. This can cause problems when using Client Command modules.
Affected Client Commands
The following Client Commands cannot be used with 2-character usernames:
Conditions
Usermanagement
Assign local user to local groups
Remove priviledge from user/group
Affected Usernames
The following usernames are mapped to system users:
Affected Usernames / SID | is expanded to |
| AA | Access control assistance operators |
| AC | All applications running in an app package context |
| AN | Anonymous logon |
| AO | Account operator |
| AP | Protected Users |
| AU | Authenticated users |
| BA | Built-In administrator |
| BG | Built-In guests |
| BO | Backup operator |
| BU | Built-In users |
| CA | Certificate publishers |
| CD | Users who can connect to certification authorities using Distributed Component Object Model (DCOM). |
| CG | Creator group |
| CN | Cloneable domain controllers. |
| CO | Creator owner |
| CY | Crypto operators |
| DA | Domain administrator |
| DC | Domain computers |
| DD | Domain controllers |
| DG | Domain guests |
| DU | Domain users |
| EA | Enterprise administrator |
| ED | Enterprise domain controllers |
| EK | Enterprise domain controllers |
| ER | Event log readers |
| ES | Endpoint servers |
| HA | Hyper-V administrators |
| HI | High integrity level |
| HO | Group members may operate hardware from user mode |
| IS | Anonymous Internet users |
| IU | Interactively logged-on user |
| KA | Domain key admins |
| LA | Local administrator |
| LG | Local guest |
| LS | Local service account |
| LU | Perfomance Log users |
| LW | Low integrity level |
| ME | Medium integrity level |
| MP | Medium Plus integrity level |
| MU | Performance Monitor users |
| NO | Network configuration operator |
| NS | Network service account |
| NU | Network logon user |
| OW | Owner Rights SID |
| PA | Group Policy administrator |
| PO | Printer operator |
| PS | Principal self |
| PU | Power users |
| RA | RDS remote access servers |
| RC | Restricted code |
| RD | Terminal server users |
| RE | Replicator |
| RM | RMS Service |
| RO | Enterprise Read-only domain controllers |
| RS | RAS servers group |
| RU | Alias to grant permissions to accounts that use applications compatible with operating systems previous to Windows 2000 |
| SA | Schema administrator |
| SH | Users allowed to connect with OpenSSH |
| SI | System integrity level |
| SO | Server operator |
| SS | Authentication service asserted |
| SU | Service logon user |
| SY | Local system |
| UD | User-mode driver |
| WD | Everyone |
| WR | Write Restriced code |



