Zscaler ZDX (Digital Experience): Upgrade Path to latest LTS / GA
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Vendor | Zscaler |
|---|---|
| Operating system | Zscaler Cloud (ZIA / ZPA / ZDX) |
| Category | Upgrade Paths |
| Skill level | Intermediate to advanced |
| DIY-able? | Yes with CLI access; some scenarios need Zscaler Support + RMA. |
I have run more Zscaler upgrades than I can count and the only ones that hurt are the ones where I skipped image-integrity verification. Zscaler Cloud (ZIA / ZPA / ZDX) either ships a `verify` step or expects you to checksum the file before Cloud-managed; clients (Client Connector / App Connector) update via the cloud.
On the ZDX (Digital Experience) platform the activation phase is where you lose data-plane connectivity. Plan the change window around that window, not the full upgrade duration.
If something goes wrong, the rollback path on Zscaler Cloud (ZIA / ZPA / ZDX) is well-trodden: but only if you saved running-config before starting. Do that now, before anything else.
What this guide covers
Upgrade procedure for Zscaler ZDX (Digital Experience) to latest LTS / GA (Zscaler Cloud (ZIA / ZPA / ZDX)).
Notes specific to this combination
Verify the supported upgrade path in the Zscaler release notes before proceeding. Some Zscaler Cloud (ZIA / ZPA / ZDX) releases require an intermediate hop; some support direct upgrade.
Step-by-step
- Verify current version:
Admin Portal → Activation. - Read the release notes for supported upgrade paths.
- Confirm minimum RAM / disk for the target release.
- Download target image; verify checksum.
- Schedule maintenance window.
- Back up running configuration.
- Copy image to local flash.
- Run
Cloud-managed; clients (Client Connector / App Connector) update via the cloud. - Reboot:
Not applicable, Zscaler is cloud-managed. - Verify;
Activate (Admin Portal upper-right)if healthy.
CLI / commands
Admin Portal → Activation
Admin Portal → Administration → Service Status
Cloud-managed; clients (Client Connector / App Connector) update via the cloud
Activate (Admin Portal upper-right)
Frequently asked questions
Will this work on my specific Zscaler Cloud (ZIA / ZPA / ZDX) version?
The procedure reflects current Zscaler Cloud (ZIA / ZPA / ZDX) behaviour. Older releases may need minor syntax adjustments. use the CLI help (? or tab-completion) to verify.
Should I open a Zscaler Support case immediately?
Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.
Where can I find the Zscaler official documentation?
https://help.zscaler.com, search the product family + feature name.
Is this procedure safe in production?
Test in a lab or maintenance window first. Capture pre-change state so you can roll back.
Related guides
Related fixes
Related guides worth a look while you sort this one out:
- Zscaler ZDX (Digital Experience): Upgrade Path to latest hardening patch
- Zscaler Cloud Firewall: Upgrade Path to latest LTS / GA
- Zscaler ZDX (Digital Experience): How to do an emergency image reload from the boot loader
- Zscaler ZDX (Digital Experience): How to perform a controlled upgrade with rollback safety net
- Zscaler ZDX (Digital Experience): How to recover from a corrupted image during upgrade
- Zscaler ZDX (Digital Experience): How to rollback to the previous image after a failed upgrade
References
- Zscaler support portal: https://help.zscaler.com
- Zscaler knowledge base: https://help.zscaler.com
- Zscaler security advisories: https://trust.zscaler.com
- Open a case: https://help.zscaler.com/submit-ticket
Reference material, not professional advice. Validate against your specific Zscaler Cloud (ZIA / ZPA / ZDX) version and test in a non-production environment before applying.
Common patterns we see
When this symptom shows up on a Zscaler device, three patterns repeat:
1. Recent firmware update changed behavior: the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger, temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear. components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.
Knowing which pattern applies saves time on the wrong fix.
Safety + preconditions
Before any work on a Zscaler device:
- Unplug from mains for any internal-access procedure.
- Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
- Use ESD-safe handling for boards and modules, no carpet, no wool sleeves.
- Avoid moisture; never apply liquids near vents or connectors.
- If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.
Verification checklist
After applying the fix on your Zscaler device, confirm:
- The original symptom is no longer reproducible.
- Related features (status LEDs, app sync, paired accessories) still work.
- The device responds to a soft reboot without the fault returning.
- Any error codes that were on display have cleared.
- Documentation (your service log, the brand companion app) reflects the change.
When to call Zscaler support instead
Escalate if:
- The same symptom returns within 24 hours of a clean fix.
- You see physical damage (burn marks, swollen battery, cracked PCB).
- The device is in warranty and a hardware replacement is the cheaper outcome.
- Repair requires specialised tools you don't own (alignment jigs, calibration software).
- Following the official path keeps the warranty intact, which matters more than the time spent.
More frequently asked questions
Will the procedure work on the international variant?
Some features and firmware paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.
How long does this fix usually take?
Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.
Why is this happening on a brand-new unit?
Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.
What if my model isn't exactly the same revision?
Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.
Is it safe to apply during business hours?
If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.