When a physical and a virtual object with identical names are present in SCOM and in the SCOM database they tend to get mixed up by the application.
Unfortunately, nworks currently does not support machines having the same name within one environment. nworks uses VM Name as a unique ID, so there is no way to use the VMware underlying unique ID. Also there is a SCOM issue with displaying performance graphs and instead of the Display Name being used, the ID will be used instead. This makes the graphs not as user-friendly because it’s very difficult when viewing graphs to relate the VMware ID to the Display Name you are familiar with.
To resolve, rename the machines in the environment.