Article ID: 2847767 - View products that this article applies to.
System Center Operations Manager 2007 R2 agent computers that utilize NIC teaming are not discovered or monitored and you see the following errors:
Log Name: Operations Manager
You may also see the following alert:
The process started at 09:44:43 failed to create System.PropertyBagData, no errors detected in the output. The process exited with 0
This can occur if the drivers being used for NIC teaming on the agent do not properly register in WMI.
The Base OS Management Pack (version 6.0.6958.0) contains a script that is responsible for discovering teamed adapters named Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs. If the NIC teaming driver being used fails to properly register in WMI, when the script runs and fails to find the registered classes the script will fail and log the errors above.
Many teaming NIC drivers also fail to register performance counters which can also be a reason why the required WMI registration is not created.
If you experience script failures such as these, disabling NIC teaming on the agent computer will resolve the issue. The problem with the NIC registration in WMI needs to be addressed by the NIC manufacturer so that the driver correctly register itself in WMI when installed. Please contact the adapter manufacturer for more information.
There is more information on this issue documented here:
Holman, Kevin. OpsMgr: Network utilization scripts in BaseOS MP version 6.0.6958.0 may cause high CPU utilization and service crashes on Server 2003 (http://blogs.technet.com/b/kevinholman/archive/2011/12/12/opsmgr-network-utilization-scripts-in-baseos-mp-version-6-0-6958-0-may-cause-high-cpu-utilization.aspx)
Also note that Microsoft now offers NIC teaming as part of Windows Server 2012.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2847767 - Last Review: May 13, 2013 - Revision: 2.0