Menu Close

Enable proxy as a default setting in SCOM



This is for SCOM 2012 through SCOM 2019.


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 once, and forget it. 

One of the FIRST things I do after installing SCOM:


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


  1. Morgan

    I’m getting the alert for my management servers but I’ve enabled it. I’ve tried turning it off and waiting and then enable it again but the alert comes back. Any ideas?

  2. ronald van den berg

    Minor adjustment, you should not run this on any scom managementserver but on a server where the scom console is installed. If you have the console on your managementserver it will run fine but it’s the console that brings the powershell commandlet.

Leave a Reply

Your email address will not be published.