Upgrade Paths

Zscaler ZIA (SWG/CASB/FWaaS): Upgrade Path to latest LTS / GA

Q: Where can I find the Zscaler official documentation?

https://help.zscaler.com — search the product family + feature name.

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance

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.

Image upgrades on Zscaler platforms have one cardinal rule: verify the running image first. `Admin Portal → Activation` on Zscaler Cloud (ZIA / ZPA / ZDX) is the single most useful command in a change window because it tells you exactly what you are rolling back to if something breaks.

Across the ZIA (SWG/CASB/FWaaS) family the upgrade syntax is `Cloud-managed; clients (Client Connector / App Connector) update via the cloud`: pay attention to the activation step because Zscaler Cloud (ZIA / ZPA / ZDX) treats download and activate as separate transactions. Forgetting the activation step is the single most common reason an 'upgrade' silently does nothing.

Zscaler Support expects you to capture pre-upgrade state and have a console session open during the change window. Anything less is a support-case waste of time if it goes sideways.

What this guide covers

Upgrade procedure for Zscaler ZIA (SWG/CASB/FWaaS) 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.

All Zscaler fix guides → /zscaler/
All vendor guides → /vendors/

Related guides worth a look while you sort this one out:

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.

Escalation guide

For a Zscaler device, the right escalation depends on impact:

Cosmetic / minor: log a ticket via the Zscaler app or web portal. Response 1-3 business days.
Mid-impact: phone support. Have your serial number ready.
Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
Out of warranty: third-party repair shop with manufacturer-certified technicians.