topic Re: Upgrading Standalone SMS in Firewall and Security Management

Upgrading Standalone SMS

ma_gorkhali — Wed, 15 Apr 2026 06:21:15 GMT

Hi All,

Planning to upgrade CheckPoint standalone SMS from R81.20 to R82 .

What is the best way to do it ?

Upgrade directly from the GUI or do an advanced upgrade ?

We are managing Maestro + SGW running VSX as well one standalone oepn server.

and also for backup system backup and snapshot I believe should be more than enough ?

Thank You !

Re: Upgrading Standalone SMS

Tal_Paz-Fridman — Wed, 15 Apr 2026 06:34:13 GMT

When you use the term "Standalone SMS" are you referring to a machine that is just a single Security Management Server? Reason I am asking is that the term Standalone also refers to a machine running a Management and a Gateway.

I would start by going over the R82 SK:

https://support.checkpoint.com/results/sk/sk181127

Go to - Downloads and Installation section

I would also follow all the best practices in R82 Installation and Upgrade Guide:

https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_Installation_and_Upgrade_Guide/Content/Topics-IUG/Getting-Started.htm

Re: Upgrading Standalone SMS

simonemantovani — Wed, 15 Apr 2026 06:36:46 GMT

Hello

I spoken with some Check Point PS in the past, and some of them prefer the advanced upgrade; so you'll use migrate export to export all the configuration and database, perform a fresh install of a new management server in R82 and the import everything exported.

But using the CPUSE is more or less the same, because even during the upgrade with CPUSE, a migrate export is performed; in this case you don't have to create a new management server but everything happens in place.

