> 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-universal-printing-best-practices/v19/introduction.md). # Introduction Printing is a vital component of any office environment. Printing can be as simple as connecting a printer to a computer and installing a driver, but it can easily become a complex task with many variables. This is especially true for modern office environments that have adopted the Microsoft Remote Desktop Services infrastructure. IT administrators in such environments are faced with the need to ensure normal usage of local printers, especially when people are using virtual applications and remote desktops. Printing while using RDS has proven to be a challenge to many enterprises whose IT administrators tend to struggle to provide the technology that can adequately deliver on printing demands created by virtualization and mobile deployments. This is because users can only print through RDS if the same set of drivers is installed on both a local device and a terminal server. Problem is, many printer drivers simply do not function in a Terminal Services environment, so the few available technologies became nonviable. Furthermore, ensuring that terminal servers contain a copy of every printer driver used throughout the entire organization is a major management headache that proves to be very taxing on IT administrators and, consequently, affects the organizations themselves. Parallels® Remote Application Server offers a variety of features that enable administrators to successfully integrate printing in every deployment scenario. By choosing the most appropriate printing configuration for their organization, IT administrators can significantly improve and simplify the user experience when it comes to printing. --- # 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-universal-printing-best-practices/v19/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 `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.