> 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/v21-en-us/parallels-ras-21-administrators-guide/remote-pcs/overview.md).

# Overview

In addition to RD Session Hosts, Virtual desktops, and Azure Virtual Desktop, resources can also be published from a standalone Remote PC running a [supported version of Windows](/landing/ras-admin-guide/v21-en-us/parallels-ras-21-administrators-guide/installing-parallels-ras/system-requirements/software-requirements.md). A Remote PC can be a physical box or a virtual machine treated as a physical PC, but typically they are physical computers. If you have virtual machines on your network, it makes sense to use them as part of the VDI infrastructure as described in the [**VDI and Virtual Desktops**](/landing/ras-admin-guide/v21-en-us/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi.md) chapter. However, if you don't need the guest VM cloning functionality or, for example, if your end users require full administrative permissions on a PC for customization, you can use a virtual machine as a Remote PC.

{% hint style="info" %}
**Note:** Remote PCs can also be combined into pools and managed as pool members. Remote PC pools use the RAS VDI infrastructure and work differently than individual Remote PCs described in this chapter. For more information see [**Remote PC pools**](/landing/ras-admin-guide/v21-en-us/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi/remote-pc-pools-in-vdi.md).
{% endhint %}

This chapter describes how to add a Remote PC to a Farm and how to publish remote applications and desktop from it.


---

# 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/ras-admin-guide/v21-en-us/parallels-ras-21-administrators-guide/remote-pcs/overview.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.