From time to time SCOM generates the following alerts, that are not showing the FQDN of a problematic server, but only the GUID of the Managed Object:
The agent was not able to submit data on behalf of another computer because agent proxy is not enabled. Details:Health service ( XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ) should not generate data about this managed object ( YYYYYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYYY ).
For some reason those alerts do not contain the name of the server to enable proxying, but obviously we will need it in order to fix the problem
The agent was not able to submit data on behalf of another computer because agent proxy is not enabled. Details:Health service ( XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ) should not generate data about this managed object ( YYYYYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYYY ).
For some reason those alerts do not contain the name of the server to enable proxying, but obviously we will need it in order to fix the problem
Usage:
If you want to get it there is a cmdlet you have to run through PowerShell
- XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX - replace it with the GUID you find in a respective place in the received alert
The cmdlet has to be obviously executed in the Operations Manager Shell on the SCOM server. It will return the FQDN of the server, that you will need to enable proxying for
Code:
Get-SCOMMonitoringObject | ?{$_.Id -match "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"}
The output of the cmdlet