> 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/pdfm-ug/v20-zh-cn/parallels-desktop-for-mac-20-yong-hu-zhi-nan/zai-mac-shang-shi-yong-windows/cong-windows-da-yin.md).

# 从 Windows 打印

默认设定 Windows 与 macOS 使用相同的打印机。只需照常在 Windows 应用程序中进行打印即可。

{% hint style="info" %}
**注意**：由于 macOS Sonoma 14 发生变化，在 Sonoma 主机 Mac 上运行的 Parallels Desktop 19 中的打印功能将发生变化，具体变化将在 Sonoma 正式发布后反映在本指南中。
{% endhint %}

您还可以将 Windows 设置为使用不同的打印机。要在 Windows 中设置打印，参见如下方法：

* 共享任何与 Mac 连接的打印机。
* 连接网络打印机。
* 直接将 USB 打印机连接到 Windows。


---

# 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/pdfm-ug/v20-zh-cn/parallels-desktop-for-mac-20-yong-hu-zhi-nan/zai-mac-shang-shi-yong-windows/cong-windows-da-yin.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.