> 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/configure-the-remote-microsoft-management-console-mmc-using-dhcpmgmt.md).

# Configure the remote Microsoft Management Console (MMC) using dhcpmgmt

Configure a Command Line entry in Remote Desktop Manager to run the remote Microsoft Management Console using dhcpmgmt.msc.

You can configure an MMC snap-in console to run on any of your servers. The snap-in needs to support remote access.

### Settings

1. Open Remote Desktop Manager.
2. Create a new entry.
3. In Macros/Scripts/Tools, select the ***Command Line*** entry type.
4. Name the session DHCP.
5. Under the ***General*** tab, in the ***Run*** field, type *dhcpmgmt.msc /ComputerName $HOST$* ($HOST$ is the variable that will be replaced by the server name or IP address).
6. Under the ***Advanced*** tab, enable ***Run as Administrator***.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If you are running a Windows 64-bit edition, enable <em><strong>Run in 64-bit mode</strong></em> as well.</p></div>
7. Click ***Add*** to save your entry.
8. Verify that your sessions use the appropriate credentials to run the tool. In the ***Management Tools – Tools*** section of each session, make sure you have selected the proper credentials to be supplied.

| Option                  | Description                                                                                                                                            |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Use default credentials | Use the credentials from the Windows session.                                                                                                          |
| Use session credentials | Use the same credentials as the session.                                                                                                               |
| Username and password   | Username, domain and password can be entered manually.                                                                                                 |
| Linked (vault)          | Specify a set of credentials from a specific vault.                                                                                                    |
| My personal credentials | Use [***My Personal Credentials***](/rdm/ribbon-menu-bar/file/my-account-settings/my-personal-credentials.md) set in ***File – My account settings***. |
| Inherited               | [Inherits credentials](/rdm/concepts/intermediate-concepts/inheritance.md) from a higher level entry.                                                  |
| Prompt for credentials  | Prompts for the credentials on use.                                                                                                                    |
| My privileged account   | Use ***My Privileged Account*** set in ***File – My account settings***.                                                                               |

#### Snaps-ins

1. To run snap-ins, select your session and execute the Command Line entry type (DHCP) from the dashboard under ***Macros/Scripts/Tools***.
2. Execute Windows run.
3. Type Microsoft Management Console (MMC) and press enter.
4. Go to ***File - Add/Remove Snap-in.***
5. Select the snap-ins and click OK.


---

# 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/how-to-articles/configure-the-remote-microsoft-management-console-mmc-using-dhcpmgmt.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.