Identify Management Packs to Migrate to New Standalone 2019 Environment

Question

We're standing up a standalone SCOM 2019 environment to replace our SCOM 2012 R2 environment and I'm looking for ways to identify what Management Packs should be brought over from the old environment and which ones should be left behind.

Is there a way to find the Management Packs that are no longer being used :
Is there a way to identify what machines are associated to each Management Pack :

Thanks,

Jason

Answer 1

This should help you:

Kevin Holman

Answer 2

Hi,

As Blake suggested, have we tried the script to filter out the MP that are not used?

When we created a new environment, we can get the MP (download from the MP catalog, copy from the installation media, or something else) and import them. Most of them are sealed and we cannot make changes to them directly. To overcome this, there is a 'Default Management Pack' for us to save the changes, for example, overrides, custom-created rules/monitors, etc. To migrate to a new environment, mostly, we only need to export the unsealed MP and import theme to new environment. Below is a sample screenshots for your reference.

Alex
If the response is helpful, please click "Accept Answer" and upvote it.