1. No virtual infrastructure objects (Clusters, Hosts, VMs etc) appear in the OpsMgr Console. Additionally you may receive an alert in Ops Mgr from the nworks Collector as follows:
Alert Name: Agent proxying needs to be enabled for a health service to submit discovery data about other computers.
Alert description (example):
Details:Health service ( [server name] ) should not generate data about this managed type ( nworks.VMware.VEM.VMGUEST ) object Id ( A2A3BA11-F03D-6757-597A-28A35B5000FE ).
Note: the alert description will contain server names and object IDs specific to your own environment.
2. Updates to the virtual infrastructure (such as adding or removing Cluster, Host, or VMs) are not reflected in the Ops Mgr views.
1. Proxying must be enabled for any server (agent or management server) where the nWorks Collector is running. This setting allows the Collector, via Ops Mgr agent, to inject new objects (such as ESX Hosts and VMs) into Ops Mgr.
2. Updates to VMware systems (such as add/remove an ESX host) may not have been reflected in Ops Mgr due to discovery synchronization or other issue.
Rebuild is available both at global Enterprise Manager level (where all Collectors will rebuild) or for individual Collectors.
After clicking this button you must wait several collection cycles (a cycle is 5 minutes by default) for the rebuild to complete.
The screenshot below illustrates Rebuild Full Topology available on the Enterprise Manager tab in the nWorks UI.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.