We have always relied on the unmapped vms view to tell us when we have VMs that are not mapped by a rule. Since 3.4 we can't get all the VMs to map to a rule. There are VMs that no matter what we do we can not get them to map, even with a VCenter, datacenter or VM DNS Name rule. How do I get help or support on this?
I had this same problem and opened a support ticket. After much back and forth trying to diagnose the problem the support engineer said he was told it would be addressed in an updated version. :smileyplain:
We have issues with rules list with Object type only as resource pool but not with other object types. You may need to restart the tomcat/reboot UM appliance service to show the correct mapped VM's.