> 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/v22-ja-jp/session-recording-experimental/session-recording-playback.md).

# セッション録画の再生

「セッション録画の再生」アプリケーションは、次の 2 つの方法のいずれかで起動できます。

**Windows の \[スタート] メニューから：**

1. Windows の **\[スタート]** メニューを開きます。
2. **すべてのアプリ** > **Parallels** の順に選択します。
3. **セッション録画再生** を選択します。

**RAS 管理コンソールから：**

1. RAS 管理コンソールで、**ファーム** > **設定** の順に選択します。
2. **機能** タブを選択します。
3. **セッション録画** をダブルクリックします。
4. **保存場所** で、表示したい録画が含まれている保存場所を選択し、その \[プロパティ] パネルを開きます。
5. **コンテンツを再生** をクリックして、セッション録画再生アプリケーションを起動します。


---

# 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/v22-ja-jp/session-recording-experimental/session-recording-playback.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.