- Products
- Learn
- Local User Groups
- Partners
- More
Maestro Masters Series 2026
WATCH NOWI am currently preparing an upgrade plan for a customer to migrate Maestro from R81.10 to R82. After reviewing several upgrade cases, I am concerned about the possibility of unexpected issues during the process.
I am considering splitting the upgrade into three phases (SMS → MHO → SG), with more than one week between each phase.
Would this approach be feasible?
I would greatly appreciate any recommendations or best practices you could share.
Thank you in advance for your guidance.
Hi,
The three phase approach is a good one. You should do that!!
Upgraded a Maestro environment from R81.10 to R82 last year and followed the steps described in the R82 Maestro Installation and Upgrade guide. The steps are very well described and easy to follow.
Preperation is very important. Make sure you have all the software downloaded. Hotfixes, Deployment Agent etc. Also make sure you are on the correct hotfix for R81.10 before upgrading. All is in the Upgrade guide.
On MHO's disk space can be an issue, so follow:
sk182325 - Importing a CPUSE package on Maestro Orchestrator fails with "There is not enough disk sp...
Before upgrading make sure you have backups and snapshots created. An Auto-snapshot will be created when upgarding to R82.
And make sure Implied Rules are enabled. In the past I had some issues with a policy install during the sp_upgrade script procedure. Maybe caused by Implied Rules not being enabled. Since enabling Implied Rules during the upgrade, I had no issues.
Good luck!!
Martijn
I don't have best practices as we don't use scalable platform devices such as 64k or Maestro anymore.
But i would say this approach is correct.
The only additional point I would consider is doing a clean install on the devices because of the move from the "special" scalable platform release R81.10SP to the "universal" release R82.
If we choose to perform the upgrade using a clean installation, wouldn’t the existing configuration and data be lost?
Or is it possible to use the command from SK174202 —
set maestro export local orchestrator — to create a backup on R81.10, and then import it after upgrading to R82?
tbh i am not sure, maybe other mates can answer this question better.
But from my end the mentioned sk is feasible.
It's not a QA'd or supported upgrade method for MHOs.
There was that webinar yesterday I found quite useful.
Hi,
The three phase approach is a good one. You should do that!!
Upgraded a Maestro environment from R81.10 to R82 last year and followed the steps described in the R82 Maestro Installation and Upgrade guide. The steps are very well described and easy to follow.
Preperation is very important. Make sure you have all the software downloaded. Hotfixes, Deployment Agent etc. Also make sure you are on the correct hotfix for R81.10 before upgrading. All is in the Upgrade guide.
On MHO's disk space can be an issue, so follow:
sk182325 - Importing a CPUSE package on Maestro Orchestrator fails with "There is not enough disk sp...
Before upgrading make sure you have backups and snapshots created. An Auto-snapshot will be created when upgarding to R82.
And make sure Implied Rules are enabled. In the past I had some issues with a policy install during the sp_upgrade script procedure. Maybe caused by Implied Rules not being enabled. Since enabling Implied Rules during the upgrade, I had no issues.
Good luck!!
Martijn
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 8 | |
| 5 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY