True up report

It's important to regularly check agent, management server and gateway server numbers by doing some comparisons. Over time they will drift, particularly agents, which means things aren't monitored.

The checks below are basic but they've been able to identify HealthService problems which, once resolved, usually fix other problems.

Compare HealthService numbers

This compares total HealthService instances to agent, management servers, and gateway servers.

First get your total HealthService count: (includes agents, management servers and gateway servers)

(Get-SCOMClass -name Microsoft.SystemCenter.HealthService | Get-SCOMClassInstance).count

Next, get your agent, management server and gateway count:

(Get-SCOMManagementServer).count # this gets MS & GW servers.
(Get-SCOMAgent).count

Adding these two numbers together should match the number from the first command.

Confirm Update Rollup info is collected

This compares total HealthService instances to update rollup instances.

This one caught me out. I found this problem when looking at the Windows Agent view in my Update Rollup mp. It wasn't matching the count from Administration > Device Management > Agent Managed.

You'll need Excel for this.

First get your total HealthService count: (includes agents, management servers and gateway servers)

get-scomclass -name "Microsoft.SystemCenter.HealthService" | get-scomclassinstance | sort displayname | select displayname | clip

Now get all Windows Computers from the update rollup mp. This will have agents, management servers, and gateway servers. Clean up the data then paste into Excel:

get-scomclass -name "Microsoft.SCOM.UpdateRollup.Class.WindowsComputer" | get-scomclassinstance | sort displayname | select displayname | clip

Now you can compare/filter in Excel to find discrepancies.