I try a migration from checkpoint 8R0.10.
I've updated to the last bersion (1.1.12) and I see option "VERSION 80.10" in the checkpoint tab, but this option is grayed out.
I try with R80 option but It does nothing after "upload" is clicked.
Do I miss something ?
If you have exported the json formatted files using the method:
If the file config source is from R80.10 you can use the R80 option and the parser will review the file source and determine which parser to use, either the R80 or R80.10.
Can you post a screenshot of the page after you click "upload"
We have not enabled R80.10 because we have found that original Checkpoint config files are missing a lot of address objects that are refereed within groups.
Until we do not find a way to export from Checkpoint a complete configuration set, we do not want to enable a parser that will led to incorrect migrations
@dgildelaig , I noticed a new procedure on the Expedition (Exped 220.127.116.11) file import page for Checkpoint R80 or greater. involves uploading and running a .jar file on the mgmt server. do you have any documentation for the new procedure or is it that simple? Also, how do I explain any risks with running the .jar file on a client's mgmt server?
Check the link we provide to download the jar file.
It is a file provided by Checkpoint, and they explain how to place it in their system and how to consume it.
I guess that if they see the source of the file, they can get some comfort as it is Chekpoint's software to patch Checkpoints software.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!