> 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/zoom-node/zoom-node-deployment-field-guide/getting-started-with-zoom-node.md).

# Zoom Node 入門

從此處開始了解 Zoom Node 部署，包括部署前檢查清單。

本《實地指南》為技術團隊、管理員與決策者提供必要的先決條件與驗證步驟，並提供單一且具權威性的參考資料，協助您在 Zoom 混合式服務中實現最佳效能、安全性與功能運用。

遵循我們的部署指引，貴組織即可透過穩健的混合式通訊平台，充分發揮 Zoom 基礎架構投資的價值。

Zoom 實地指南包含各種具體指示、參考資料等內容，協助貴組織充分運用 Zoom 產品與服務。檢閱這些資料將協助您：

* **降低部署風險**：透過全面的部署前驗證，避免部署失敗
* **最佳化資源**：從試行階段到企業級規模，依實際需求調整基礎架構投資
* **加快 Zoom Node 就緒進度**：透過明確且可執行的需求，縮短導入時程
* **打造面向未來的架構**：建立可支援持續擴展的混合式服務組合的基礎

### <mark style="color:藍色;">使用此檢查清單，確認您已做好部署前準備</mark>

建立妥善的管理基礎，有助於順利部署及持續管理。繼續之前，請先確認已完成以下事項：

**基礎架構準備**

* [ ] 已部署 Hypervisor 平台，並確認可存取管理介面
* [ ] 已依照服務需求配置 VM 資源
* [ ] 已驗證網路連線（確認未受 Hypervisor NAT 干擾）

**網路架構**

* [ ] 已為所有規劃中的服務保留並記錄 IP 位址
* [ ] 已建立 DNS 項目並確認可透過公用 DNS 解析
* [ ] 已針對 Zoom 雲端 IP 範圍設定防火牆規則

**安全性與法規遵循**

* [ ] 已選定憑證策略（Auto PKI 或自備憑證 \[BYOC]）
* [ ] 已設定正確的 SAN 項目（若使用 BYOC）
* [ ] 已完成憑證驗證

**管理準備**

* [ ] 自訂 URL 已獲得以下單位核准： [Zoom 支援](https://support.zoom.com/hc/en/contact?id=contact_us)
* [ ] 已確認可存取 Zoom 帳戶的管理員權限
* [ ] 已依需求啟用服務專屬功能


---

# 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/zoom-node/zoom-node-deployment-field-guide/getting-started-with-zoom-node.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.
