Skip to content

Windows Execution Contexts ​

Choose an execution context to control which Windows account runs an endpoint script, package workflow, artifact collection, or GUI automation. Runner scripts use the Runner service account instead.

Choosing a Context ​

ContextUse when
Local systemMaking machine-wide changes without a user's profile or desktop
Local Ordyn installation userInstalling software with Ordyn's managed local account, .\OrdynInst
Specific userUsing a saved Windows Account, even when the user is signed out
Templated userSelecting credentials from variables, including prompted job values
Specific user elevated / Templated user elevatedThe selected account must run with administrator rights
Current active user sessionWorking in the active console user's existing session
Current active user session elevatedWorking in that session with administrator rights
Specific logged-in userTargeting a particular account's existing session on a multi-user endpoint

The local Ordyn installation user is the default for new Windows package workflows. It is unavailable on Active Directory domain controllers; use Local system or a suitable domain account there.

For templated users, select a plain string variable for the username and a secret string variable for the password. In jobs, credentials resolve from the task's applicable endpoint, product, package, job, and submitted run values. Direct execution outside a job uses endpoint values.

Elevated contexts require an account that can run as an administrator. Other user contexts do not request elevation, but Windows settings such as disabled User Account Control can still give an administrator account broader access.

Targeting existing sessions ​

Current-active-user contexts select the console user when the task starts. A delayed event-triggered job may therefore run for a different user than the one who caused the event. Remote Desktop events do not select their RDP session automatically.

Use Specific logged-in user to select an existing session by DOMAIN\username, username@domain.example, .\username, or HOSTNAME\username. Avoid bare usernames when accounts could be ambiguous. The task fails if the required session is unavailable.

Network access ​

The selected account must have access to network resources used by the task. On a domain-joined endpoint, LocalSystem presents the computer account's credentials, DOMAIN\HOSTNAME$, to remote servers. The share and filesystem must allow that computer account. See Microsoft's computer-account guidance.

Prefer UNC paths where possible. Mapped drives belong to a Windows session and may not be available in another context.

Session reuse within a job ​

Credential-backed tasks in the same job target can share session state, such as mapped drives, when they use the same saved account or templated credential pair, resolve to the same user, and use the same elevation mode.

Changing account or elevation starts a separate session. Sessions are not shared between runs or endpoints, and an Agent or endpoint restart starts a fresh session.

Running an endpoint script on the active desktop ​

Windows PowerShell and CMD scripts can target the existing active desktop in blocking or non-blocking mode. This requires a signed-in, unlocked console session. LocalSystem is unavailable for this mode, and a specific logged-in user must own that console session.

GUI programs launched by the script can appear on the desktop. The script interpreter stays hidden; blocking mode does not make its console visible.

Use blocking mode when the job needs the output, exit code, timeout, or cancellation. If the script starts a GUI program asynchronously, make it wait—for example with PowerShell's Start-Process -Wait—when later job steps depend on that program finishing.

Non-blocking mode confirms only that the interpreter started. Later failures and completion are not tracked, and cancelling the job does not stop the launched work.

Desktop logon ​

Creating a desktop logon requires a saved Windows Account, templated credentials, or the managed installation user. Existing-session contexts cannot create a new sign-in. See GUI automation for managed desktop preparation and cleanup.