There is currently no resolution for vCenter Server 6.0.
This issue is resolved in vCenter Server 6.5 U3
This issue is resolved in vCenter Server 6.7 U3
Workaround:
Complete all of the following. If one set of steps resolves the issue, you may skip the other remaining steps.
Ensure Windows OS Guests or Virtual Machines with a Windows OS are running guest VMware Tools version 10.3.2 (10338) or later.
Note: The vCenter VM summary page will show the Guest Tools version if you click More info.
Ensure the vRealize Operations Manager VMware vSphere adapter credentials have the Performance > Modify intervals privilege enabled in the target vCenter(s). See Minimum Collection User Permissions in vRealize Operations Manager 6.x and later for more information.
Note: The adapter credentials in use can be reviewed or modified in vRealize Operations Manager by clicking Configure on the VMware vSphere solutions under Administration > Solutions.
Once the credentials have been corrected, complete the following:
Disconnect and reconnect the parent hosts from vCenter
Virtual machine guest metrics will start collecting in vRealize Operations Manager within a few collection cycles.
Note: Disconnecting a managed host does not remove it from vCenter Server; it temporarily suspends all monitoring activities that vCenter Server performs. The managed host and its associated virtual machines remain in the vCenter Server inventory.
To be alerted when this article is updated, click Subscribe.
Impact/Risks:
The guest memory values can cause Capacity Calculations to be inaccurate for the Memory container.