So time for a small investigation. First I ran Health Explorer against that Object. And with a single glance I knew why this Object didn’t get a status:
Exactly! Not a single Monitor is in place. Only the Parent Monitors, which are by default shown for any Object, but nothing else. So no matter what, but that Object will never ever get any status. Which is bad. Personally I don’t like DAs which have any component which are stateless.
So why not borrow it by using a Dependency Rollup Monitor? The funny thing is with Monitors like these, they borrow/reflect the status of any other Monitor. So by themselves these Monitors aren’t monitoring anything. They just copy the status of any other Monitor.
How it was built
In the SCOM R2 Console: go to Authoring > Authoring > Management Pack Objects > Monitors. Hit the Change Scope option in the top level bar and select as Object VMware View Connection Server Groups > OK. Now the Object is shown. Collapse it by clicking on the plus signs and you have a view like this:
Right click on Parent Monitor Availability > Create a Monitor > Dependency Rollup Monitor. And follow these screen dumps:
Select as Monitor Target VMware View Connection Server Groups , as Parent Monitor Availability and empty the checkbox for the option Monitor is enabled > Next
For Monitor Dependency select the sub node Availability under the node VMware View Connection Server Group (All VMware View Connection Server Groups) > Next