OpManager data incorrect (CPU Memory etc)

OpManager data incorrect (CPU Memory etc)

Hi I have been using OpManager at the place I work for about 2 and a half years.
I used to love this software... but as I have used it more and more, I am seeing some MAJOR problems...
If any of this is based on improper usage, please let me know.

I feel that In this past 5-6 months I have seen OpManager decline in quality.
This is making OpManager unusable because we cannot trust the data OpManager is reporting...

Here are some of the problems we have started experiencing. We have read through the troubleshooting guides, and ran repairdb and we have even reinstalled fresh a few times thinking it was something in our database...

So lets start fresh.
First we do a fresh install, and using network discovery to add all of our devices, this is where problem #1 comes in.
When we use network discovery to add our devices, OpManager decides to list each ip address as an individual device, instead of showing one device with multiple interfaces.... this increases cost to license the software and also makes the software hard to manage when we have a lot of devices and lot of different ip addresses.

I normally remove all of the duplicates but the main ip address, because the duplicates show different statistics than the main ip address.
Which also doesn't make any sense to me... how can the device, have different memory usage/cpu usage based on a different ip address? (same system)


So lets assume I've removed all the duplicates now, and I've moved on to the virtual machines.
Now I check a host, and some of the VM's are showing but with no ip address...
It turns out OpManager discovered them as physical servers instead of hyper-V VM's.  Quite annoying... now I have to manually assign the VM's ip addresses or they will stay showing as physical servers.

Ok, so now I've manually corrected the VM's... but one of the hosts needed to reboot for windows updates... and all the VM's are now moved to a different host in the cluster... now I must rediscover the host/devices in order to continue receiving alerts and information for the VM's... Not very intuitive... but not a deal breaker...

So now lets assume I've re-discovered and manually fixed everything... I have all my devices... but now the data that is being displayed is incorrect...

I noticed that for some of our devices, the CPU and memory %'s stay exactly the same over the 7/30 day reports for days at a time... so I decided to check... 
I set a server to start installing SQL Server 2012.  I left it sitting where it was using over 50% of it's memory, and it stayed that way overnight. I login again to check OpManager the next day, and it still says 0% memory utilization. More data we cannot trust.

And to finish me off... in the past week, something happened and now OpManager cannot properly display the menu bar under Home/Network/Server/Appls etc.   it is cut off half way.

The incorrect CPU/Memory reporting is a deal breaker by itself if that cannot be fixed. we need to be able trust the data OpManager is giving... The rest are mainly annoyances... but it really feels like OpManager is declining in quality...  We have started using Spiceworks along side OpManager... at first Spiceworks was nowhere near usable... now its almost better than OpManager and its free...



I have attached screenshots showing some of the problems.  I know this is more of a community forum...but any assistance would be appreciated... before I spend the time troubleshooting each issue individually to see if OpManager is even worth all the work...  If its this much work to get OpManager to a point where we can trust it's data... why don't I learn to set up Nagios or some free one? and save the cash?

                New to ADSelfService Plus?