Zscaler ZDX (Digital Experience): How to verify image integrity before activating
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 Failure |
| 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 ZDX (Digital Experience) 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
Verify image integrity before activating on a Zscaler ZDX (Digital Experience) (Zscaler Cloud (ZIA / ZPA / ZDX)).
Step-by-step
- Copy the image to local flash.
- Run the vendor checksum / md5 command.
- Compare against the checksum published on the vendor portal.
- If mismatched, the image is corrupt. re-download.
CLI / commands
# Boot recovery prompt: Client Connector logs / App Connector service
# Verify image
Admin Portal → Activation
# Upgrade
Cloud-managed; clients (Client Connector / App Connector) update via the cloud
# Save / commit
Activate (Admin Portal upper-right)
# Rollback
Admin Portal → Activation → Revert
Recovery options
- Boot loader recovery (Client Connector logs / App Connector service)
- Rollback to the previous image with
Admin Portal → Activation → Revert - Force failover to a known-good standby (HA platforms)
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: How to verify image integrity before activating
- Zscaler ZIA (SWG/CASB/FWaaS): How to verify image integrity before activating
- Zscaler ZPA (Private Access): How to verify image integrity before activating
- Zscaler ZDX (Digital Experience): How to do an emergency image reload from the boot loader
- 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.
What changed recently?
Fault diagnosis on a Zscaler device goes faster when you map the symptom to a recent change:
- Did firmware update in the last 7 days?
- Did the network (router, ISP, VPN) change?
- Was the device moved physically?
- Did paired devices (phone, hub, app) update?
- Were any accessories swapped in or out?
The answer narrows the root cause to a manageable subset.
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
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.
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.
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.
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.