SCOM Core – Removing all the add-on management packs that make SCOM 2016 Bloated and Slow

Wouldn’t it be cool if SCOM 2016 was super fast and required less resources?

SCOM 2016 is full of legacy solutions that make it bloated and slow.  You can remove “most” of these solutions if your not going to use them anyway?

SCOM was created in a very modular fashion using management packs to add features over the years.

After careful analysis I created the following PowerShell script to remove many of the management packs that slow down SCOM.

I have broken the script into pieces so you can remove any parts that you want to keep.  The script was created using a clean SCOM 2016 install.  If you have been using SCOM 2016 for a long time or have an upgraded SCOM environment you may have some additional dependencies in unsealed MPs you created.

If you find you need a solution in the future.  Simply add the MPs back from the installation media.


The script:

For APM:  You will need to manually remove the Secure Reference Override before you can delete “Microsoft.SystemCenter.Apm.Infrastructure” mp.  Notes in are in the script as to what needs to be deleted.

My Core Environment:


Authoring Wizard – Much cleaner

Discovery Wizard – Notice Unix is gone

Event Logs – No errors

One of the most valuable management packs to remove would be the “System.NetworkManagement.Library” MP.  But removing this MP breaks the Windows Computer discovery wizard.

Any issues, comments or ideas for removing additional management packs please leave them in the comments.

3 Responses to SCOM Core – Removing all the add-on management packs that make SCOM 2016 Bloated and Slow

  1. Konstantin September 1, 2017 at 4:31 am #

    Thank you Tim,
    this looks quite interesting and I will definitely remove some of the listed MPs.
    Although the Management Packs are in the installation media I will export all of them first so I need not to search in case I have to reimport them.

    As I already removed the APM MPs in the past I did not like to edit the SecureReferenceOverride MP manually.
    There are a couple of blogpost how to achieve that with PS.

    To delete the Microsoft.SystemCenter.Apm.Infrastructure MP you need to remove a RunAs account profile association (Operations Manager APM Data Transfer Service) and then clean up the SecureReference library (

    Therefore I first removed the profile association and the reference and afterwards all APM MPs.
    Of course this should be tested first in a dev environment.

    # remove the APM association for the Data Warehouse Account profile
    $APMAccount = Get-SCOMRunAsAccount -Name ‘Data Warehouse Action Account’
    $APMProfile = Get-SCOMRunAsProfile -DisplayName ‘Data Warehouse Account’
    $APMClass = Get-SCOMClass -Name ‘Microsoft.SystemCenter.Apm.DataTransferService’
    Set-SCOMRunAsProfile -Action ‘Remove’ -Profile $APMProfile -Account $APMAccount -Class $APMClass

    # export the Microsoft.SystemCenter.SecureReferenceOverride MP
    $MP = Get-SCOMManagementPack -Name Microsoft.SystemCenter.SecureReferenceOverride
    $MP | Export-SCOMManagementPack -Path C:\temp\

    # delete the reference to the Microsoft.SystemCenter.Apm.Infrastructure MP

    # remove APM Management Packs
    $delMPs = Get-SCOMManagementPack | Where-Object {$_.Name -like ‘*apm*’}
    $delMPs | Format-Table -AutoSize
    $delMPs | Remove-SCOMManagementPack

    At the end Remove-SCOMDisabledClassInstance should be run to remove all these discovered instances that are not used anymore.

    Best regards,

  2. Konstantin September 1, 2017 at 11:06 am #

    For SCOM 2012 R2 the ‘System.NetworkManagement.Reports’ needs to be deleted first because it depend on the ‘System.NetworkManagement.Monitoring’ MP.
    Why not deleting it for SCOM 2016 as well?

  3. Rich March 1, 2018 at 6:41 pm #

    FYI: I had a customer remove the “System.NetworkManagement.Reports.MP” as part of the tuning of a new SCOM 2016 Management Group. They had not yet installed SCOM Reporting, and found that install would fail, roll back and break SSRS. We had to run ResetSRS.exe to fix reporting services, reimport both the “System.NetworkManagement.Monitoring.MP” and “System.NetworkManagement.Reports.MP” , then we could successfully install SCOM Reporting. The install of SCOM Reporting is looking for the Network Management Reports in the Data Warehouse and will fail if it is not there.

Leave a Reply