Zscaler ZPA (Private Access): 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 ZPA (Private Access) 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 ZPA (Private Access) 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 Cloud Firewall: Upgrade Path to the next major release
- Zscaler ZDX (Digital Experience): Upgrade Path to the next major release
- Zscaler ZIA (SWG/CASB/FWaaS): Upgrade Path to the next major release
- Zscaler ZPA (Private Access): How to do an emergency image reload from the boot loader
- Zscaler ZPA (Private Access): How to perform a controlled upgrade with rollback safety net
- Zscaler ZPA (Private Access): How to recover from a corrupted image during 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.
Quick verification
Before you walk away from a Zscaler device fix, run through:
1. Reproduce the original trigger, does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.
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.
More frequently asked questions
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.
Does this affect other devices on my network?
Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.
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.
Will this void my warranty?
Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.