Loading...
Loading...
Either of the following scenarios apply: No virtual infrastructure objects (e.g., Clusters, Hosts, or VMs) appear in the OpsMgr Console. Additionally, you may receive an alert in Ops Mgr from the Veeam Management Pack for Microsoft System Center 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. Updates to the virtual infrastructure (e.g., adding or removing Cluster, Host, or VMs) are not reflected in the Ops Mgr views.
Verify Proxy Settings Proxying must be enabled for any server (agent or management server) where the Veeam Management Pack for Microsoft System Center 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. Verify that the Proxy setting has been enabled for the server where the Veeam Management Pack for Microsoft System Center Collector is installed: In the OpsMgr console, verify the Proxy settings. Go to the Administration pane. If the Collector is running on a standard Ops Mgr agent, then browse to Device Management | Agent Managed and select the Collector server. If the Collector is running on an Ops Mgr Management server, then browse to Device Management | Management Servers and select the Collector server. Double-click the relevant server, click the Security tab, and ensure that the "Allow this agent to act as a proxy and discover managed objects on other computers" check box is selected. Rebuild TopologyUpdates to VMware systems (such as add/remove an ESX host) may not have been reflected in Ops Mgr due to discovery synchronization or another issue. If only certain VMware systems items are missing or have not been updated in Ops Mgr, then it may be required to trigger a topology rediscovery. This is accomplished with the Rebuild Full Topology function available in the Veeam MP UI. Rebuild is available at global Veeam Extensions level (where all Collectors will rebuild). After clicking this button you must wait several collection cycles (a cycle is 5 minutes by default) for the rebuild to complete.
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.