> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/powershell-terminal-local.md).

# PowerShell terminal (local)

Configure PowerShell terminal (local) settings in Remote Desktop Manager, including the script source, terminal application, parameters, run as, and version.

This article details the many settings and options available for ***PowerShell terminal (local)*** session entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located. Click the browse button to select a folder, or click the add button to create a new one.</td></tr><tr><td><strong>Display</strong></td><td><p>How the entry opens: <em><strong>External</strong></em>, <em><strong>Embedded (tabbed)</strong></em>, or <em><strong>Undocked</strong></em>. When <em><strong>External</strong></em> or <em><strong>Undocked</strong></em> is selected, two lists beside it select the monitor and the virtual desktop. The virtual desktop list is not supported on macOS.</p><p>On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</p></td></tr><tr><td><strong>Host</strong></td><td>Where the host of the entry comes from. Select a host mode from the list. When the host comes from a linked host entry, the <em><strong>Host</strong></em> field of the <em><strong>Host and credentials</strong></em> tab is unavailable.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list. When the credentials come from another source, the <em><strong>Username</strong></em>, <em><strong>Domain</strong></em>, and <em><strong>Password</strong></em> fields of the <em><strong>Host and credentials</strong></em> tab are unavailable.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Type</strong></td><td><p>What the session runs:</p><ul><li><strong>Command</strong> — Run the command entered in the <em><strong>Command</strong></em> field.</li><li><strong>Embedded script</strong> — Run a script stored in the entry. Click <em><strong>Edit embedded script</strong></em> to write or modify it. The script cannot be empty.</li><li><strong>Filename</strong> — Run the PowerShell script file selected in the <em><strong>Filename</strong></em> field.</li></ul></td></tr><tr><td><strong>Command</strong></td><td>The PowerShell command to run. Available when <em><strong>Type</strong></em> is set to <em><strong>Command</strong></em>.</td></tr><tr><td><strong>Filename</strong></td><td>The path of the PowerShell script file to run. Click the browse button to select an existing file or to create a new one. Available when <em><strong>Type</strong></em> is set to <em><strong>Filename</strong></em>.</td></tr><tr><td><strong>Edit embedded script</strong></td><td>Open the script editor to write or modify the embedded script. Available when <em><strong>Type</strong></em> is set to <em><strong>Embedded script</strong></em>.</td></tr><tr><td><strong>Arguments</strong></td><td>The arguments passed to the command or script.</td></tr><tr><td><strong>Executable arguments</strong></td><td>Additional arguments passed to the PowerShell executable when the session starts.</td></tr><tr><td><strong>Working directory</strong></td><td>The folder in which the session starts. Click the browse button to select a folder.</td></tr><tr><td><strong>Load RDM CmdLet</strong></td><td>Load the Remote Desktop Manager PowerShell module in the session before the command or script runs.</td></tr></tbody></table>

### Terminal

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Application</strong></td><td><p>The terminal application that hosts the session:</p><ul><li><strong>Default (Windows Terminal)</strong></li><li><strong>Classic</strong></li><li><strong>Windows Terminal</strong></li><li><strong>Let Windows decide</strong></li></ul></td></tr><tr><td><strong>Configuration</strong></td><td>An optional Windows Terminal entry whose profile the session uses. Select an entry to use its profile instead of the default profile configured on your machine. On Windows, click the browse button to pick an entry. Click the clear button to remove the selection. Visible when <em><strong>Application</strong></em> is set to <em><strong>Default (Windows Terminal)</strong></em> or <em><strong>Windows Terminal</strong></em>. The selected entry is saved only when <em><strong>Application</strong></em> is set to <em><strong>Windows Terminal</strong></em>.</td></tr></tbody></table>

### Host and credentials

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Host</strong></td><td>The host name or IP address of the computer. Enter a host or click the browse button to select one. Unavailable when the host comes from a linked host entry.</td></tr><tr><td><strong>Username</strong></td><td>The username used by the session. Unavailable when the credentials come from another source.</td></tr><tr><td><strong>Domain</strong></td><td>The domain of the user. Unavailable when the credentials come from another source.</td></tr><tr><td><strong>Password</strong></td><td>The password of the user. Unavailable when the credentials come from another source, or when the <em><strong>Disable password saving in vaults</strong></em> system setting is enabled.</td></tr></tbody></table>

The tab also lists the variables you can use in your parameters: `$USERNAME$`, `$DOMAIN$`, `$HOST$`, and `$PASSWORD$`.

