I suggest you ...

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

81 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Subramani Ananthapadmanabhan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Subramani Ananthapadmanabhan commented  ·   ·  Flag as inappropriate

        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.

      • John West commented  ·   ·  Flag as inappropriate

        As an alternative, I would love to see a method to change this configuration without a full installation of the client.

      Feedback and Knowledge Base