Upgrade from 2.2 to 2.3 best practices


A large customer of mine will be upgrading OpenManage Essentials from 2.2 to 2.3  Customer has about 700 assets discovered and managed. He is using remote database. Although from documentation it is a straight forward process every single time he upgraded from a previous version he faced issues. I wonder if we do have any guidelines/best practices to use before starting the upgrade. What backup should be taken proactively before start?

Please advise

Thank you


0 Kudos
1 Reply

RE: Upgrade from 2.2 to 2.3 best practices

Hi Argy,

Thanks for the query.

It is unfortunate to know the customer is not able upgrade OME cleanly in the past. We would really like to know what kind of problems were faced so that we can make the experience better.

The best practice guide will include nothing beyond following steps:

  1. Take a backup of the current database manually before upgrading. Preserve it in-case needed in future.
  2. Ensure that the user (admin on the OME server) installing OME must have db_owner rights on OME's database.



0 Kudos