- Products
- Learn
- Local User Groups
- Partners
- More
Check Point Jump-Start Online Training
Now Available on CheckMates for Beginners!
Why do Hackers Love IoT Devices so Much?
Join our TechTalk on Aug 17, at 5PM CET | 11AM EST
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
ZTNA Buyer’s Guide
Zero Trust essentials for your most valuable assets
The SMB Cyber Master
Boost your knowledge on Quantum Spark SMB gateways!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
I am going to be upgrading our SMS from R80.30 to R81.10. I just recalled that Geo Protection policy changed in R81. Now using updatable objects in an access policy. I have found some info on this here in the community, but I need to know what to expect after my in place upgrade. Will the legacy Geo Policy be gone after my upgrade or will it stay in place since we are leveraging it now. According to the below SK it sounds like it might stay, but I just want to be sure I know what will happen after the upgrade.
The legacy policy is in shared policies
Im pretty sure it will not stay, because I noticed it gone in 3 customer's environments, as well as 2 labs I did.
Can anyone verify for sure what happens after an in place upgrade?
I will let CP people confirm for you, but Im 100% sure thats what happens based on my experience with those upgrades.
When you do an upgrade, if nothing is configured in the legacy Geo Policy, it should be hidden.
If there are rules there, it shouldn’t be hidden on upgrade.
At least that’s how I understand it.
Can confirm what Dameon said, if the legacy Geo Policy is still in its default "out of the box" configuration with no changes made it will be hidden in R81+. If anything was touched at all in the Geo Policy at any point along the way it will still be visible in R81+.
Thats interesting, because thats not my experience at all. With 2 customers, we made changes back in R80.20 in default geo policy, upgraded to R81, all was there, made more changes, then upgraded to R81.10 and default geo policy was gone.
I am using a non default specific policy for Geo Protection currently on R80.30. To be clear, it sounds like this should still be active and available in SmartConsole after my upgrade?
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY