This event "Refresh Hardware Information" is required due to a known limitation in the VMware API....the vCenter API does not automatically keep the current hardware status of the ESX hosts.
So in order to have current status of power supply, temperature sensors etc, we have to call an explicit "Refresh Hardware" function for each Host; and this logs an event, as you can see.
We do split the refresh calls over 6 intervals, by default. You can configure the interval 'spread'.The setting is not available in our UI, but you can create this registry key on the nworks Collector(s) -
(for 64-bit system, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\nworks\VIC\Collector\GlobalSettings)
Create DWORD setting called 'IntervalCount' and set this to your required interval spread.
For example, if you had 24 ESX Hosts, and you set IntervalCount to 24, then one Host would be refreshed every interval (5 mins by default)
If you set IntervalCount to 12, then 2 Hosts would be refreshed every interval, and so on.
You can turn off the refresh hardware event completely - however I would not recommend that, as you would have no visibility of the hardware status of ESX servers.
I'd also recommend you don't set the interval too large; as you will experience a delay in getting hardware alerts into SCOM.
Note the above change only affects Hardware Status alerts. Other aspects of VMware data (vCenter events, Host & VM performance metrics etc) is not affected.
There are more details in the Release Notes for nworks MP 5.0.3, found here http://www.veeam.com/files/release_note ... _5.0.3.pdf
Hope the above answers your question - please let me know,