> 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-best-practices-guide/introduction.md). # Introduction Parallels® Remote Application Server (Parallels RAS) is an application delivery and virtual desktop solution. It extends Microsoft Windows Remote Desktop Services by providing centralized and simplified management, universal printing, and highly available load balanced remote access solution to Windows Terminal Services based applications and desktops from any device, anywhere. Traditionally, application delivery and VDI solutions were challenging to set up and manage. Design and implementation could take weeks or even months to complete. In contrast, Parallels RAS can be installed in days or even hours, providing a quicker return on your investment and an easier path to realizing the benefits of remote desktop computing. This guide is intended for system administrators responsible for installing and configuring Parallels RAS. The guide assumes that the reader is familiar with such Microsoft services as Active Directory, DNS, DHCP, Terminal Servers/Remote Desktop Session Hosts and has an intermediate networking knowledge. --- # 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-best-practices-guide/introduction.md?ask=&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.