Image may be NSFW.
Clik here to view.
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