Commandlist

Last modified by Steffi F on 2026/08/07 06:33

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.

save

Saves the current Client Command.

Properties

Opens the Properties dialog box.

variables

Opens the dialog box for editing variables.

FileRepository

Opens the file repository.

Tree_ViewAsList

 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.
When you want to use a command, simply drag and drop it to the appropriate location in the script area.
A dialog box will then appear, allowing you to control the exact function of the command. Various icons are displayed in a column on the left side of the dialog box. If an icon is hidden, that function is not available for the command; for example, it may not allow nested commands or multiple iterations (the latter applies, for example, to the Loop command):

Compatibility (​Kompabilität.png)

The Windows icon indicates which operating systems the Command is compatible with. A list appears showing the various versions under which the Command can run.

Loop Command (Loop.png​)

You can place other commands indented under this command, and they will be executed repeatedly until the loop is finished. This applies to all blocks that are nested under this command.

Main Command (Hauptbefehl.png​)

This command allows nested commands, so you can place other commands indented under this command.

Commandlist
Commandlist

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.).

ClientCommandCenter_CommandList2

Allgemeine Command Informationen

Hinweis  Note:  

Please note that some commands are always executed in the user context. These include all commands in the “Dialogs” category, as well as “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 in to the client. Also note that no user is logged in during shutdown. Additionally, it is possible that no user is logged in when the Client starts up.

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.

Hinweis  Note:  

Whenever files, directories, numbers, or similar items are specified, a variable can be used in the corresponding input fields instead of a specific value.

All time and date values written to variables by commands use the format set in Windows (Control Panel => Regional and Language Options).

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

If user is (not) local admin

If user is (not) in group

If logged on user is (not)

Usermanagement

Create local user

Rename local user

Set password for local user

Set flag for local user

Set profile for local user

Delete local user

Assign local user to local groups

Add priviledge to user/group

Remove priviledge from user/group

Affected Usernames

The following usernames are mapped to system users:

Affected Usernames

 / SID

is expanded to

AAAccess control assistance operators
ACAll applications running in an app package context
ANAnonymous logon
AOAccount operator
APProtected Users
AUAuthenticated users
BABuilt-In administrator
BGBuilt-In guests
BOBackup operator
BUBuilt-In users
CACertificate publishers
CDUsers who can connect to certification authorities using Distributed Component Object Model (DCOM).
CGCreator group
CNCloneable domain controllers.
COCreator owner
CYCrypto operators
DADomain administrator
DCDomain computers
DDDomain controllers
DGDomain guests
DUDomain users
EAEnterprise administrator
EDEnterprise domain controllers
EKEnterprise domain controllers
EREvent log readers
ESEndpoint servers
HAHyper-V administrators
HIHigh integrity level
HOGroup members may operate hardware from user mode
ISAnonymous Internet users
IUInteractively logged-on user
KADomain key admins
LALocal administrator
LGLocal guest
LSLocal service account
LUPerfomance Log users
LWLow integrity level
MEMedium integrity level
MPMedium Plus integrity level
MUPerformance Monitor users
NONetwork configuration operator
NSNetwork service account
NUNetwork logon user
OWOwner Rights SID
PAGroup Policy administrator
POPrinter operator
PSPrincipal self
PUPower users
RARDS remote access servers
RCRestricted code
RDTerminal server users
REReplicator
RMRMS Service
ROEnterprise Read-only domain controllers
RSRAS servers group
RUAlias to grant permissions to accounts that use applications compatible with operating systems previous to Windows 2000
SASchema administrator
SHUsers allowed to connect with OpenSSH
SISystem integrity level
SOServer operator
SSAuthentication service asserted
SUService logon user
SYLocal system
UDUser-mode driver
WDEveryone
WRWrite Restriced code
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community