自此版本起，access-wizard 會將啟動程序節點設定、控制平面初始化、控制平面部署、Access 和基礎結構服務部署，以及租用戶建立等步驟整合為單一引導式命令並自動執行。精靈會提示您回答一組簡短的問題、產生所需的組態檔，然後依序執行各個部署階段。如果您偏好個別執行這些步驟，請參閱手動部署 Omnissa Access。
**附註：**Access Wizard 26.07 支援綠地部署 Omnissa Access 26.07.0.0。更新現有部署及部署後續版本不在此版本的支援範圍內。
如果您已備妥所需的 IP 位址、憑證和其他資訊，完成問題回答大約需要幾分鐘。之後的自動化部署約需 1.5 至 2 小時。
開始之前
開始之前，請確認下列事項：
- 階段 1 - 準備用於安裝 Omnissa Access 的虛擬機器和階段 2 - 部署 Omnissa Access 安裝所需的虛擬機器中所述的啟動程序節點、基礎結構和 Omnissa Access 虛擬機器均已部署並開啟電源。
- 已依照使用負載平衡器或反向 Proxy 來啟用 Omnissa Access 的外部存取中的說明設定負載平衡器，並已啟用 X-Forwarded-For 標頭且接聽連接埠 443。
- 租用戶 FQDN (例如
tenant.example.com) 的 DNS 可解析至負載平衡器的 IP 位址。 - 您已取得在 OVA 部署期間於每個節點上設定的
configuser密碼。如果此密碼已到期或需要重設，請參閱管理 Omnissa Access Control Plane 叢集節點。 - 您已備妥 TLS 憑證，可以是自我簽署憑證 (精靈可為您產生)，或是由您自己的 CA 簽發且包含完整鏈結的 PEM 憑證，以及與其相符且未加密的私密金鑰。
附註：
- 精靈會驗證啟動程序節點上的磁碟空間和 Docker 儲存區，並檢查與其他每個節點之間的 SSH 連線能力和驗證。精靈不會另外驗證遠端節點的 CPU、RAM 或磁碟配置大小，因此開始之前，請依據階段 1 - 準備用於安裝 Omnissa Access 的虛擬機器中的規模配置表進行確認。
- Access Wizard RPM 已進行數位簽署。驗證簽章 (請參閱下方的信任簽署金鑰並驗證 RPM) 與下一節中的 SHA-256 總和檢查驗證是兩項不同的檢查；總和檢查只能確認下載內容未損毀，無法確認該檔案確實來自 Omnissa。
下載並驗證 Access Wizard
操作程序：
-
登入 Omnissa Customer Connect 並下載：
- Omnissa Access 資產服務包 (包含控制平面資訊清單和容器映像的 ZIP 檔案)。
- Access Wizard RPM 服務包 — 其中包含三個項目的 ZIP 檔案：RPM (
access-wizard-26.07.noarch.rpm)、其.sha256總和檢查檔案，以及 Omnissa RPM 簽署公開金鑰 (omnissa-linux-rpm-gpg-key.pub)。
-
在本機機器上解壓縮 RPM 服務包 (或將其複製到啟動程序節點後再解壓縮 — 請參閱下一節)：
unzip <wizard-bundle>.zip -
使用服務包中包含的
.sha256檔案驗證 RPM，並使用已發佈的總和檢查驗證資產服務包：sha256sum -c access-wizard-26.07.noarch.rpm.sha256 sha256sum <asset-bundle>.zip如果任一值不相符，請勿繼續。
將檔案上傳至啟動程序節點
操作程序：
-
將兩個 ZIP 檔案複製到啟動程序節點：
scp <wizard-bundle>.zip <asset-bundle>.zip \ configuser@<bootstrap-ip>:/home/configuser/ -
以
configuser身分連線至啟動程序節點，並解壓縮 RPM 服務包：ssh configuser@<bootstrap-ip> unzip <wizard-bundle>.zip在此程序的其餘步驟中，請保持以
configuser身分登入。後續所有命令都會明確使用sudo。
信任簽署金鑰並驗證 RPM
操作程序：
-
匯入 Omnissa RPM 簽署公開金鑰 (請從解壓縮 RPM 服務包的目錄中執行)。
sudo rpm --import omnissa-linux-rpm-gpg-key.pub -
驗證 RPM 的簽章和完整性：
sudo rpm -K access-wizard-26.07.noarch.rpm輸出必須顯示有效的摘要和簽章。如果驗證失敗，請勿安裝 RPM。
安裝 RPM
操作程序：
sudo dnf install -y access-wizard-26.07.noarch.rpm
已安裝的套件身分識別資訊為 access-wizard-26.07-1.noarch。
確認安裝
操作程序：
sudo access-wizard --version
預期的輸出：
access-wizard 26.07
開始引導式部署
操作程序：
sudo access-wizard deploy --asset-bundle /<path>/<asset-bundle>.zip
精靈會顯示歡迎畫面，其中列出六個問題區段 (基本資訊、租用戶、基礎結構節點、Access 節點、憑證、選用服務)，然後提示您按 Enter 開始。
● OMNISSA ACCESS — Deployment Wizard
Official documentation
• Release Notes
- https://docs.omnissa.com/bundle/workspace-one-access-release-notesV26.07/page/workspace-one-access-release-notes.html
• Install Omnissa Access
- https://docs.omnissa.com/bundle/workspace-one-access-installation-guideV26.07/page/InstallingOmnissaAccess.html
• Deploy Access & Infrastructure
- https://docs.omnissa.com/bundle/workspace-one-access-installation-guideV26.07/page/DeploytheOmnissaAccessandInfrastructureServices.html
View or copy all official documentation URLs: sudo access-wizard docs
-------------------------------------------------------------
Omnissa Access - guided deployment
-------------------------------------------------------------
This wizard asks what it needs, writes your config files, and runs
the deployment in the right order. If a step doesn't validate, it
stops and tells you what to look at rather than pressing on.
There are 6 sections of questions.
The deployment itself takes about two hours. If your connection
drops during it, reconnect and run:
sudo access-wizard resume
It continues from the last completed deployment stage without asking the
questionnaire again.
1. Basic information
2. Tenant
3. Infrastructure nodes
4. Access nodes
5. Certificates
6. Optional services
Press Enter to begin.
第 1 節：基本資訊
-
檢閱
https://www.omnissa.com/general-terms/上的 EULA，並接受其條款。============================================================= Section 1 of 6: Basic information ============================================================= ------------------------------------------------------------- License agreement ------------------------------------------------------------- Before anything else, please read and accept the end user license agreement. Review it at https://www.omnissa.com/general-terms/ Do you agree to these terms? [Y/n]: EULA accepted <acceptance-timestamp> -
確認精靈自動找到的資產服務包。精靈會依據已發佈的總和檢查驗證其完整性。
------------------------------------------------------------- Asset bundle verification ------------------------------------------------------------- ✓ Asset integrity <verification-detail> -
選擇叢集名稱。此名稱會決定工作目錄路徑
/opt/wss/<cluster_name>。------------------------------------------------------------- Cluster ------------------------------------------------------------- Choose a short name for this deployment. The wizard creates /opt/wss/<cluster_name>. This becomes the working directory for future WSO administration and maintenance commands. What would you like to call this cluster?: <cluster_name> Working directory will be /opt/wss/<cluster_name> Your answers are saved to /opt/wss/<cluster_name>/wizard.ini -
選擇部署大小 — 小型、中型或大型。精靈會顯示每個選項的節點拓撲。
What size deployment is this? Every deployment uses 3 Infrastructure nodes. The number of Access nodes and supported scale depend on the deployment size. 1) Small 2 Access nodes 300,000 users 3,000 groups 50 apps 2) Medium 2 Access nodes 1,000,000 users 10,000 groups 150 apps 3) Large 3 Access nodes 1,000,000 users 20,000 groups 500 apps Choose 1-3: 1 ✓ Deployment size Small Topology: 3 Infrastructure + 2 Access nodes -
確認偵測到的啟動程序節點 IP 位址。
------------------------------------------------------------- This node ------------------------------------------------------------- This looks like the Bootstrap node, with IP address <bootstrap-ip>. Is that right? [Y/n]: Y -
輸入共用的
configuser密碼。精靈會立即針對啟動程序節點驗證該密碼。如有需要，請參閱管理 Omnissa Access Control Plane 叢集節點以重設此密碼。------------------------------------------------------------- Credentials ------------------------------------------------------------- The credentials the cluster uses to reach every node. This is the configuser password you already set when you deployed the OVA. Not a new one. It must be the same on every node. Enter the configuser password:******** Enter it again to confirm:******** Validating configuser authentication on Bootstrap (<bootstrap-ip>)... configuser password validated against Bootstrap. -
選擇叢集向其他節點進行驗證的方式：使用您剛輸入的密碼，或使用已產生的 SSH 金鑰配對。
-
密碼
How should the cluster authenticate to the Infrastructure and Access nodes? 1) password use the password you just entered 2) ssh_key generate a key and copy it to every node Choose 1-2: 1 -
ssh_key
How should the cluster authenticate to the Infrastructure and Access nodes? 1) password use the password you just entered 2) ssh_key generate a key and copy it to every node Choose 1-2: 2
-
-
輸入負載平衡器 IP 位址；如果您的部署適用，也請輸入 X-Forwarded-For IP 位址。精靈會檢查連接埠 443 的連線能力。
------------------------------------------------------------- Load balancer ------------------------------------------------------------- The load balancer sits in front of your Access nodes. It should already be configured with X-Forwarded-For headers enabled. You'll add the Access nodes as upstreams once they're deployed. What is the load balancer IP address: <load-balancer-ip> Checking... Load balancer <load-balancer-ip> port 443 reachable ------------------------------------------------------------- X-Forwarded-For trusted proxies ------------------------------------------------------------- The load balancer and Access node IPs are included automatically. Enter only additional trusted proxy, WAF, CDN, or other forwarding-hop IPs. Do you need to add any additional IPs for X-Forwarded-For? [y/N]: y Additional trusted IP: <trusted-proxy-ip> Added <trusted-proxy-ip> Add another trusted IP? [y/N]: n Section 1 complete.
第 2 節：租用戶
輸入租用戶前置詞和基本網域 — 使用者可透過 https://<tenant-name>.<base-domain> 存取部署。精靈會檢查該 FQDN 是否解析至負載平衡器 IP 位址，然後提示您輸入租用戶管理員的使用者名稱 (預設為 admin)、名字、姓氏和電子郵件地址。
=============================================================
Section 2 of 6: Tenant
=============================================================
Now configure the tenant your users will sign in to.
Load Balancer URL: https://tenant.acme.example.com
Tenant: tenant
Base domain: acme.example.com
What should the tenant be called: <tenant-name>
What is the base domain: <base-domain>
Users will reach this deployment at:
https://<tenant-name>.<base-domain>
Checking DNS...
<tenant-name>.<base-domain> resolves to <load-balancer-ip>
Matches the load balancer.
-------------------------------------------------------------
Tenant administrator
-------------------------------------------------------------
The first administrator account for this tenant.
What should the administrator's username be? [admin]: admin
Administrator's first name: <first-name>
Administrator's last name: <last-name>
Administrator's email address: <administrator-email>
Section 2 complete.
第 3 節：基礎結構節點
輸入 3 個基礎結構節點各自的 IP 位址。您輸入每個節點時，精靈都會檢查 SSH 連線能力，並對該節點進行驗證。不允許使用重複的位址。
=============================================================
Section 3 of 6: Infrastructure nodes
=============================================================
Every deployment uses 3 Infrastructure/Platform nodes, regardless
of size.
These run the platform services (Vault, Consul, Nomad) and the
shared infrastructure: PostgreSQL, Redis, Kafka, and OpenSearch.
What is the IP address of Infrastructure node 1: <infra-ip-1>
What is the IP address of Infrastructure node 2: <infra-ip-2>
What is the IP address of Infrastructure node 3: <infra-ip-3>
Checking SSH reachability and authentication on each Infrastructure node...
✓ Infrastructure node 1 <infra-ip-1> reachable and authenticated
✓ Infrastructure node 2 <infra-ip-2> reachable and authenticated
✓ Infrastructure node 3 <infra-ip-3> reachable and authenticated
All 3 Infrastructure nodes are reachable and authenticated.
Section 3 complete.
第 4 節：Access 節點
輸入每個 Access 節點的 IP 位址 (小型或中型部署為 2 個，大型部署為 3 個)。精靈會檢查每個節點的連線能力和驗證。
=============================================================
Section 4 of 6: Access nodes
=============================================================
Your small deployment uses 2 Omnissa Access nodes.
These run the Access application services and sit behind your load
balancer. Platform services also run here.
What is the IP address of Access node 1: <access-ip-1>
What is the IP address of Access node 2: <access-ip-2>
Checking SSH reachability and authentication on each Access node...
✓ Access node 1 <access-ip-1> reachable and authenticated
✓ Access node 2 <access-ip-2> reachable and authenticated
All 2 Access nodes are reachable and authenticated.
Section 4 complete.
第 5 節：憑證
選擇 Access 用於租用戶 FQDN 的 TLS 憑證：
- 自我簽署 — 在部署期間自動產生。
- 自訂 — 將您自己的 PEM 憑證和私密金鑰上傳至啟動程序節點。精靈會驗證憑證鏈結、金鑰是否相符，以及憑證是否涵蓋租用戶 FQDN。
-
自我簽署
============================================================= Section 5 of 6: Certificates ============================================================= Access needs a TLS certificate for <tenant-name>.<base-domain>. What certificate should Access use? 1) self-signed generated for you during deployment 2) custom your own certificate from a CA Choose 1-2: 1 Section 5 complete. -
自訂
============================================================= Section 5 of 6: Certificates ============================================================= Access needs a TLS certificate for <tenant-name>.<base-domain>. What certificate should Access use? 1) self-signed generated for you during deployment 2) custom your own certificate from a CA Choose 1-2: 2 ------------------------------------------------------------- What you need ------------------------------------------------------------- Two files, both PEM format: Certificate complete chain, with the server certificate first, followed by any intermediate CA certificates; the file starts with -----BEGIN CERTIFICATE----- Private key text file starting with -----BEGIN PRIVATE KEY----- or -----BEGIN RSA PRIVATE KEY----- It must not be encrypted or password protected. The certificate must cover <tenant-name>.<base-domain>, as the Common Name or a Subject Alternative Name. A wildcard (*.<base-domain>) also works. Upload both to this node. From your workstation: scp mycert.pem mykey.pem configuser@<bootstrap-ip>:/home/configuser/omnissa-upload/ I've created /home/configuser/omnissa-upload for you. Where are your certificate files? 1) Already uploaded to this node 2) Not yet, I'll upload now - wait for me 3) Actually, use a self-signed certificate instead Choose 1-3: 1 Checking /home/configuser/omnissa-upload... <mycert>.pem <size> KB certificate <mykey>.pem <size> KB private key Found a certificate and key. Use these? [Y/n]: Y Checking the certificate... Format PEM certificate Covers <tenant-name>.<base-domain> (via wildcard *.<base-domain>) Issued by <Issuer> Valid until <date> (<> days from now) Key match yes Certificate accepted. Both files will be copied into place when deployment starts. Section 5 complete.
第 6 節：選用服務
共有四個選用項目：SMTP、NTP、NFS 共用儲存區，以及適用於 Android 版行動 SSO 的 Cert-Proxy。在任何 [y/N] 提示中回答 n，即可暫緩設定該項目。部署完成後，可使用 access-wizard configure 再次設定這四個項目。
**附註：**啟動程序節點會驗證您輸入之 NTP 伺服器的 DNS 名稱解析。
=============================================================
Section 6 of 6: Optional services
=============================================================
Four optional items. All can be configured later if you'd rather
get the deployment running first.
-------------------------------------------------------------
Email (SMTP)
-------------------------------------------------------------
Access sends email for password resets, notifications, and new
user invitations. Without it, the administrator can still sign in
using the reset link created at the end of this deployment, but no
other user will receive email.
Configure SMTP now? [y/N]: n
-------------------------------------------------------------
Time synchronization (NTP)
-------------------------------------------------------------
Cluster nodes need their clocks in sync. Certificate validation and
token expiry both depend on it, so drift causes authentication
failures that are hard to trace.
Do you have an NTP server? [y/N]: n
-------------------------------------------------------------
Shared storage (NFS)
-------------------------------------------------------------
Optional shared storage for the cluster.
Do you have NFS storage to configure? [y/N]: n
-------------------------------------------------------------
Cert-Proxy (Mobile SSO for Android)
-------------------------------------------------------------
Cert-Proxy enables Mobile SSO for Android devices.
It can be configured later if you skip it now.
Configure Cert-Proxy (Mobile SSO for Android)? [y/N]: y
Which certificate should Cert-Proxy use?
1) Reuse the Load Balancer certificate selected above (recommended)
2) Use a different certificate and private key
Choose 1-2: 1
Section 6 complete.
檢閱並確認
完成全部六個區段後，精靈會顯示您所有回答的完整摘要。
=============================================================
Ready to deploy
=============================================================
CLUSTER
Name <cluster_name>
Working directory /opt/wss/<cluster_name>
Size small
Bootstrap <bootstrap-ip>
Load balancer <load-balancer-ip>
Credentials configuser (password set)
Authentication SSH key
password used for initial key distribution
Asset bundle <asset-bundle>.zip
EULA <verification-detail>
TENANT
URL https://<tenant-name>.<base-domain>
Username <username>
Administrator <first-name> <last-name>
Email <administrator-email>
INFRASTRUCTURE NODES
Node 1 <infra-ip-1>
Node 2 <infra-ip-2>
Node 3 <infra-ip-3>
ACCESS NODES
Node 1 <access-ip-1>
Node 2 <access-ip-2>
X-FORWARDED-FOR TRUSTED HOPS
Load balancer <load-balancer-ip>
Access nodes <access-ip-1>, <access-ip-2>
Additional trusted IPs <trusted-proxy-ip>
Final trusted list <load-balancer-ip>, <access-ip-1>, <access-ip-2>, <trusted-proxy-ip>
CERTIFICATE
Type custom
Covers <tenant-name>.<base-domain> (via wildcard *.<base-domain>)
Expires <date>
OPTIONAL
Cert-Proxy enabled (FQDN_CERT)
SMTP not configured
NTP not configured
NFS not configured
-------------------------------------------------------------
This takes roughly 1.5 to 2 hours:
Loading images 5 minutes
Control plane deploy 30-60 minutes
Services deploy 40 minutes
Tenant creation 5-10 minutes
You don't need to stay at the terminal. Progress is shown here
and written to /opt/wss/.omnissa-wizard/logs/
At the end you'll get a password reset link for the
administrator account. It expires in 24 hours, so be ready to
copy it.
Everything above has been saved to /opt/wss/<cluster_name>/wizard.ini
If you stop now, nothing has been changed on any node.
-------------------------------------------------------------
Is everything above correct?
1) Yes, continue to validation
2) No, let me change something
3) Exit without deploying
Choose 1-3:
選擇 1 以繼續進行驗證、選擇 2 以修改設定，或選擇 3 以結束而不進行部署。
Is everything above correct?
1) Yes, continue to validation
2) No, let me change something
3) Exit without deploying
Choose 1-3: 1
接著，精靈會顯示最終的就緒狀態摘要，並提示您開始部署。
-------------------------------------------------------------
Deploying
-------------------------------------------------------------
✓ Workflow continuation protected from SSH disconnects
-------------------------------------------------------------
Stage 1 of 7 - Validate prerequisites
-------------------------------------------------------------
Checking this Bootstrap node before making deployment changes.
✓ Root privileges running as root
✓ Required commands all available
✓ Node authentication 6 nodes verified (password)
✓ Bootstrap <bootstrap-ip> AlmaLinux 9.6
✓ Infrastructure 1 <infra-ip-1> AlmaLinux 9.6
✓ Infrastructure 2 <infra-ip-2> AlmaLinux 9.6
✓ Infrastructure 3 <infra-ip-3> AlmaLinux 9.6
✓ Access 1 <access-ip-1> AlmaLinux 9.6
✓ Access 2 <access-ip-2> AlmaLinux 9.6
✓ Node OS validation 6 nodes running AlmaLinux 9.6
✓ Asset bundle located access-26.07-assets.zip
✓ Asset bundle structure manifest and Linux CLI found
✓ Working-directory disk space 132 GB available
✓ Docker storage 44 GB available at /var/lib/docker
✓ Disconnect protection systemd transient services
✓ Cluster node connectivity 5/5 answering on SSH
✓ Load balancer port 443 <load-balancer-ip> reachable
✓ Tenant certificate files certificate and key available
Pre-deployment readiness
✓ Bootstrap authenticated · <boostrap-ip>
✓ Infrastructure nodes 3/3 authenticated
✓ Access nodes 2/2 authenticated
✓ Node addresses unique and validated
✓ Configuration ready for deployment
1) Start deployment
2) Review or change configuration
3) Re-enter the shared configuser password
4) Exit safely
Choose 1-4:
部署階段
精靈會自動執行下列七個階段。請保持終端機工作階段開啟，以監控進度。
| 階段 | 名稱 | 執行內容 |
|---|---|---|
| 1 | 驗證先決條件 | root 權限、必要命令、節點驗證、作業系統驗證、資產服務包完整性、磁碟空間、負載平衡器檢查 |
| 2 | 準備部署資產 | 工作目錄、資產服務包暫存與解壓縮、CLI 安裝、容器映像載入 |
| 3 | 初始化叢集 | 叢集組態、SSH 金鑰散佈 (如果已選取)、叢集詳細目錄、控制平面設定檔 |
| 4 | 驗證叢集 | 組態預先檢查、詳細目錄驗證 |
| 5 | 部署控制平面 | Vault、Consul、Nomad 和平台服務；平台健全狀況驗證 |
| 6 | 部署 Access 服務 | Access 設定檔、組態同步、所有 Access 應用程式服務、服務就緒檢查點 |
| 7 | 建立租用戶 | 租用戶建立、重設連結交付、SMTP 組態 (如果已選取) |
-------------------------------------------------------------
Stage 1 of 7 - Validate prerequisites
-------------------------------------------------------------
✓ Root privileges running as root
✓ Required commands all available
✓ Node authentication 6 nodes verified (password)
✓ Node OS validation 6 nodes running <supported-os>
✓ Asset bundle located <asset-bundle>.zip
✓ Asset bundle structure manifest and Linux CLI found
✓ Working-directory disk space <nn> GB available
✓ Docker storage <nn> GB available at <docker-root>
✓ Disconnect protection systemd transient services
✓ Cluster node connectivity 5/5 answering on SSH
✓ Load balancer port 443 <load-balancer-ip> is listening
✓ Tenant certificate self-signed selected
OK All prerequisites passed
-------------------------------------------------------------
Stage 2 of 7 - Prepare deployment assets
-------------------------------------------------------------
✓ Working directory /opt/wss/<cluster_name>
✓ Asset bundle staged ...
✓ Asset bundle extracted ...
✓ WSO CLI installed /usr/bin/wso
✓ EULA acceptance recorded by the CLI
▓ Loading images <elapsed>
✓ Container images loaded and verified
-------------------------------------------------------------
Stage 3 of 7 - Initialize the cluster
-------------------------------------------------------------
✓ Cluster initialization cp-cluster / <size>
✓ Cluster inventory 5 nodes across 12 groups
✓ Control Plane profile generated defaults retained
-------------------------------------------------------------
Stage 4 of 7 - Validate the cluster
-------------------------------------------------------------
• Optional Control Plane precheck skipped
✓ Cluster inventory validated
-------------------------------------------------------------
Stage 5 of 7 - Deploy the Control Plane
-------------------------------------------------------------
▓ Control Plane deployment <elapsed>
✓ Control Plane deployed
✓ Platform health Vault, Consul, and Nomad healthy
-------------------------------------------------------------
Stage 6 of 7 - Deploy Access services
-------------------------------------------------------------
✓ Access profile written
✓ Access configuration synced to Vault and Consul
✓ <service-1> deployed
✓ <service-2> deployed
...
✓ <service-47> deployed
✓ Access services 47/47 · 100%
✓ Service readiness all services READY
-------------------------------------------------------------
Stage 7 of 7 - Create the tenant
-------------------------------------------------------------
▓ Tenant creation <elapsed>
✓ Tenant created successfully
如果連線中斷或您中斷精靈
resume 命令會從上一個已完成的部署階段繼續執行。仍然有效的已完成工作會略過，先前已儲存的問題回答也不會再次要求輸入。
- **在回答問題期間：**按 Ctrl+C，然後執行
resume，即可還原您已儲存的回答。 - **監控受保護的部署階段時：**按 Ctrl+C 只會中斷終端機連線。不會停止部署。即使 SSH 工作階段中斷，受保護的階段仍會繼續執行。
無論是哪一種情況，若要檢查進度或繼續執行，請重新連線並執行：
sudo access-wizard status
sudo access-wizard resume
租用戶建立與完成
接近第 7 階段結束時，畫面上會顯示一次性密碼重設連結。**立即複製該連結，因為連結會在 24 小時後到期，且不會寫入任何記錄檔。**儲存連結後，輸入 CONTINUE。
=============================================================
COPY THIS NOW - the link expires in 24 hours
=============================================================
Login URL https://<tenant-name>.<base-domain>
Username admin
Reset your password at:
<one-time-reset-link>
如果在回答問題期間已設定 SMTP，此時 Omnissa CLI 會以安全方式提示您輸入 SMTP 服務帳戶密碼。
SMTP uses a secure password prompt from the Omnissa CLI.
Enter SMTP Password: ********
✓ SMTP configured
部署完成後，精靈會顯示完成摘要，其中包含部署總時間、租用戶 URL、管理員使用者名稱、叢集名稱和節點數量。如果在回答問題期間略過任何選用項目，尚待完成一行會列出日後需要設定的項目。
---------------------------------------------------------------
Deployment complete
---------------------------------------------------------------
✔ All done - total time: <elapsed>
Tenant URL https://<tenant-name>.<base-domain>
Administrator admin
Cluster <cluster_name>
Nodes 3 Infrastructure, 2 Access
Still outstanding:
SMTP is not configured. Run: sudo access-wizard configure
PLATFORM ACCESS
From /opt/wss/<cluster_name>/cp-cluster/cp-cluster.env
Nomad https://<nomad-ip>:4646
Consul https://<consul-ip>:8501
Vault https://<vault-ip>:8202
Administrative tokens are stored in the protected environment file:
/opt/wss/<cluster_name>/cp-cluster/cp-cluster.env (root-only, mode 600)
To display tokens securely:
sudo access-wizard show-tokens
Logs from this run are in: /opt/wss/.omnissa-wizard/logs/
進行疑難排解時，也可以直接從節點讀取相同的值，而不必透過 show-tokens 取得：
sudo cat /opt/wss/<cluster_name>/cp-cluster/cp-cluster.env
部署後
檢查狀態：
sudo access-wizard status
---------------------------------------------------------------
Progress
---------------------------------------------------------------
Cluster <cluster_name>
Tenant <tenant-name>.<base-domain>
done Prerequisite validation
done Working directory preparation
done Deployment asset preparation
done Workspace ONE configuration
done Cluster initialization
skipped SSH key configuration
done Cluster configuration
done Control Plane profile
skipped Control Plane precheck
done Cluster inventory validation
done Control Plane deployment
done Platform health validation
done Access profile preparation
done Access configuration synchronization
done Access services deployment
done Service readiness
done Tenant creation
done SMTP configuration
All phases complete.
顯示平台權杖 (部署後不會自動顯示 Nomad、Consul 和 Vault 權杖)：
sudo access-wizard show-tokens
需要使用互動式終端機。出現提示時，輸入 REVEAL。
設定 SMTP、NTP、NFS 或 Cert-Proxy。access-wizard configure 命令只能在部署完成後執行。此命令會依序引導您設定全部四個項目，並針對每個項目顯示 [y/N] 提示。回答 n 可保留該設定不變：
[root@ng-bootstrap wss]# access-wizard configure
Full session log: /opt/wss/.omnissa-wizard/logs/session-20260807-220226-configure.log
-------------------------------------------------------------
Optional configuration
-------------------------------------------------------------
Configure the optional settings you need. Answer no to leave a
setting unchanged and continue to the next one.
Configure SMTP? [y/N]: n
Configure NTP? [y/N]: n
Configure NFS? [y/N]: n
Configure Cert-Proxy (Mobile SSO for Android)? [y/N]: n
-------------------------------------------------------------
Configuration complete
-------------------------------------------------------------
SMTP unchanged
NTP unchanged
NFS unchanged
Cert-Proxy unchanged
如果 Omnissa 要求您傳送診斷資料，請收集支援服務包：
sudo access-wizard support-bundle
此命令會將記錄、組態和環境詳細資料建立為經敏感資訊遮蔽處理的封存檔，並寫入 /opt/wss/.omnissa-wizard/。傳送前請先檢閱其內容。
其他命令：access-wizard 也提供 credentials、verify-control-plane、docs 和 deploy --dry-run 選項。執行 access-wizard --help 可查看完整的使用方式。
如果服務在部署期間失敗
如果第 6 階段 (部署 Access 服務) 回報某項服務的健全狀況不良，您可以在不重新啟動整個部署程序的情況下進行復原：
-
檢查停滯的階段或服務：
sudo access-wizard status -
根據狀態顯示的資訊，決定後續處理方式：
-
如果控制平面部署狀態為
running，請勿嘗試繼續執行。請改為向 Omnissa 支援提交支援票證，並附上支援服務包：sudo access-wizard support-bundle -
如果控制平面部署狀態為
done，且狀態中未明確指出任何特定失敗項目，請使用下列命令繼續執行：sudo WIZ_CP_REDEPLOY=yes access-wizard resume此命令會從健全狀況驗證開始，接著執行 Access 設定檔，然後執行 Access 服務。
-
如果控制平面部署狀態為
done，且狀態輸出指出特定 Access 服務失敗 (顯示為 X/47)，請先解決該服務的問題：-
開啟 Nomad UI，找出失敗的工作並將其清除 (停止並移除，而不只是重新啟動)。
-
從啟動程序節點的叢集工作目錄中，只重新部署該項服務：
cd /opt/wss/<cluster_name> wso services deploy -s <service-name>**附註：**僅部署自動化流程期間失敗的服務。
-
該服務成功重新部署後，請繼續執行精靈：
sudo access-wizard resume
依序部署的服務清單：
control-plane-logging host-logging telegraf-statsd telegraf-asset-server ingress ingress-gateway-route-reloader control-plane-backup client-side-load-balancer telegraf-uptime cp-ops-dispatch cp-ops-output-processor kafka kafka-monitoring postgres postgres-monitoring pgbouncer postgres-backup postgres-diff-backup postgres-operations postgres-operations-vacuum redis redis-monitoring opensearch coredns eecache nginx-http acs crypto cds token analytics saas federation authcontrol greenbox ws1notifications ws1ntfmanager skycap cas certproxy commchannel launcher ws1admin hubconsole mpsso nginx-stream usergroup -
-
只要服務進入異常狀態，此項處理即適用，不僅限於初始部署期間。完成部署後或升級期間，也可以使用相同的復原流程。
此頁面對您有幫助嗎?