- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Device Diagnostics?
Dec 2nd @ 5pm CET / 11am EST
AI Security Masters
Security in the Pace of AI:
From Threat to Force Multiplier
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
Check Point Named a Leader
The Forrester Wave:
Enterprise Firewall Solutions, Q4 2026
What’s New in Agentic Network Orchestration
CheckMates Go:
Fun Ding
Hello community,
We are trying to upgrade CheckPoint Secure Management Seerver from R81 (and R81.20) to R82.
When we run migrate export, Upgrade report shows warning about verifying the Site to Site VPN Encrytion Domain per Community (screenshot attached). Upgrade report shows same warning with R81, and with R81.20. We have folowed solution with Jumbo Hotfix Accumulator, with no luck.
We have multiple clients with multiple Site to Site VPN tunnels, and as in sk170857 we do not prefer to change as suggested in immediate workaround (VPN Community : According to gateway).
We have tried migrate export with skip warnings in lab environment, it executes with success, and import is succesfull.
I am wondering if anyone have faced this or similar issues or how to resolve it.
Any help appreciated,
Regards,
The warning does not indicate that you would face any immediate issues after the upgrade. First, you need to check if you are even using EDCP in the first place. If yes, proceed with extra care.
But if you are already running one of the mentioned versions:
you should not expect any issue at all.
To be on the safe side,
Actually, what we did is we used Jumbo Hotfix Accumulator for R81 Take 107. We will try to use Take 99, and check upgrade report again. For R81.20 we have to check which Take was used.
We did upgrade an R81.20 SMS to R82 today with advanced upgrade (migrate_server) and don't see adverse impacts on VPN, they all use custom encryption domains.
Probably a general warning in the verifier.
Hi Alex,
Just for info, when you did upgrade from R81.20 SMS, did you have to run migrate export with --ignore_warnings flag, or it completed succesfully without it?
Regards
Yes, using the flag was necessary.
In this case, it is already included in the higher Take version
Note the SK states that the fix is actually if you're not in the versions where the behaviour is addressed.
We had the same warning, I believe it is meant to be more of a "BTW" notice. Every single one of my IPsec VPNs use granular encryption domains and we had zero issues with IPsec VPNs after the upgrade.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 7 | |
| 7 | |
| 6 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
Tue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaThu 26 Nov 2026 @ 10:00 AM (CET)
The Cloud Architects Series: Cloud Security State in 2026 – Lessons Learned and a Look AheadWed 02 Dec 2026 @ 02:00 PM (CET)
E-Mail-Agent-Hijacking: E-Mail-Sicherheit im Zeitalter der KI neu überdenkenWed 02 Dec 2026 @ 02:00 PM (GMT)
Why Email Agent Hijacking Marks the End of Post-Delivery Email SecurityWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 02:00 PM (CET)
E-Mail-Agent-Hijacking: E-Mail-Sicherheit im Zeitalter der KI neu überdenkenWed 02 Dec 2026 @ 02:00 PM (GMT)
Why Email Agent Hijacking Marks the End of Post-Delivery Email SecurityWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseWed 02 Dec 2026 @ 11:00 AM (PST)
Why Email Agent Hijacking Marks the End of Post-Delivery Email SecurityAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION