There has been a lot of activity towards migrating to SCOM 2016. With that, Savision has been getting several requests on how to migrate their existing Live Maps Dashboards.
SCOM 2016 Migration
First there are 2 basic ways to migrate to SCOM 2016. How each company decides to upgrade really depends on their current SCOM implementation and overall health of environment.
- In place upgrade from SCOM 2012 R2 UR9 to SCOM 2016
- Side By Side implementation – New SCOM 2016 Management group. Multi-home SCOM agents to report to current mgmt. group and new one.
There could be variations on the different migrations paths, but these are the basics.
Live Maps Upgrade Scenarios
Scenario 1. In place upgrade of SCOM 2012 R2 to SCOM 2016.
In this case, everything in your database is getting upgraded. This also means your Live Maps Dashboards will all remain. There are a couple things that you should do to ensure everything works.
- Upgrade Live Maps to the latest version before the upgrade process. V8 is the only Live Maps version that is certified to work with SCOM 2016. You can download the latest version by following this link. If you are V7 or below please contact email@example.com or firstname.lastname@example.org PRIOR to attempting to upgrade. It will require a new license key to upgrade.
- After upgrading to the latest version of Live Maps you can procced with your upgrade to SCOM 2016
- All dashboards will be preserved in your SCOM Database and therefore when you are done with the upgrade of SCOM, everything should remain as it was before.
Scenario 2. Side-By-Side Migration. New SCOM Mgmt group
In this scenario, things are a little bit more complicated.
- First thing is to build your new SCOM mgmt. group. Start the process like you normally would.
- When you are ready to add Live Maps to the new SCOM mgmt. group, please contact email@example.com or firstname.lastname@example.org. You will need to inform us of your upgrade path and time frame.
- At that point we can issue you a new license and cover any of paperwork procedures we need to decommission the existing license and issue a new one.
- Next install Live Maps as you would a new installation.
Migrating Existing Dashboards into the new SCOM mgmt. group.
Most dashboards are stored in Management packs in SCOM, however some are not. For the most part it can be as simple as exporting the MP and importing it in to the new management group. There are a couple things to be aware of during this process.
First realized that your Dashboards will have dependencies on existing MPs in your current SCOM group. When importing the new MPs into the new SCOM mgmt. group it should tell you which dependencies you will need. Let me cover the various dashboards to assist with the process.
- Live Maps Services – These are generally contained in individual MPs. They would be called “Savision Live Maps Service <name of service>” There could be several of these depending on the number of services you have created.
- Individual Lists or Diagrams created with the Authoring console. These can be saved in just about any MP. If you have questions as to the MP, you can open the dashboard in the Live Maps Authoring Console and look at the properties of the individual dashboards. MOST dashboards by default will be stored in the “Savision Live Maps Authoring” MP. You many need to edit this MP and increase the version number above any new “Savision Live Maps Authoring” MP that will be there by default in the new installation prior to importing in the new mgmt group.
- Summary Dashboards – In order to copy your Summary Dashboards, please follow this KB article.
- Static URLs. – While not a Dashboard of itself, it is something I wanted to add in here since it should be stated. These are stored as Objects in SCOM and just like Summary dashboards, will need to be recreated.
There are a couple other scenarios that can exist. For one if you only want to export a couple dashboards into the new mgmt group, then it is possible to copy these into different MPs instead of coping over the entire bunch of Dashboards. This is a manual process that support can give you instructions on how to do.
We do suggest looking at the dashboards after the move. If your dashboards were created with Membership rules, then they will simply auto-populate with the new or existing object from the new mgmt. group. If you have populated your dashboards with explicit objects then there could be cases where an object doesn’t exist in the new mgmt. group. Those objects will show up as an un-associated object.
Last note, if you need assistance, please feel free to contact email@example.com. We can make suggestions on how to move only certain dashboards if needed.