Forcepoint: How to check device end-of-life / end-of-support date
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Vendor | Forcepoint |
|---|---|
| Operating system | Forcepoint NGFW / Security Manager Console |
| Category | Warranty / RMA / Support |
| Skill level | Intermediate to advanced |
| DIY-able? | Yes with CLI access; some scenarios need Forcepoint Customer Hub + RMA. |
What this guide covers
How to check device end-of-life / end-of-support date in the Forcepoint support ecosystem.
Step-by-step
- Sign in to https://support.forcepoint.com
- Navigate to End-of-Life / End-of-Sale notices.
- Search the product code.
- Note: End-of-Sale, End-of-Software-Maintenance, End-of-Vulnerability-Service, End-of-Hardware-Support.
- Plan refresh before End-of-Hardware-Support.
Useful URLs
- Support portal: https://support.forcepoint.com
- Open a case: https://support.forcepoint.com
- Bug / advisory search: https://support.forcepoint.com
- Knowledge base: https://support.forcepoint.com
- Security advisories (PSIRT): https://www.forcepoint.com/trust/security-advisories
- Warranty lookup: https://www.forcepoint.com/legal
Frequently asked questions
Will this work on my specific Forcepoint NGFW / Security Manager Console version?
The procedure reflects current Forcepoint NGFW / Security Manager Console behaviour. Older releases may need minor syntax adjustments. use the CLI help (? or tab-completion) to verify.
Should I open a Forcepoint Customer Hub 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 Forcepoint official documentation?
https://support.forcepoint.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
- All Forcepoint fix guides → /forcepoint/
- All vendor guides → /vendors/
Related fixes
Related guides worth a look while you sort this one out:
- Forcepoint: How to check warranty / support contract status
- Forcepoint: How to check security advisories for your product
- Forcepoint: How to collect tech-support / diagnostic bundle
- Forcepoint NGFW N1100 vs Check Point: How to Choose
- Forcepoint NGFW N120 vs Check Point: How to Choose
- Forcepoint NGFW N2100 vs Check Point: How to Choose
References
- Forcepoint support portal: https://support.forcepoint.com
- Forcepoint knowledge base: https://support.forcepoint.com
- Forcepoint security advisories: https://www.forcepoint.com/trust/security-advisories
- Open a case: https://support.forcepoint.com
Reference material, not professional advice. Validate against your specific Forcepoint NGFW / Security Manager Console version and test in a non-production environment before applying.
Common patterns we see
When this symptom shows up on a Forcepoint: 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.
Before you start
A few things to confirm so the Forcepoint: 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.
Quick verification
Before you walk away from a Forcepoint: 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.
When to call Forcepoint: 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
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.
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.
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.
How often should I run preventive checks?
Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.