As I told you, some PS prefer Advanced Upgrade; I usually performed upgrade using CPUSE (because in my case, I'm not free to create new VMs to install R82 from scratch) ... If, in your case, is easy to create a new management server in R82 with fresh install then you could follow the Advanced Upgrade procedure (in any case ii could be a good exercise).

Re: Upgrading Standalone SMS

WarrenJ1 — Wed, 15 Apr 2026 06:40:45 GMT

@simonemantovani Have you compared the downtime and rollback options between the Advanced Upgrade and CPUSE methods to determine which approach minimizes risk for your environment?

Re: Upgrading Standalone SMS

the_rock — Wed, 15 Apr 2026 06:47:45 GMT

I usually do it from web UI, just make sure to expect database transfer to take some time.

Re: Upgrading Standalone SMS

Martijn — Wed, 15 Apr 2026 06:54:05 GMT

Hi,

Make sure you are using the latest version of the Deployment Agent and migration tools.
I always perform a verify of the database so I can fix any issues before upgrading.

I would perform an advanced upgrade when the SmartCenter has gone through a lot of upgrades and hotfix installations.
If this is a fresh R81.20 installation with some hotfixes, you can choose to do a CPUSE upgrade.

Martijn

Re: Upgrading Standalone SMS

Vincent_Bacher — Wed, 15 Apr 2026 07:45:22 GMT

I would always and without exception opt for the Advanced Upgrade (using export and import to a new VM created from scratch) and wouldn’t recommend anything else. Especially if you’re running a management system on VMware, it’s the only option in my view.

Re: Upgrading Standalone SMS

ma_gorkhali — Wed, 15 Apr 2026 12:35:28 GMT

Thank you Vincent for replying back. I was told by a PS to do as an advanced upgrade.

Since the new server needs an IP for SSH and file transfer, should I:
- Build it with a temporary IP, perform the import, and then switch to the production IP during cutover?
- Or should the old management server be disconnected from the network from the beginning so I can use the same IP?

What is the recommended approach/best practice?

Thanks in advance.

Re: Upgrading Standalone SMS

ma_gorkhali — Wed, 15 Apr 2026 12:36:09 GMT

It is standalone management server

Also one more thing

Thank you Vincent for replying back. I was told by a PS to do as an advanced upgrade.

What is the recommended approach/best practice?

Thanks in advance.

Re: Upgrading Standalone SMS

simonemantovani — Wed, 15 Apr 2026 12:48:47 GMT

Honestly I never compared the downtime between the two methods; with CPUSE method, if it fails it revert to the previous version (R81.20).

Every time I performed an upgrade, I always performed a VMware snapshot of the management (because it was a virtual server), just to quickly rollback.

In the past I performed an upgrade using CPUSE for an MDS with 17 domains and several thousands of objects and it took about 5 hours to complete the whole procedure (migrate export, upgrade, migrate import).

Re: Upgrading Standalone SMS

ma_gorkhali — Wed, 15 Apr 2026 13:06:51 GMT

Thank You for replying

What is the recommended approach/best practice?

Re: Upgrading Standalone SMS

Vincent_Bacher — Wed, 15 Apr 2026 13:56:06 GMT

This is the procedure I've used reliably across multiple customer environments during my history at solution providers. It keeps your production environment untouched until the very last step.

Preparation

Perform a migrate export on the production management system, then implement a change freeze (using the pre-upgrade verifier, etc.).
If not already in place, create a dummy VLAN (switches) in VMware, running completely separate from the production environment.
Copy all necessary packages to a Windows VM + transfer the migrate export from the production Check Point management to this VM + install SmartConsole on the VM.
Connect this Windows VM to the dummy VLAN, configure an IP from the same management subnet as the management interface of the Check Point management.

Build & Validate the New Management Server

Create a new VM for the new Check Point management system, connect it to the dummy VLAN.
Run the First Time Wizard and use the same attributes/configurations as in production.
Install Jumbo HFA and, if necessary, the private hotfix.
Connect to the management system using SmartConsole from the Windows VM.
If this works, close SmartConsole and transfer the migration export to the new management system.
Perform migrate import.
Reconnect to SmartConsole and visually check the policy packages.

Cutover to Production

At a suitable time, either shut down the production management system or disconnect the network connection of the management interface.
Change the network connection of the management interface from the new management server to the production VLAN.
Reconnect to SmartConsole, perform a visual check, test policy installation, test logs – the usual checks.

Tip: The beauty of this approach is that you build and validate everything in an isolated environment first. Production stays untouched until step 12, and your rollback is simply powering the old management back on.

I hope that helps, and I hope my memory hasn’t let me down, because at my current workplace, a colleague always does this in collaboration with Check Point PS, and I haven’t done it myself for a while.

Re: Upgrading Standalone SMS

Oliver_Fink — Wed, 15 Apr 2026 14:42:11 GMT

I think, that is the best way to do it.

But if you do not want to build a twin VLAN, this is what I would do:

Get 2 additional IPs (IPb and IPc) in the SMS LAN with actual SMS (IP: IPa).

Set up a new SMS on IPc.
Verify with Migration Tools on old SMS (IPa).
Fix problems on Old SMS (IPa).
Export with Migration Tools on old SMS (IPa).
Transfer data to new SMS (IPb)
Import with Migration Tools on new SMS (IPb).
Do some Tests on new SMS (IPb). Maybe try "Install Database" in SmartConsole after you changed the IP of the SMS object to IPb. DO NOT INSTALL POLICIES! But you should see the state of the VSes in SmartConsole. Remember to change IP of SMS obejct back to IPa before next steps.
On old SMS (IPa) do "fw logswitch; cpstop" to rotate actual log away from "fw.log" to log with time stamp.
Change old SMS (IPa) to a new IP (IPc).
Change the new SMS (IPb) to a new IP (IPa).
Do an "Install Database" in SmartConsole if you changed it in Step 7. It is not wrong to do that in any case.
I would recommend to install all Policies step by step to the VSes with intensive testing.
If errors occur you can still switch back to the old SMS with switching new SMS back to IPb and old SMS back to IPa.
Otherwise transfer logs from old SMS (IPc) to new SMS (IPa) if you do not use separate log servers.
Initiate log indexing following sk111766 and undo the settings if indexing is finished.
Delete the old SMS (IPc) after some days if everything works fine.

Re: Upgrading Standalone SMS

Vincent_Bacher — Wed, 15 Apr 2026 14:58:23 GMT

Exactly. But setting up a new VLAN/Switch in vCenter is just a matter of a few clicks. It doesn’t need to be accessible from the outside, so there’s nothing else to do. You just use the VMs via the VMware console. 😊

But of course, your to-do list is spot on. 👍

Re: Upgrading Standalone SMS

PhoneBoy — Wed, 15 Apr 2026 16:47:05 GMT

It's safe to perform the import on a system with a different IP.
Nothing will change on gateways until policy is pushed.

Re: Upgrading Standalone SMS

ma_gorkhali — Tue, 19 May 2026 12:38:01 GMT

@Oliver_Fink what if I am using the same IP for both old and new Security Management Server ?

After I export the database can I disable the network for the Active SMS from Vmware interface and then bring the network up on new Management Server with same IP. After that import the database and also add in the license ? Does it work in that way ?

Re: Upgrading Standalone SMS

PhoneBoy — Tue, 19 May 2026 17:38:56 GMT

When you do a migrate export, it includes the license, which is tied to the original IP.
If you migrate import to a different host/VM with the same IP, the existing license will work.