One of our customers wanted to monitor Windows servers remotely via RSP probe thru MCS configuration. They have a group of servers in one USM group but there are multiple WMI accounts to monitoring all servers in this USM group.
As a Remote System Monitoring profile can work with only one WMI account, we created multiple profiles, one for each WMI account.
Now each server in this group is being authenticated with each WMI account from each profile. One profile, which is able to successfully authenticate, is to poll the metrics, but all other profiles are generating connection errors.
MCS is great for certain use cases, and this is one that shows its limitations. My first choice would be to not use MCS but if that is the way the client insists on, then setup a nas auto operator per-processing rule to exclude all those specific false alarms. Perhaps someone else has a better solution.