I'm a little disappointed in not only this version of OpManager, but what appears to be the lack of support from your staff in getting all my issues addressed. Here is a list of items I'd like addressed:
- 8721 has a bug that shows multiple hosts that are not virtualized because they have multiple cores in their processors. This is a known bug, but I was given a "hotfix" that was supposed to have corrected this problem and it doesn't work.
- When virtual machines on my ESX servers are rebooted, OpManager loses their IP address and their notification profiles and all monitored alarms associated with that devices.
- The version I'm on apparently holds onto "stale" entries in the database and you have to manually run scripts against not only the IP address of the "stale" device, but the hostname.
- URL monitoring is broken and can't even be trusted as working at this point in time. When inputting a URL montior from the Admin/URL monitoring all your URL's won't poll correctly. And when entered in on the machine that's associated with the website, you get a error when viewing the snapshot that says "Graph not available, Possible Causes: Service may not be running. Enable the service again to view the graph" How can I trust this monitor when it thinks the services isn't even running.
This last upgrade has totally fuc'd up my entire monitoring system which took over two weeks to get built correctly and working. Now I feel my only option is to downgrade the system, and restore from a known good backup to correct all these issues that were brought about by an upgrade.