Partager via

Reinstalling your SCOM agents with the NOAPM switch

  • Article

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    August 06, 2017
    Excellent idea. I have added a link to this post from https://ianblythmanagement.wordpress.com/2017/08/05/scom-2012-r2-agent-shows-apmapp-pool-crashes-in-2016-mg/ where I just show overriding one rule but this completes it with all the additional options.Ian
  • Anonymous
    August 06, 2017
    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?
    • Anonymous
      August 06, 2017
      The comment has been removed
  • Anonymous
    August 07, 2017
    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,Konstantin
    • Anonymous
      August 07, 2017
      From my testing - it appears the UR is unaffected - when I checked the versions of the UR files - they remained intact.
  • Anonymous
    August 18, 2017
    HiIf 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.
    • Anonymous
      November 10, 2017
      You can't, but you can write a script that automatically removes APM after the installation as a last step (you need to check with get-scomagent if the agent has been deployed already). If you don't have access to the computer directly you can wait (loop check in orchestrator) until this mp has discovered the agent and then call the scom task with a script.
  • Anonymous
    August 19, 2017
    Great time-saver!
  • Anonymous
    August 21, 2017
    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. Alex
  • Anonymous
    October 06, 2017
    Hey!Is there any news about an Update Rollup 4 for SCOM 2016? Hopefully this is fixed in an new UR.Jan-Ove
    • Anonymous
      October 08, 2017
      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=1Any 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?Thanks
      • Anonymous
        October 13, 2017
        The comment has been removed
        • Anonymous
          November 30, 2017
          The comment has been removed
          • Anonymous
            November 30, 2017
            Excellent, thanks Thorsten - that is it! My path did have a space in it (wrapped in quotes). Thanks for that!Steve
  • Anonymous
    October 20, 2017
    Does this only work with SCOM 2016 or will it work with 2012 as well? The reason I ask is because I cannot get this to change to NOAPM on 2012. The override runs for maybe 2 seconds and nothing changes. I tried using the "/i" and adding the "AcceptEndUserLicenseAgreement=1" to no avail. I also tried running the MOMAgent from and network folder and locally, but still not successful.
    • Anonymous
      November 10, 2017
      I only have issue with agent that have an OMS workspace as well.
  • Anonymous
    January 04, 2018
    Hi Kevin,Thank you for your very helpful article. We deployed SCOM 2016 UR4, and had got also this issue in SharePoint farm IIS servers.You wrote "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..."Do you speak here only about "Microsoft.SystemCenter.Apm.Infrastructure MP" or also other SCOM 2016 MPs which you listed above?Best RegardsBirdal
    • Anonymous
      January 04, 2018
      Hi Kevin,although we deleted all MPs related to APM as you defined above, the Agents staus are listed in Operation Console still in "APS Installed > true"?Is there any other step in this workaround?Best RegardsBirdal
  • Anonymous
    January 04, 2018
    Hi Kevin,although we deleted all MPs related to APM as you defined above, the Agents staus are listed in Operation Console still in "APS Installed > true"?Is there any other step in this workaround?Best RegardsBirdal
  • Anonymous
    January 19, 2018
    Thank you so much for this! I was going the route of creating an SCCM package and config baseline but this was much faster with your MP. I have a huge criticism for the OM team enabling APM by default in 2016 when it wasn't in 2012 especially since the APM agent broke SP and IIS. I was able to path this directly to my agent folder on the OM server and using an account with local admin rights on the agent servers and not the default action account. msiexec.exe /fvomus "\SCOM01\d$\Program Files\Microsoft System Center 2016\Operations Manager\Server\AgentManagement\amd64\MOMagent.msi" NOAPM=1Thanks for the MP as well. That will be helpful for more things going forward.Brett
  • Anonymous
    February 07, 2018
    We also deployed 2016 agents with UR4 - and the IIS/APM apppool crashing issue has occurred. The issue is still not fixed in scom2016 UR4!!!Happenned today following first restart of an application server where the 2016 agent and UR4 had been installed several weeks ago. We worked around by running agent install with NOAPM=1 which resolved the issue.Kevin, Please ask Microsoft to fix this once and for all!
    • Anonymous
      February 07, 2018
      Yes, I covered this in my UR4 update documentation. The issue is not complete fixed. This is why I recommend to use NOAPM switch on agent installs, and remove the APM management packs from SCOM. I don't have a timeline for when this will be fixed, so the safe route is best.
  • Anonymous
    March 07, 2018
    Hi KevinI removed all APM management packs and pushed SCOM agent to a new server but I still see the Monitoring APM service installed on the agent.even after removing the APM management packs do I still need to import the MP you created and run the task that disable the APM ?What if my environment doesn't allow importing such customized MP's, is there is other solutions doesn't include uninstall and install the agent ?Thanks,
    • Anonymous
      March 07, 2018
      Removing the APM packs has zero impact. If you want to remove the APM service from the agent - you must reinstall the agent with the -NOAPM switch. There is no other solution outside of reinstalling the agent. What kind of environment does not allow install of custom MP's? If that was the case, then I'd say write your own using mine as a template. Without community MP's or custom authored MP's, SCOM will be very basic. I cannot imagine that scenario.
  • Anonymous
    August 02, 2018
    Hi Kevin,We are ready to use APM with some of our systems and would like to know the proper way to add it back to agents that were deployed with the NOAPM=1 switch. Should we repair with NOAPM=0?or repair without the NOAPM switch?or is there another option than running a repair installation?Thanks,Andy
    • Anonymous
      August 06, 2018
      Any guidance her would be appreciated. Thanks, Andy
      • Anonymous
        August 06, 2018
        I have not tested it. I'd assume a repair without the NOAPM might do it, but if that fails an uninstall/reinstall of the agent certainly will.