### Parameters

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Parameter name</strong></td><td>The name of the parameter. Click the name to rename the parameter in a separate window.</td></tr><tr><td><strong>#</strong></td><td>The token that identifies the parameter on the command line, such as <code>{1}</code> for the first parameter.</td></tr><tr><td><strong>Type</strong></td><td><p>Select the parameter type:</p><ul><li><strong>Unused</strong></li><li><strong>Text</strong></li><li><strong>Secured</strong></li><li><strong>Env. variable</strong></li></ul></td></tr><tr><td><strong>Default value</strong></td><td>The default value of the parameter. The value is masked when the type is <em><strong>Secured</strong></em>, and unavailable when the type is <em><strong>Unused</strong></em>.</td></tr><tr><td><strong>Delete</strong> (row button)</td><td>Reset the parameter of the row: its type returns to <em><strong>Unused</strong></em>, its default value is cleared, and its name returns to the default name. Shown when the type is not <em><strong>Unused</strong></em>.</td></tr><tr><td><strong>Add</strong></td><td>Add a parameter at the end of the list.</td></tr><tr><td><strong>Delete</strong></td><td>Remove the last parameter of the list. Available when parameters were added beyond the first five.</td></tr><tr><td><strong>Load</strong></td><td>Read the parameters declared in the script selected on the <em><strong>General</strong></em> tab and add them to the list.</td></tr><tr><td><strong>Prompt for parameters on open</strong></td><td>Prompt for the parameter values each time the session opens.</td></tr></tbody></table>

On macOS and Linux, the parameter names are typed directly in the list, the token is shown to the left of the name, and the ***Add parameter*** button below the list replaces the ***Add*** and ***Delete*** buttons. Hover over a row and click its delete button to clear the parameter.

### Run as

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Run as administrator</strong></td><td>Run the session with administrator privileges. When selected, the credential fields below are unavailable.</td></tr><tr><td><strong>Run as mode</strong></td><td><p>How the session is elevated:</p><ul><li><strong>Default (ShellExecute)</strong></li><li><strong>GSudo</strong></li></ul></td></tr><tr><td><strong>Credentials</strong></td><td><p>The credentials used to run the session:</p><ul><li><strong>None</strong></li><li><strong>Current session</strong></li><li><strong>Username and password</strong> — Enter the <em><strong>Username</strong></em>, <em><strong>Domain</strong></em>, and <em><strong>Password</strong></em>. Select <em><strong>Always ask for password</strong></em> to be prompted for the password instead of saving it.</li><li><strong>Linked</strong> — Select the vault in the <em><strong>Vault</strong></em> list, then select the <em><strong>Credential</strong></em> entry to use. Selecting the user vault from an entry in a shared vault lets you enter the <em><strong>Entry name</strong></em> of a credential entry to find in each user's user vault.</li><li><strong>My personal credentials</strong> — Click the button next to the list to edit them.</li><li><strong>My privileged account</strong> — Click the button next to the list to edit it.</li></ul></td></tr></tbody></table>

### Advanced

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>PowerShell version</strong></td><td><p>The PowerShell version that runs the session:</p><ul><li><strong>Default</strong> — Use the version set in the application settings. The list shows this version in parentheses.</li><li><strong>Windows PowerShell (2.0) [Deprecated]</strong></li><li><strong>Windows PowerShell (5.1)</strong></li><li><strong>PowerShell 7</strong></li></ul></td></tr><tr><td><strong>Threading</strong></td><td><p>The apartment state of the PowerShell thread:</p><ul><li><strong>Default</strong> — Use the value set in the application settings. The list shows this value in parentheses.</li><li><strong>MTA (multithreaded apartment)</strong></li><li><strong>STA (single-threaded apartment)</strong></li></ul></td></tr><tr><td><strong>Command type</strong></td><td><p>How the command is passed to PowerShell:</p><ul><li><strong>Default</strong> — Use the command type set in the application settings. The list shows this command type in parentheses.</li><li><strong>Command</strong></li><li><strong>Encoded command</strong></li><li><strong>Secure command</strong></li></ul></td></tr><tr><td><strong>Prompt mode</strong></td><td><p>Whether PowerShell starts in interactive mode:</p><ul><li><strong>Default (Interactive)</strong> — Neither mode is forced, and PowerShell starts in interactive mode on its own.</li><li><strong>Interactive</strong> — Available with <em><strong>PowerShell 7</strong></em> only.</li><li><strong>Non-interactive</strong></li></ul></td></tr><tr><td><strong>No exit</strong></td><td>Keep PowerShell open after the command or script completes.</td></tr><tr><td><strong>Resize window</strong></td><td>Resize the PowerShell window and buffer to the sizes set in the application settings when the session starts.</td></tr><tr><td><strong>No profile</strong></td><td>Start PowerShell without loading the PowerShell profile.</td></tr><tr><td><strong>No logo</strong></td><td>Hide the PowerShell startup banner.</td></tr><tr><td><strong>Debug</strong></td><td>Display the preparation steps that Remote Desktop Manager runs before the command or script, instead of clearing the console.</td></tr></tbody></table>

### See also

* [PowerShell (RDM CmdLet)](https://docs.devolutions.net/rdm/ribbon-menu-bar/tools/powershell-rdm-cmdlet.md)
* [Use custom Windows terminal over console host in PowerShell session entries](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/use-custom-windows-terminal-over-console-host-in-powershell-session-entries.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/powershell-terminal-local.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
