Feature Requests - OMIVV 5.0

I have run in to a few things in OMIVV that have caused a little bit of frustration, so I would like to propose some ideas for improvement:

1. Health Dashboard - It would be nice to be able to click on the status and see a list of hosts with that status. For example, if I see that I have 1 host with "Critical" status on the dashboard, there isnt a very easy way to find out which host it is. I could look at the OMIVV logs, but that still isnt what I would call an "easy" way to look for the offending host. I would like to be able to click on the status, such as "Critical", and be taken to a list where I can see all hosts that have that status.

2. Profiles - When you update a System Profile that is attached to a Cluster Profile, the changes to the System Profile are not reflected in the Cluster Profile until you edit the Cluster Profile and finish the wizard. I was trying to get a Cluster Profile to show as "Compliant" by updating some settings in the System Profile that werent valid and then manually changing the other offending settings in BIOS. I kept re-running Inventory and Drift Detection jobs but I could not get the Drift Report to show the updated baselines and therefore would never show the host as compliant, even thought the settings matched the System Profile exactly. It wasnt until I went back to the Cluster Profile tab and noticed that there was a yellow exclamation next to the Cluster Profile that I found out that you have to edit/update the Cluster Profile. It would make more sense to me to have the Cluster Profile automatically updated when an attached System Profile is updated, however, if there are other reasons for this behavior that make it intended, at least a notification on the "Summary" window to tell you that you have to go update the Cluster Profile would be nice. Had I not stumbled across the yellow exclamation, Id likely still be pulling my hair out about that one.

3. System Profile Compliance - The system profile settings are applied nicely if you use Bare Metal Deployment, however, if you do not deploy the server through OMIVV and the BIOS settings dont match the System Profile, there is no mechanism within OMIVV to apply the System Profile settings and update BIOS on the host. If you want to get the host in to compliance with your profile, you have to manually boot in to System Settings and change the BIOS settings yourself. I know I could add the host to OME and reconcile the Configuration Compliance that way, however, that does not work for our environment as we have to keep the infrastructures separate due to security and lack of RBAC functionality/granularity in OME.

Thanks for the time and consideration! I know it sounds like Im bashing OMIVV, but that is not my intent, at all. This is a really good product that could be really GREAT with a few subtle improvements.

Have a good one!