> 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/how-to-articles/run-as-another-user/manual-runas.md).

# Manual RunAs

{% hint style="info" %}
This article describes the manual method of using RunAs. Some types support built-in RunAs details are available. See [Run as another user](https://docs.devolutions.net/rdm/kb/how-to-articles/run-as-another-user/built-in-runas/).
{% endhint %}

### Settings

#### Scenarios

There are two major scenarios when using RunAs: the authentication server is accessible directly from you machine or you need delayed authentication.

* #### Authentication server is locally accessible

This scenario is for when you are already authenticated on a domain/workgroup and you need to switch to another account of the same domain/workgroup.

* #### Delayed Authentication

This scenario is for when it is impossible to log on your machine using the other set of credentials. For example you need to connect to a client's domain using your laptop that is on your company's domain. This will require using the /NETONLY parameter of RunAs.

#### Examples

The RunAs command is invoked from an entry of the ***Command line*** type. Create the entry either by pressing the Insert key or by using the menus. Select the ***Command line*** type and enter a name for it.

#### Example 1: Running a command prompt as another user of the same workgroup/domain

1. You can use the ellipsis button to browse for the runas.exe command, but if you are in a Team workspace and the session is used on various operating systems, it is better to type in "**%systemroot%\system32\runas.exe**" because it will work on all of them.
2. Append /user:$DOMAIN$$USERNAME$, keeping it outside of the quotes. Note the use of two variables that will pull the appropriate value from other fields of the same session.
3. Append the name of the executable you want to run. Enclose it in quotes if the full path contains spaces. In our case we can simply add ***CMD***.

   <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4573.png" alt=""><figcaption></figcaption></figure>
4. Specify your credentials in the ***Host and Credential*** tab. Note that when you are not part of a domain, you should enter the computer name in the domain field.

   <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4574.png" alt=""><figcaption></figcaption></figure>
5. In the ***Events*** tab you must define a typing macro.
   * Set the Initial Delay to the lowest value that will allow the initial prompt to appear. On most systems 1 second is sufficient.
   * In the ***Typing macro*** field, enter the following: $PASSWORD${ENTER}.

     <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4575.png" alt=""><figcaption></figcaption></figure>
6. In the ***Security Settings*** tab, you must check ***Allow password in variable***. When you run your session, a command prompt window appears requesting the password for the user. The Typing Macro will fill it in after the 1 second delay. After this, the command window that is running under the different credentials appears. Note that the title indicates the other identity.

<figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4576.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4577.png" alt=""><figcaption></figcaption></figure>

#### Example 2: Running SQL Server Management Studio as a user of a different domain/workgroup for using Windows Authentication

There are minor differences with Example 1, but here is the full procedure to make it easy to read.

{% hint style="info" %}
Note that most of our entries now support NetOnly as a built in feature.
{% endhint %}

1. You can use the ellipsis button to browse for the runas.exe command, but if you are in a Team workspace and the session will be used on various operating systems, it is better to type in "**%systemroot%\system32\runas.exe**" because it will work on all of them.
2. Append /netonly /user:$DOMAIN$$USERNAME$, keeping it outside of the quotes. Note the use of two variables that will pull the appropriate value from other fields of the same session. Also note the use of the NetOnly parameter, it signals that the credentials will be used for network access only.
3. Append the name of the Management Studio executable and its parameters. All this needs to be within the same double quotes
   * SQL Server Management studio is located at **C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe** on most machines, adapt to your situation if it is not the same.
   * My parameters look like this: -S sql.windjammer.loc -E -S is for the server name, -E is to use windows authentication, you can even specify the database using -d **DB\_NAME** (i.e. -d rdm).

The result is **C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe -S sql.windjammer.loc -E**.

4. Uncheck ***Use Shell Execute*** (this must be done for most Windows Applications)

   <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4578.png" alt=""><figcaption></figcaption></figure>
5. Specify your credentials in the ***Host and Credential*** tab. Note that when you are not part of a domain, you should enter the computer name in the domain field.

   <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4579.png" alt=""><figcaption></figcaption></figure>
6. In the Events tab you must define a typing macro.
   * Set the Initial Delay to the lowest value that will allow the initial prompt to appear. On most systems 1 second is sufficient.
   * In the Typing macro field, enter the following: $PASSWORD${ENTER} For more information please consult Auto Typing Macro.

     <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4580.png" alt=""><figcaption></figcaption></figure>
7. In the advanced tab, you must check Enable password in variable. Run the session and wait for Management studio to appear, attentive users will notice that it looks like you are running under your local credentials because of these. A simple query will prove that it worked, perform a SELECT SUSER\_NAME() query.

   <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4581.png" alt=""><figcaption></figcaption></figure>

   <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4582.png" alt=""><figcaption></figcaption></figure>

   <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB4583.png" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/run-as-another-user/manual-runas.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.