> 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/v26-ja-jp/parallels-desktop-for-mac-26-yzzugaido/windows-noinsutrumatahainpto/windows-wo-it-kara.md).

# Windows を IT 担当者から入手

Parallels Desktop を動作させるには、任意のオペレーティングシステム（多くの場合は Windows）とアプリケーションを搭載した仮想マシンが必要です。Parallels Desktop for Mac Business/Enterprise Edition を使用している場合、Parallels Desktop の初回起動時に次のような画面が表示されることがあります。

<figure><img src="https://content.gitbook.com/content/jdeysXjAuWf8fiOmc0Q9/blobs/k4UlxwHkMhpKOT7f01wL/image.png" alt=""><figcaption></figcaption></figure>

これは、システム管理者が必要なアプリをすべてインストールした、事前構成済みの仮想マシンを提供していることを意味します。必要な操作は、これをダウンロードするだけです。**\[ダウンロードとインストール]** をクリックし、画面上の指示に従います。仮想マシンの準備が整ったら、自動的に起動され、そのアプリケーションで作業できるようになります。


---

# 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/pdfm-ug/v26-ja-jp/parallels-desktop-for-mac-26-yzzugaido/windows-noinsutrumatahainpto/windows-wo-it-kara.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.
