Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Polling issues when VMAN monitors a vCenter that is hosted on a virtual machine (affects AppStack)

Polling issues when VMAN monitors a vCenter that is hosted on a virtual machine (affects AppStack)

Updated March 28, 2018


You may encounter polling issues when VMAN is monitoring a vCenter that is hosted on a virtual machine.


In this case, AppStack will treat the vCenter as a virtual machine and display the parent entities of the virtual machine instead of the environment underneath the vCenter.


  • VMAN
  • AppStack
  • vCenter


This is a configuration-based issue, caused by a conflict where VMAN polls the vCenter, which is hosted by a virtual machine underneath that vCenter or another vCenter hosted on a VM that is managed by another VCenter.


As a work-around, you can alter the permission of the user/group credential used by VMAN for monitoring the vCenter to prevent polling of the virtual machine. 


The user/group's permissions must be modified using the vSphere client. For the virtual machine where the vCenter is installed, set the user/group's permission to "No access".


Doing so will prevent the vCenter from polling the virtual machine. 


The following steps and image provide an example.

  1. Locate and select the virtual machine where the vCenter you are polling is installed.
  2. Select the Permissions tab.
  3. Select the user/group and modify the Access Rule to No access.
  4. Select Propagate and click OK.


Last modified