> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/ja/library-packs/l1-support/dex-checklist.md).

# DEXチェックリスト

## 概要 <a href="#dexchecklist-overview" id="dexchecklist-overview"></a>

DEX スコアチェックリストは、トラブルシューティングプラットフォームから直接、単一デバイスの DEX スコアを簡単に表示します。インストールが完了すると、チェックリストは[デバイスビュー](/platform/ja/user-guide/device-view.md)または[Amplify](/platform/ja/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/configure-amplify.md)でアクセス可能になります。

これらのハイレベルスコアから、サポートエージェントはデバイスの健康状態だけでなく、従業員のデバイスとの全体的な経験も迅速に理解できます。

## 主要な機能 <a href="#dexchecklist-keyfeatures" id="dexchecklist-keyfeatures"></a>

* [Amplify](/platform/ja/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/configure-amplify.md)または[デバイスビュー](/platform/ja/user-guide/device-view.md)から直接DEXスコアを使用してトラブルシューティングを行います。
* DEX スコアを他のデバイス情報と比較する。
* DEX スコアの可視性と使用を向上させる。

## 始めに <a href="#dexchecklist-getstarted" id="dexchecklist-getstarted"></a>

以下のリンクに従ってパックを構成して使用を開始してください。

* [使用ガイド: DEXチェックリスト](/platform/ja/library-packs/l1-support/dex-checklist/usage-guide_-dex-checklist.md)
* [設定ガイド: DEXチェックリスト](/platform/ja/library-packs/l1-support/dex-checklist/configuration-guide_-dex-checklist.md)


---

# 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.nexthink.com/platform/ja/library-packs/l1-support/dex-checklist.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.