Best Practices Question

Migrating from physical KACE SMA v7.2.103 to virtual SMA 9.0.2. Best practice?

10/02/2018 1363 views
We currently have a physical SMA appliance which is a few versions behind (7.02.103) and are going to upgrade to the 9.02 VIRTUAL appliance.  Has anyone done this?  What lessons learned would you care to share?

We also have an option to just greenfield this as we haven't invested a lot of effort into the SMA physical appliance up to now.  The only gotcha I can see is that we have the old Agents deployed.  Any ideas or opinions on this approach?

0 Comments   [ + ] Show comments


All Answers

At first:
You cannot upload the backup in another version.

The first step would be:
Update the agents to 7.2 at least:
Go to Settings | Provisioning |Update Agents and upload the 7.2 agent bundle and enable Auto Update.
This will update the agents step by step when they check in next time. Do not go further until you got rid off all agents older than 7.0!

The second step: collect the license key from the old appliance. 
The third step: do a full backup, verify that it works
The fourth step: Update the old appliance as high as possible (I assume you are using an old G11 appliance, so 8.0 will be the latest step)
Follow this KB article to do so:
The fifth step: Shutdown your old appliance. Setup the new appliance in the very same version as the old appliance. 
The sixth step: Restore the backup from the old one. Follow this KB article:
The seventh step: Update the appliance (if not done) to the latest version (see step 4)
The final step: Upload the latest agent bundle and let auto update the agents to 9.
Answered 10/02/2018 by: Nico_K
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