> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/common-management-tasks/improving-virtual-machine-and-application-performance.md).

# Improving virtual machine and application performance

Windows 10 and Windows 11 contain many applications, services, and background tasks that are not optimized for use in virtual desktop environments. You can improve the user experience and decrease virtual machine boot times, sign-in times, and application start-up times by running the Microsoft Virtual Desktop Optimization Toolkit (VDOT) on your Golden Image.

To start VDOT:

1. Sign in to Parallels DaaS Management Portal.
2. Select the **Golden Image** category.
3. &#x20;Click the **Edit** button to start the virtual machine. Once the Golden Image virtual machine starts, open a browser in the VM and go to<https://github.com/The-Virtual-Desktop-Team/Virtual-Desktop-Optimization-Tool>

&#x20;4\. Click the **Code** menu and select **Download ZIP**.

<figure><img src="https://342210427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2FhOsVSzu3vAb61Uku5M%2Fuploads%2Ff1mTLQcRnZkntx2kxMkD%2Fimage001.png?alt=media&amp;token=11d9e7fd-d712-4d7f-99ec-742fecf27119" alt="Code menu on GitHub"><figcaption></figcaption></figure>

5. Create a folder (ex. "C:\VDOT").
6. Unblock the downloaded .zip file, either manually using **File** > **Properties**, or using the [Unblock-File](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/unblock-file?view=powershell-5.1) PowerShell command.
7. Extract the VDOT download to the folder you created (ex. "C:\VDOT").
8. Start an elevated PowerShell prompt.
9. In PowerShell, change the directory to the folder that contains scripts (ex. "C:\VDOT").
10. Run the following PowerShell commands:

{% code overflow="wrap" %}

```powershell
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process
```

{% endcode %}

This allows PowerShell script execution but only as long as the app is open.&#x20;

{% code overflow="wrap" %}

```powershell
.\Windows_VDOT.ps1 -Optimizations All -AdvancedOptimizations RemoveOneDrive -Verbose -AcceptEULA -Restart
```

{% endcode %}

This will run every VDOT optimization with verbose output, automatically accept the EULA, and restart the device.

11. Once the machine reboots, reconnect and save your Golden Image.

You can find the full documentation and advanced parameters at <https://github.com/The-Virtual-Desktop-Team/Virtual-Desktop-Optimization-Tool?tab=readme-ov-file>


---

# 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.parallels.com/landing/daas-guides/daas-administrators-guide/common-management-tasks/improving-virtual-machine-and-application-performance.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.