Enable proxy as a default setting in SCOM 2016




The default setting for new SCOM agents is that Agent Proxy is disabled.  You can enable this agent by agent, or for specific agents with script automations.  I find this to be a clumsy task, and more and more management packs require this capability to be enabled, like Active Directory, SharePoint, Exchange, Clustering, Skype, etc.  At some point, it makes a lot more sense to just enable this as a default setting, and that is what I advise my customers.

Set it, and forget it.  One of the FIRST things I do after installing SCOM.

(This also works just fine and exactly the same way in SCOM 2012, 2012 SP1, and 2012R2.)


On a SCOM management server:  Open up any PowerShell session (SCOM shell or regular old PowerShell)

add-pssnapin "Microsoft.EnterpriseManagement.OperationsManager.Client"; new-managementGroupConnection -ConnectionString:localhost; set-location "OperationsManagerMonitoring::"; Set-DefaultSetting -Name HealthService\ProxyingEnabled -Value True

If you want to use this remotely โ€“ change โ€œlocalhostโ€ above to the FQDN of your SCOM server.


In order to inspect this setting, you can run:

add-pssnapin "Microsoft.EnterpriseManagement.OperationsManager.Client"; new-managementGroupConnection -ConnectionString:localhost; set-location "OperationsManagerMonitoring::"; Get-DefaultSetting

Comments (16)

  1. Steven Peck says:

    YAY! No more running my script to set this on new agents every month! Is there anything else you advice customers to default to (Other then the SQL queries and registry settings for management servers you updated the other day)?

  2. Mayan Nath says:

    very helpful.. and one less task to worry about.
    I wonder why its not enabled by default to begin with.

  3. GuyInIT says:

    Does this work in SCOM 2012 R2? We currently rely on a management pack to do this for us.

    1. Steven Peck says:

      It sure seems to. ๐Ÿ™‚

      1. Kevin Holman says:

        See the part in bold and highlighted. ๐Ÿ™‚

  4. Kitaab says:

    Would it enable the setting for already existing agents or the the ones installed after running the commands.

    1. Kevin Holman says:

      Both in my experience. Since existing agents generally inherit the default setting.

      1. Kitaab says:

        Thanks , it worked for both existing and new Agents

  5. Hussein Mahfouz says:

    Very helpful.. Thanks ๐Ÿ™‚

  6. John Bradshaw says:

    Nice one!!
    Many thx

  7. matte says:

    Can’t get this to work on Windows Server 2016, getting:
    add-pssnapin : No snap-ins have been registered for Windows PowerShell version 5.

    When doing it remotely from a 2012 R2 I get:
    Set-DefaultSetting : Exception has been thrown by the target of an invocation.

    Any ideas?

    1. Kevin Holman says:

      Run it on the management server.

      1. matte says:

        I did, management server is Windows Server 2016

        1. Kevin Holman says:

          How are you launching powershell? I have tested this on WS2016 management servers and it works fine. Is the SCOM console installed?

          1. matte says:

            Launching powershell as admin. No console installed.
            I guess that it needs to be installed, I’ll install it and try again. ๐Ÿ™‚

          2. matte says:

            Worked much better with the console installed. thanks for the help @kevin!

Skip to main content