Keep NOAPM=1 as default setting for all MMA versions
The APM component (regardless of APM being enabled) frequently breaks .NET applications. Re-installing agent with NOAPM=1 means we cannot leverage the SCOM console to deploy agents. Request
Subramani Ananthapadmanabhan commented
If one reconfigures the agent with NOAPM=1; then "Pending Management" updates ( in the event of applying a UR) fails from the console. The console expects APM component to be installed; so this would require a fix in the console side as well.
yes we want this
John West commented
As an alternative, I would love to see a method to change this configuration without a full installation of the client.