SolarWinds Virtualization Manager has it's Pros and Cons
Overall Satisfaction with SolarWinds Virtualization Manager
We're using the product for a consolidated view of our VMware and Hyper-V environments in the UK. We integrate VMAN into our current Orion solution for detailed information on our servers and storage. We also make use of out of the box alerts and recommendations to maintain the platforms.
- Detailed server / storage information and performance statistics.
- Recommendations, particularly on right sizing.
- Single pane of glass for virtualized environments.
- Dashboard widgets - Sorting lists by column headings is not available in all views.
- Hyper-V needs more attention in general. But being able to group servers by Clouds, Host Groups, Replication status, Mainenence mode, host status etc. need to be added.
- Capacity management could do with the ability to report on entire enviroment and not just a single cluster.
- Hyper-V Recommendations – Memory – There should be a clear distinction between static and dynamic RAM. And actions should not mention or perform reboot if dynamic and not required.
- Positive TBA, We were hoping for more management based reporting and capacity management across the entire platform. This hasn't been the case as yet.
- Negative, the addition of a number of Cisco Flexpod-based hosts resulted in all hosts crashing due to Configuration collection being set to pull wmi fibrechannell_scsi_inquiry. We've now had to skip this to prevent any outage. But this means that this is turned off for all non-flexpod based servers as well.
were behind the VMAN implementation.