ESX hardware status change however, the change is not reflected in OpsMgr.

An ESX hardware status change takes place and is registered in VMware vSphere client. It also may be confirmed via the VMware MOB; however, the change is not reflected in OpsMgr.

The object properties added at the end of the object name are referred to as trailers. The overall health status of the host can be changed correctly in some scenarios, but the hardware item health status will not be updated in OpsMgr. Most often the health state of the affected hardware item may be "Unknown" (grey) in VMware vSphere client.

In nworks 5.6 the following issue with the state table exists: object properties are considered part of the object name and when a property is changed, it appears to nworks as if these are two different objects. Therefore, two state table entries appear - one for each object.

If the health status of the host is not updated in OpsMgr, first please check that nworks shows the corect status in the log.

If you are able to see the correct status in the log then you may require a patch to resolve your issue. Please submit a support request for the patch  via our support portal and include the applicable logs.

NOTE: The support team will make 100% sure that you are experiencing this specific issue described in this particular article before delivering the patch.

Once you receive the patch, here is how to install it:

1. Stop "nworks Virtual Infrastructure Collector service" service

2. Back up "nworksCore.dll" and "nworksVIC.exe" from the Collector installation folder

3. Replace "nworksCore.dll" and "nworksVIC.exe" with files from the archive

4. Move "trailers.xml" to "[system_drive]\Program Files\nworks\VIC\Collector\Resources"

5. Remove old "StateTbl.xml" from "[system_drive]\Program Files\nworks\VIC\Collector\Data"

6. Start "nworks Virtual Infrastructure Collector service" service