> 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/ras-admin-guide/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi/remote-pc-pools-in-vdi/ras-guest-agent-installation-options.md).

# RAS Guest Agent installation options

To be managed in a Remote PC pool, a Remote PC must have RAS Guest Agent installed. This can be done using one of the following options:

* When you add an individual Remote PC to a pool, you'll be asked to upgrade the agent. Follow the onscreen instructions and install or upgrade it.
* When you add all Remote PCs in a host to a pool at once, you can add them first and then use the **Tasks** > **Upgrade all Agents** menu option in the **Desktops** tab.
* When you assign Remote PCs to a Provider via Active Directory, you can have a Group Policy in the OU with a script to deploy the agent. See [**Configuring the Provider** > **Dynamic (VDI subtype)**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi/remote-pc-pools-in-vdi/adding-remote-pcs-to-a-provider.md).
* To install or upgrade the agent on an individual Remote PC, select it in the **Desktops** tab and click **Tasks** > **Troubleshooting** > **Check agent** option. In the dialog that opens, click **Install**.
* Finally, you can install RAS Guest Agent manually by running the Parallels RAS installer on a Remote PC and selecting to install the RAS Guest Agent component.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi/remote-pc-pools-in-vdi/ras-guest-agent-installation-options.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 `build a script that syncs our docs to a CMS` 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.