Reinstalling your SCOM agents with the NOAPM switch


This one comes from collaboration with my colleague Brian Barrington.

Because of the issues with SCOM 2016 and the default APM modules impacting IIS and SharePoint servers…..  (Read more about that issue HERE, HERE, and HERE)


Brian was looking for a way to easily remove the APM components from the deployed agents with minimal impact.

Normally, the guidance would be to uninstall the SCOM agent, then reinstall it from a command line installation using the NOAPM=1 command line parameter.  That could be a challenging task if you have hundreds or thousands of agents!


His idea?  Use my SCOM Agent Tasks MP here:


It has a class property in the state view called “APM Installed” to help you see which agents still have the APM components installed (which are installed by default)



It has a task called “execute any PowerShell” 

In the task – Override to provide the command you want to run – such as:

msiexec.exe /fvomus "\\server\share\agents\scom2016\x64\MOMagent.msi" NOAPM=1

You just need to place the MOMAgent.msi file on a share that your domain computer accounts would have access to.



This performs a lightweight upgrade/installation of the agent, but only changes the switch “NOAPM=1” which will result in leaving all other settings alone, and only removing the APM service and components!

We have gotten good feedback on the success of this process across hundreds of agents in a short time frame.


Removing the APM MP’s

On another note – if you have no plans to use the APM feature in SCOM – you should consider removing those MP’s which get imported by default.  They discvoer by default a LOT of instances of sites, services, and instances of classes where APM components are installed on the agents.

MP’s to remove in SCOM 2016:

  • Microsoft.SystemCenter.DataWarehouse.ApmReports.Library (Operations Manager APM Reports Library)
  • Microsoft.SystemCenter.Apm.Web  (Operations Manager APM Web)
  • Microsoft.SystemCenter.Apm.Wcf  (Operations Manager APM WCF Library)
  • Microsoft.SystemCenter.Apm.NTServices  (Operations Manager APM Windows Services)
  • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring  (Operations Manager APM Infrastructure Monitoring)
  • Microsoft.SystemCenter.Apm.Library (Operations Manager APM Library)
  • Microsoft.SystemCenter.Apm.Infrastructure (Operations Manager APM Infrastructure)

All of the above can be deleted.  However – in order to delete the Microsoft.SystemCenter.Apm.Infrastructure MP, you will need to remove a RunAs account profile association, then clean up the SecureReference library manually by deleting the reference.

In the Admin pane > Run As Configuration > Profiles, in the Data Warehouse Account.  On the RunAs accounts, you will need to remove the Operations Manager APM Data Transfer Service:


Then – manually export the Microsoft.SystemCenter.SecureReferenceOverride MP, and edit it using your favorite XML editor.  (Make a Backup copy of this FIRST!!!!!)

Delete the reference to the Microsoft.SystemCenter.Apm.Infrastructure MP.



Save this, then reimport the Microsoft.SystemCenter.SecureReferenceOverride MP.

At this point you can delete the final APM MP – Microsoft.SystemCenter.Apm.Infrastructure (Operations Manager APM Infrastructure)


Deleting that MP with manual edits too scary for you?

At a bare minimum – if you are not using the APM feature – you should disable the discoveries:



Then run Remove-SCOMDisabledClassInstance in your SCOM Command Shell, which will remove all these discovered instances that you don’t use.

Comments (11)

  1. Ian Blyth says:

    Excellent idea. I have added a link to this post from where I just show overriding one rule but this completes it with all the additional options.


  2. AlexP says:

    Is there any solid reason to actually keep APM on, given the fact that most public websites are monitored via other tools, and internal sites are often not that critical?

    1. Kevin Holman says:

      The best/only reason to leave APM components, is only if you wish to use APM in SCOM for your custom developed .NET applications, as a developer performance tool. You do not need it to use SCOM’s URL monitoring.

  3. staxkill says:

    Helpful articel as usual!
    Does the “lightweight upgrade/installation of the agent” consider any installed update rollup as the msi will be rerun without the msp from an UR?

    Best Regards,

    1. Kevin Holman says:

      From my testing – it appears the UR is unaffected – when I checked the versions of the UR files – they remained intact.

  4. Peter says:


    If you use the cmdlet Install-SCOMAgent (like we do via Orchestrator) how can you prevent the APM installation? It doesn’t seem to have that Parameter.

  5. AlexLarkin says:

    Hi Kevin, (FYI)
    I have found that this APM issue not only affects SharePoint but most applications that are running the .NET v2.0 framework. It only appears after a reboot of the server.


  6. Hey!
    Is there any news about an Update Rollup 4 for SCOM 2016? Hopefully this is fixed in an new UR.


    1. Kiwifulla2 says:

      I’m not sure if this is a locale (US-NZ) thing for me or VL thing (?!), however firstly I had to add AcceptEndUserLicenseAgreement=1 to the command or else it failed?

      But more impotrtantly, if I use msiexec.exe /fvomus “\\server\share\agents\scom2016\x64\MOMagent.msi” NOAPM=1 AcceptEndUserLicenseAgreement=1, the repair only took about 2 seconds, reported (Event Log) that it was successful, but the Microsoft Monitoring APM service was still installed (yes I hit refresh :))?

      I then resorted to a /i instead of the /fvomus command which resolved it – e.g.:
      msiexec.exe /i “\\server\share\agents\scom2016\x64\MOMagent.msi” NOAPM=1 AcceptEndUserLicenseAgreement=1

      Any ideas why /fvomus didnt remove the APM service? I tested this on multiple machines. Also, do you not get prompted for the license agreement like I do?


      1. Kiwifulla2 says:

        Sorry I’ve upgraded a few more via SCCM and using this ((still needed that license piece) worked now: msiexec /fvomus “MOMAgent.msi” NOAPM=1 /q AcceptEndUserLicenseAgreement=1

        Still not sure why it didnt remove the APM service when I ran it manually via the command line as per my previous post. I didn’t have the /q there before and manually selected upgrade, so perhaps that was the issue.

        Apologies for the confusion.

        BTW, I read somewhere else that the UR needs the NOAPM=1 too. Is this required if UR3 is already on there, and I am reinstalling the main MOMAgent.msi with the NOAPM=1 switch first, which effectively at that point removed the APM stuff anyway?

        Step 1: msiexec /fvomus “MOMAgent.msi” NOAPM=1 /q AcceptEndUserLicenseAgreement=1
        Step 2: KB4016126-AMD64-Agent.msp NOAPM=1

        Appreciate your help Kevin!

Skip to main content