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
thanks Kevin!
Does this work on SCOM 2019? I am rolling out a new environment and this is a pesky part with SQL especially.
Yep
Thanks!
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?
Is this count for all agent installation method (Push, and Manual)?
Yes. It is a one-time permanent change for all agents in the management group, present and future.