> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/remote-desktop/customization/how-to-customize-the-shortcut.md).

# How to Customize the Remote Desktop Shortcut

If your users always work against the same storage unit, you can make the environment's Windows Explorer open it directly instead of having them browse to it manually every time they save or consult files. This is achieved by adjusting the application arguments.

> #### 👍 What you get
>
> The environment's Windows Explorer opens directly on the unit you choose for all users, without intermediate steps.

### Before you start

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment.
* Have an active Remote Desktop subscription. If you don't already have one, set it up with the [Remote Desktop Quick Start.](/docs-en/productos/remote-desktop/quickstart.md)
* Have the **Windows Explorer** published in the environment.

### Step 1. Open the Windows Explorer application

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and enter the environment subscription. Open the **Applications** tab and go to the application **Windows Explorer**.

{/\* 📸 CAPTURE 1 · Applications · Windows Explorer application \*/}

![Windows Explorer application in Applications](https://REEMPLAZA-URL/escritorio-remoto-explorador-01.png)

### Step 2. Define the unit that opens by default

In the **Arguments**, type `,/ROOT,` followed by the network drive you want to open by default. For example, to have it open drive Z: directly

```shell
,/ROOT,Z:
```

Click **Save** and check that the confirmation message for the change appears.

{/\* 📸 CAPTURE 2 · Arguments field with ,/ROOT,Z: and Save button \*/}

![Explorer Arguments field with the opening drive](https://REEMPLAZA-URL/escritorio-remoto-explorador-02.png)

> #### 📘 Change the letter to your drive
>
> Replace `Z:` with the letter of the drive you use in your environment. If later you want another opening drive, return to this field, edit the letter, save, and validate again.

### Step 3. Validate the behavior

Open the **Applications Launchpad** with any user in the environment and run the **Windows Explorer**. Check that it opens directly in the drive you configured.

{/\* 📸 CAPTURE 3 · Explorer opening in the configured drive \*/}

![Explorer opening in the configured drive](https://REEMPLAZA-URL/escritorio-remoto-explorador-03.png)

### Conclusion

Customizing the Explorer shortcut is a small adjustment with a comfortable effect in daily use: the user opens the application and is already in the correct drive, with no extra clicks.

It all comes down to the Arguments field with `,/ROOT,` and the drive letter. If you change the work drive, just edit that letter and validate again.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/productos/remote-desktop/customization/how-to-customize-the-shortcut.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.