The virtual machine object name in vRealize Operations Manager might be different from the object name in the vRealize Configuration Manager compliance templates. This difference is a result of how vRealize Operations Manager and vRealize Configuration Manager retrieve and collect data from vCenter Server.

Some virtual objects in the templates might be managed in vRealize Configuration Manager as a virtual machine with a guest operating system on which the vRealize Configuration Manager Agent is installed and as a virtual object that is managed through a vCenter Server instance using the Managing Agent. When the object is managed as a virtual machine with a guest operating system and as a virtual object, the name that appears in the template detail results might be different from the name that appears in vRealize Operations Manager.

The name in the vRealize Configuration Manager template results is the object name that you assigned when the object was created, usually similar to the DNS name. The name in vRealize Operations Manager is based on the vCenter Server object name unless you renamed the object in vCenter Server. If you renamed the object, vRealize Operations Manager displays the user-assigned name. If the name is different from the originally assigned name, you see one name in vRealize Operations Manager and the DNS-derived name in vRealize Configuration Manager.

To verify that you are working with the same object, use the data in vRealize Configuration Manager to correlate the object name, the guest object name, and the DNS name.