zms-troubleshoot-agent-deployment

Troubleshoot ZMS agent deployment and connectivity issues via MCP GraphQL operations.

44|24|Updated May 29, 2025
One-click install
npx skills add https://github.com/zscaler/zscaler-mcp-server --skill zms-troubleshoot-agent-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zms-troubleshoot-agent-deployment
Source: https://github.com/zscaler/zscaler-mcp-server/tree/main/skills/zms/troubleshoot-agent-deployment
Command: npx skills add https://github.com/zscaler/zscaler-mcp-server --skill zms-troubleshoot-agent-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Troubleshoot ZSCALER Microsegmentation (ZMS) agent deployment and connectivity issues across the fleet, identifying root causes and guiding remediation.

Core Features & Use Cases

  • Fleet health checks: verify agent status, connection status, and version distribution, and identify disconnected or outdated agents.
  • Agent group and provisioning workflow: validate agent groups, provisioning keys, and enrollment credentials (TOTP secrets) to enable new deployments or re-enrollment.
  • Guided resolution templates: provide step-by-step diagnosis templates and actionable resolutions for common issues (enrollment failures, upgrades, and removal of decommissioned agents).

Quick Start

Describe the problem and initiate the ZMS troubleshooting workflow to isolate and resolve the issue.

Frequently Asked Questions about zms-troubleshoot-agent-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot ZMS agent deployment and connectivity issues?

ZMS agent enrollment failures are diagnosed by validating provisioning keys, checking for key exhaustion, and verifying enrollment credentials like TOTP secrets. The workflow inspects nonces and agent group configurations to pinpoint incorrect or depleted deployment assets.

Why does my ZMS agent report a disconnection or version mismatch?

ZMS agent disconnection or version mismatches occur when agents run outdated software or lose network connectivity. The troubleshooting workflow queries agent version statistics and connection health to identify specific agents requiring upgrades or network remediation.

Do I need a customer ID to diagnose ZMS provisioning key problems?

Yes, you must set the ZSCALER_CUSTOMER_ID environment variable to diagnose ZMS provisioning key problems. This read-only GraphQL workflow requires this identifier to query agent groups, nonces, and enrollment secrets for your specific tenant.

What's the best way to resolve ZMS agent group configuration and key exhaustion?

Resolving ZMS agent group configuration and key exhaustion involves validating existing provisioning keys and regenerating enrollment secrets if depleted. The workflow provides step-by-step resolution templates to correct group assignments and restore deployment capacity.