> 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/file-storage/how-to/how-to-integrate-file-storage-with-remote-desktop.md).

# How to Integrate File Storage into Your Remote Desktop

Find out how to integrate the File Storage service into any user's Remote Desktop environment in 2 steps

By integrating File Storage into the Remote Desktop environment, your users can access their shared files directly from Windows Explorer without leaving the environment.

This is how they save and manage the documents they create in their remote applications in centralized storage.

> #### 👍 What you get
>
> File Storage mounted as a network drive within Remote Desktop, available to the user from Windows Explorer.

### Before you begin

* A subscription to **File Storage** active. If you don't have it yet, set it up with the [Quick Start for File Storage.](https://docs.plenit.com/docs-en/productos/file-storage/quickstart.md)
* An environment of **Remote Desktop** deployed. If you don't already have it, set it up with the [Remote Desktop Quick Start.](https://docs.plenit.com/docs-en/productos/remote-desktop/quickstart.md)
* Have accessed the environment with each user to whom you are going to apply the integration. The user walkthrough is in [How to access your Remote Desktop.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/user-quickstart-guide.md)
* Have the **Windows Explorer** published in the environment and users have visibility over it.

### Step 1. Copy the SMB access URL

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → File Storage** and go to the subscription.

Open the **Customization** and, in the block **SMB**, copy the **URL** it shows. You need it in the next step.

{/\* 📸 SCREENSHOT 1 · Customization › SMB block · highlight the URL field to copy \*/}

![SMB access URL in the Customization tab](https://reemplaza-url/escritorio-remoto-integrar-archivos-01.png)

> #### 📘 The SMB URL and its CNAME
>
> Below the URL field you will see the CNAME configuration, which is what makes a custom URL work. For the integration you only need to copy the SMB access URL.

### Step 2. Mount the network drive inside the environment

Enter the Remote Desktop environment with the user for whom you are configuring the integration. The rest of the process happens within their Windows session.

#### 2.1 Open Windows Explorer

In the **Application Launchpad**section, open the **Windows Explorer** with a double click.

{/\* 📸 SCREENSHOT 2 · Launchpad · Windows Explorer \*/}

![Windows Explorer in the Remote Desktop environment](https://reemplaza-url/escritorio-remoto-integrar-archivos-02.png)

#### 2.2 Open the Map network drive option

In Explorer, go to the subsection **This PC** and, in the menu that appears, select **Map network drive**.

{/\* 📸 SCREENSHOT 3 · Explorer › This PC › Map network drive \*/}

![Map network drive option](https://reemplaza-url/escritorio-remoto-integrar-archivos-03.png)

#### 2.3 Configure the drive

In the window **Map network drive**, fill in:

* **Drive**: the letter or name for the network drive.
* **Folder**: paste the **SMB access URL** you copied in Step 1.

Also check **Reconnect at sign-in** and **Connect using different credentials**, and click **Finish**.

{/\* 📸 SCREENSHOT 4 · Map network drive dialog · highlight Drive, Folder and the two checkboxes \*/}

![Network drive setup](https://reemplaza-url/escritorio-remoto-integrar-archivos-04.png)

> #### 🚧 Check both boxes
>
> **Reconnect at sign-in** keeps the drive available in subsequent sessions, and **Connect using different credentials** is what lets you authenticate with the storage user.
>
> If you don't check them, the drive will not reconnect or you won't be able to enter the correct credentials.

#### 2.4 Enter the credentials

A window opens asking for credentials. Enter the storage user's credentials and click **Accept**.

{/\* 📸 SCREENSHOT 5 · user credentials dialog \*/}

![Credentials entry](https://reemplaza-url/escritorio-remoto-integrar-archivos-05.png)

#### 2.5 Check that the drive appears

Go back to Windows Explorer and verify that the new network drive appears and is accessible.

{/\* 📸 SCREENSHOT 6 · Explorer with the network drive already mounted \*/}

![Network drive mounted in the environment](https://reemplaza-url/escritorio-remoto-integrar-archivos-06.png)

> #### 📘 One drive per user
>
> Repeat Step 2 for each Remote Desktop user who needs access to File Storage. The SMB URL from Step 1 is the same for everyone; what changes are each user's credentials.

### Conclusion

With the network drive mounted, your users work with the centralized storage as if it were just another folder in the environment, directly from Windows Explorer.

The part to pay attention to is Step 2: paste the SMB URL correctly into the Folder field and check both boxes so the drive reconnects and authenticates with the correct credentials.

Once done for each user, access is fixed in their subsequent sessions.


---

# 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.plenit.com/docs-en/productos/file-storage/how-to/how-to-integrate-file-storage-with-remote-desktop.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.
