> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/device-management/managing-zoom-clients-and-devices-explainer/troubleshooting.md).

# 疑難排解

Zoom Workplace 應用程式內建工具，可在需要時協助使用者與管理員檢視目前設定並排除 Zoom 裝置管理（ZDM）同步問題。

{% hint style="info" %}
**注意**

請參閱 [使用 Zoom 網路連線工具](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0058114) 文章，以了解更多關於 Zoom Client Healthcheck 的資訊。
{% endhint %}

若要存取 Zoom Client Healthcheck 工具，請使用以下鍵盤快速鍵：

* **Windows：** Ctrl + Alt + Shift + D
* **macOS：** Command + Option + Shift + D

<div data-with-frame="true"><figure><img src="https://2668295848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2FnLZv8DWbJi0i0PGaQasb%2Fimage.png?alt=media&amp;token=28411ffa-91fc-4eef-80d0-65da86e38de9" alt="Sample Zoom Client Healthcheck screen" width="375"><figcaption><p>Zoom Client Healthcheck 範例畫面</p></figcaption></figure></div>

在左側導覽中，按一下 **應用程式設定**。此頁面會顯示目前的 ZDM 註冊狀態、群組詳細資料，以及每項政策如何強制執行。

當用戶端或透過 ZDM 變更政策與設定時，您可以按一下 **重新載入** 按鈕，即可即時驗證更新。

* **裝置名稱：** Zoom Admin portal 中顯示的裝置主機名稱和值。
* **註冊權杖：** 目前設定的註冊權杖。
* **狀態：** 顯示裝置是否已成功註冊至 ZDM（成功）。
* **政策：** 這是一份已強制套用的政策清單、其目前值，以及來源（GPO、ZDM 等）。


---

# 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://library.zoom.com/technical-library/zh-tw/jin-jie-qi-ye-fu-wu/device-management/managing-zoom-clients-and-devices-explainer/troubleshooting.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.