OK, I believe this group population will not longer work since we removed the relationship between virtual machine (Veeam VMGUEST class) and Windows Computer (Microsoft class)....
We had to make this change, because we discovered that this relationship could cause SCOM performance issues in the database, in large environments with many MPs installed.
(to share more detail, the large nested topology created by this relationship caused the RecursiveMembershipTable in SCOM Db to grow hugely...sometimes to several million rows, with resultant performance issues...and that's enough database deep-dive I think!
Actually we made this change in MP v7.0 R2, but perhaps you upgraded straight from 7.0 to 8.0, skipping R2, so this is your first experience of the change....
Anyway, the good news is that we DO still, in MP 8.0, create some relationship to the Windows OS inside the VM. It took some R&D, but we were able to optimise the way we do that, so we could still keep that valuable link between VM and the WIndows OS, without breaking SCOM internals...
We now create a relationship between VM and the special Veeam object 'Ops Mgr Agent in vSphere VM'.
If you look in the All VMs state view, you will see that there is a column for this new contained object (it replaces the column for Windows Computer that we had before)
And, there is a brand new Dashboard, called 'Apps on this VM', which you can see in the Navigation pane. That will open a diagram view of the associated Ops Mgr agent - so you still have a way to browse to that Windows OS and see the MPs that run inside. So our 'App-to-Metal' story still works!
Bottom line, your desired group of all related objects should still be possible - we need to take a look and change the classes in there. I'll get my team to check it out. Watch this space!