Zscaler ZIA (SWG/CASB/FWaaS): Upgrade Path to the next major release
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 ZIA (SWG/CASB/FWaaS) 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 ZIA (SWG/CASB/FWaaS) to the next major release (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 ZIA (SWG/CASB/FWaaS): How to do an emergency image reload from the boot loader
- Zscaler ZIA (SWG/CASB/FWaaS): How to perform a controlled upgrade with rollback safety net
- Zscaler ZIA (SWG/CASB/FWaaS): How to recover from a corrupted image during upgrade
- Zscaler ZIA (SWG/CASB/FWaaS): How to rollback to the previous image after a failed upgrade
- Zscaler ZIA (SWG/CASB/FWaaS): Upgrade Path to latest hardening patch
- Zscaler ZIA (SWG/CASB/FWaaS): Upgrade Path to latest LTS / GA
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.
Why this matters for your day-to-day
A Zscaler device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.
Before you start
A few things to confirm so the Zscaler device fix goes cleanly:
- Latest firmware downloaded if you're going to update.
- Warranty + support contract status checked. opening sealed parts may void it.
- Backup of current configuration (where applicable) taken.
- Spare parts on hand if you anticipate replacement.
- Adequate workspace, lighting, and time, rushing causes regressions.
How to confirm it's actually fixed
On a Zscaler device, the test is rarely "reboot and see". Use this list:
- Active reproduction: trigger the original failure path on purpose.
- Indirect reproduction: do an activity that would expose the same subsystem.
- Status indicator review: every LED / display / app status should be green.
- 24-hour soak: leave the device under normal load overnight; check the next morning.
- Telemetry check: review the device or app's diagnostic log for new error entries.
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
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.
Can I roll this back if something breaks?
Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.
Are there safer alternatives for non-technical users?
Yes: the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.
Should I update firmware first or last?
Update firmware first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.