> 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/gao-ji-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 客户端健康检查的更多信息。
{% endhint %}

要访问 Zoom 客户端健康检查工具，请使用以下键盘快捷键：

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

<div data-with-frame="true"><figure><img src="https://2325962437-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 客户端健康检查屏幕示例</p></figcaption></figure></div>

在左侧导航中，单击 **应用设置**。此页面将显示当前 ZDM 注册状态、群组详细信息以及各项策略的强制执行方式。

当客户端上的策略和设置通过 ZDM 发生更改时，您可以单击 **重新加载** 按钮，以在右上角实时验证更新。

* **设备名称：** Zoom 管理员门户中显示的设备主机名和值。
* **注册令牌：** 当前配置的注册令牌。
* **状态：** 显示设备是否已成功注册到 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/gao-ji-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.