Product Blog

14 Posts authored by: chrispaap

I am excited to announce the latest release of Virtualization Manager (VMAN) 8.1 which is now available on the Customer Portal. Continuing the great work done in VMAN 8.0 to migrate VMAN functionality to a unified Orion platform, VMAN 8.1 further extends these capabilities by providing Capacity Planning natively on the Orion platform. With VMAN 8.1, the new and improved capacity planning feature provides a modeling wizard, which is more intuitive and helps the user create various configurations along with test variable growth scenarios.  Administrators are now empowered to generate reports on the fly and provide accurate growth predictions of their virtual infrastructure to the business. In addition to Capacity Planning, Azure Cloud Monitoring has been added to VMAN's capabilities to monitor hybrid infrastructure.



What's New in Virtualization Manager 8.1



Capacity Planning


The new and improved Capacity Planning is an Orion-based scenario wizard that helps you create and test variable configurations on the fly. You can also take a more intensive approach, accounting for your environment's historical performance, new system needs, and peak usage times.  When planning your virtual environment infrastructure, resources, and allocation, you may need help determining the best amounts and structure. How will adding a substantial amount of VMs affect your resource usage and performance? Should you add one or more new hosts to keep up with expansion? Do you need to worry about capacity right now, or will your environment be okay for the next 6 months? Capacity Planning uses historical data and trending calculations to better determine the outcome of your infrastructure needs. Run multiple types of expansion scenarios: Simulate adding VMs, adding hosts, or both. Each scenario generates a report with detailed usage statistics covering predicted CPU, memory, and disk usage.

Click here for online demo.


Capacity Planning Home

From the Capacity Planning home page, you may select prior capacity planning reports to review or select new to open up the capacity planning wizard to create a new report.

Three different modeling scenarios to choose from

  • Run Checkup Wizard -  A resource depletion report will be run on a cluster designated by you based on existing resource utilization.


  • Simulate adding extra VMs - Model a scenario of adding additional VM load infrastructure and determine the impact to your existing hosts. Model VM usage based on an existing VM or create your own configuration.


  • Simulate adding extra host computers - Determine the impact of adding additional hosts to an existing cluster.


  • Simulate adding extra VMs and host computers -  Determine if your infrastructure growth strategy will keep up with expected VM growth by simulating adding both VMs and Hosts to an existing cluster.



Profiles are used to determine the impact of adding the specified number of VMs or hosts to your infrastructure.


  • Predefined Profiles - You can select a predefined VM profile of Small, Medium, or Large.

These profiles are static and not based on your an actual VM in your environment.

  • Custom
    • Use an existing VM/Host -  Selecting an existing VM will model a scenario of adding a number of VMs based on the resource utilization of the profile.
    • The use of custom profiles greatly improves capacity planning modeling when you can forecast an upcoming project that will increase the use of resources based on a currently used profile.
    • Build your Own - You can manually specify hardware configurations.  Useful if you do not have an existing VM or host to model configurations after.


The use of custom profiles greatly improves capacity planning modeling when you can forecast an upcoming project that will increase the use of resources based on a currently used profile.



The Capacity Planning reporting wizard culminates in an easy to review report that breaks out the current and expected state of your virtual infrastructure.


The report can be broken up into 3 sections.


Projected Growth

    • Workload - Provides an aggregated view of VM workload utilization in the selected cluster.
    • Resources - Provides an aggregated view of Host resources in the selected cluster
    • Simulated growth - The amount and configuration of VMs or Hosts added



Charting Thresholds

Provides a graphical representation of the actual vs simulated utilization of CPU, memory, & Disk. Estimations of when thresholds are reached for Warning, Critical, and Capacity are provided




  • Available Virtual Capacity - How many VMs can fit in the environment based on selected profile and all 3 default profiles (small, medium, & large) and what the initial constraint will be for growth (CPU, memory, or Storage).
  • Additional Hosts Recommended - How many more hosts are predicted to be needed in the selected cluster based on the default or custom profile used in the selected time period.
  • Advanced Statistics - These are essentially a roll-up of the resource modeling chosen, usage history that the prediction is made on and the thresholds and resources included in the report.


Cloud Infrastructure Monitoring for Microsoft Azure

Cloud Monitoring for Azure is now available to both VMAN & SAM customers. Similar to Cloud Infrastructure Monitoring for AWS the cloud vendor API will be used to monitor cloud instances. This basic cloud visibility doesn’t use Orion licenses for the cloud servers. For full details on performance and availability, you can optionally manage cloud servers as Orion nodes, which will consume licenses.  Additionally, if you add SAM application component monitors to your cloud instance this would obviously require SAM licenses.



What is included

  • Edit AWS/Azure Account using new UI (without editing API polling options)
  • Choose Instances/VMs for AWS/Azure Accounts
  • Azure VM’s polling, including performance metrics
  • Cloud Summary page accommodating instances for both cloud providers
  • Azure Cloud VM Details page with majority of resources
  • Monitor Azure VM as Orion Node (requires Orion node license)







VMAN 8.1 Release Notes - Virtualization Manager 8.1 Release Notes - SolarWinds Worldwide, LLC. Help and Support

Getting Started - Virtualization Manager (VMAN) Getting Started Guide - SolarWinds Worldwide, LLC. Help and Support

Admin Guide - VMAN 8.1 Administrator Guide - SolarWinds Worldwide, LLC. Help and Support

In continuance of the great Q3 release from SolarWinds (NPM, NTA, NCM, UDT, IPAM, DPA, & SRM), I am excited to announce the Generally Availability of Virtualization Manager (VMAN) 8.0.  Over time, Virtualization Manager has incrementally evolved from a stand-alone virtual appliance to providing advanced integration to the SolarWind's monitoring stack. VMAN Orion allows for a single pane of glass for troubleshooting (AppStack ), root cause analysis (PerfStack), and VMAN features found only on Orion (predictive recommendations).  In VMAN 8.0 we have taken this a step further by providing native VMAN functionality in Orion while removing the virtual appliance requirement.  Our goal with the release was to improve ease of use while strengthening VMANs ability to find and resolve problems in the virtual infrastructure.  The VMAN 8.0 download can be found in the SolarWinds customer portal.


Native VMAN Polling on Orion

It is now possible to download and install VMAN much like you would for SAM & NPM without upgrading and maintaining the VMAN appliance.  If you are currently integrated, it is extremely simple to migrate your VMAN polling to Orion by going to Virtualization Settings VMware Settings (or Hyper-V Settings).  Just select the vCenter or Hyper-V host to switch polling over and choose VMAN Orion Polling from the Polling Method drop-down menu.  In VMAN 8.0 there are 3 different polling methods that you will notice.

  • Basic - This is the general polling performed by SAM & NPM and does not require a VMAN license but it will require a SAM or NPM node license. ***Note - you can still use the basic polling method if you only have VMAN polling since the VMAN license is allocated node licenses equal to the socket count in your VMAN license, (e.g. 64 socket license = 64 node licenses).
  • VMAN Appliance - This is the traditional VMAN polling which occurs from the virtual appliance and requires that the appliance is integrated with Orion to get full VMAN functionality in Orion.
  • VMAN Orion - Full VMAN polling that occurs from Orion and does not require the VMAN appliance but does require a VMAN license



In addition to the new polling method in VMAN 8.0 we have added the ability to scale out your VMAN polling using the Additional Polling Engine (APE) framework for free.  No additional polling engine license is required to run with VMAN infrastructure monitoring.


Batch Execution of Recommendation Actions

The time it takes to optimize your environment has been drastically reduced with the ability to quickly select and batch multiple recommendations to execute immediately or schedule for a later time through just a few clicks.


VMAN will automatically configure the correct order of operations in which to perform the actions based on your selections.



Management action based recommendation policies


New policies in Virtualization Manager allow for greater control and precision over the recommendations which optimize your environment.  Create granular policy exclusions based on recommended actions for CPU, Memory, VM & Storage Migrations.

The new policy becomes available by selecting the Disallow Actions for Recommendations and then selecting the scope (vm, host, cluster, or datastore) to apply the policy against.  Then select the actions to exclude from recommendations for the scope chosen above.

  • Move VM - Actions based on VM movement/placement to a different host or datastore.
    • Move VM to a different host
    • Move VM to a different Datastore
  • Configuration - Modification of the VM memory or vCPU configuration
    • Change CPU Resources
    • Change Memory resources



PerfStack 2.0 - New Features & Improvements

With VMAN 8.0 we also get a new and improved version of Perfstack that continues to build on the tenants of SolarWinds to help dig into problems faster and identify true root cause across different IT disciplines.

    • Links from VM & Host Details that populate the PerfStack palette
    • Zoom into PerfStack charts to view more detail for the selected time period
    • Data ExplorerAlert visualization improvements
      • Export PerfStack data to Excel
    • Alert visualization improvements
      • Each individual alert start/end time is now visualized separately in PerfStack
      • Existing aggregate alert visualization against an object is retained
    • Export PerfStack data to Excel
    • Easier to share PerfStack dashboards with the new ‘Share’ button.
    • PerfStack 2.0 - Real-Time Polling

You can get to PerfStack from within the VM details page in three different spots (we wanted to make sure you didn't miss it.)

  • Virtualization Manager Tools
  • Virtual Machine Details
  • Resource Utilization



View of the PerfStack palette pre-populated with metrics of the VM.







    • Install and upgrade one or more Orion Platform products simultaneously
    • Modern interface with a simplified design and intuitive workflow
    • Downloads and installs only what is needed
      • Reduces download size & accelerates installation



Windows Authentication & SSL Encryption for Orion Microsoft SQL Database connectivity




Virtualization Manager (VMAN) - SolarWinds Worldwide, LLC. Help and Support


VMAN 8.0 Release Notes - SolarWinds Worldwide, LLC. Help and Support

If you have been keeping up with the Thwack product blog lately you know that Drag & Drop Answers to Your Toughest IT Questions revealed PerfStack, the new way to view performance analysis by visualizing and correlating data within the Orion web interface and Get Your Head Out of the Clouds, and Your Data Too identified that you can collect configuration and metric data directly from Amazon Web Services® (AWS), and have that data visualized along with the rest of the environment you are already monitoring in SAM 6.4 or VMAN 7.1.  This is great news for any administrator that needs to troubleshoot a Hybrid IT application with on-premises VMs and AWS cloud instances.


The good news is that Virtualization Manager (VMAN) 7.1 allows you to leverage the "new hotness" found in PerfStack and Cloud Infrastructure monitoring to correlate and pinpoint where the application performance issue is in your hybrid infrastructure. In the following example, we have a hybrid cloud application that has resources in the cloud (SQL AWS) as well as an on-premises virtual server (Analytics VM) both of which are monitored with VMAN. As with most IT incidents, the administrator is left trying to figure out what exactly is causing the performance degradation in their application with little to go on other than the "application is slow". Using PerfStack you can quickly dive down into each KPI and drag and drop the metrics you want to compare until the troubleshooting discovery surfaces what the issue is or isn't. The fact that VMAN contains cloud infrastructure monitoring means that you can add AWS counters from your cloud instances into PerfStack and correlate those with other cloud instances or with your on-premises VMs to troubleshoot your hybrid infrastructure with VMAN.



In the example above, the cloud instance, SQL AWS is experiencing some spikes in CPU load but it is well within the normal operating parameters while the on-premises VM, Analytics VM is experiencing very little CPU load. With PerfStack my attention is easily drawn to the memory utilization being high on both servers that participate in the application's performance and the fact that my on-premises VM has an active alert gives tells me I need to dig into that VM further.


By adding Virtualization Manager counters that indicators of VM performance (CPU Ready, ballooning, Swapping) I see that there are no hidden performance issues from the hypervisor configuration (figure below).

Perfstack -2.jpg

From the Virtualization Manager VM details page for the Analytics VM, I see that the active alert is related to large snapshots on the VM which can be a cause of performance degradation. In addition, the VM resides on a host with an active alert for Host CPU utilization which may be a growing concern for me in the near future.  To monitor hybrid cloud infrastructure in VMAN  allows the administrator the ability to create a highly customized view for discovery and troubleshooting with the contextual data necessary minus the alert noise that can regularly occur.


One of the added benefits of monitoring cloud instances with VMAN is that you can now build on the single pane of glass view that will be the monitoring authority for both your on-premises and cloud environment. Not only is it essential to have one place to monitor and correlate your data when applications span across hybrid environments but having visibility into both environments from Solarwinds allows you to determine what requirements will be necessary when moving workloads into your AWS cloud or off your AWS environment.


on-prem2.jpg         cloud-sum-2.jpg


For more information on PerfStack and Hybrid end-to-end monitoring, check out the following link.

Hybrid IT – Hybrid Infrastructure | SolarWinds


Don't forget to check these blog posts for deeper dives into PerfStack & Cloud Monitoring respectively.

Drag & Drop Answers to Your Toughest IT Questions

Get Your Head Out of the Clouds, and Your Data Too

Virtualization Manager (VMAN) 7.0 is now available with predictive and alert recommendations. VMAN 7.0 started with the basis to expand on Solarwinds current strengths of Discovery, Alerting, & Reporting and grow our toolset to provide advanced remediation and troubleshooting capabilities to support the *D.A.R.T framework. We tackled this challenge with intelligent actions that remediate existing alerts and predictive recommendations that pro-actively avoid downtime time and performance issue in your virtual infrastructure. Our goal was to stay true to Solarwinds tenants of simplicity and provide a toolset that was designed by systems engineers for systems engineers.  I feel confident that we have done that with VMAN 7.0.

What is included VMAN 7.0:


  • Updated UI Look and Feel - This release updated the SolarWinds Orion Web Console’s user interface, navigation, and notifications.


  • Predictive Recommendations - Advanced trending analysis is used to identify workload patterns of your virtual infrastructure to provide strategic recommendations. Based on historical data and trending, recommendations are created for Performance Optimization, Maximum Environment Utilization, and Problem Prevention.  Since these recommendations require historical data a minimum of 7 days of data is required.
      • Performance Optimization - Recommendations balance the workload of the virtual infrastructure to ensure the best performance is attained.  Based on historical trending, VMAN will identify the true work-load patterns, and determine where to place VMs. This ensures that all VMs have the necessary resources and that VMs residing on the same host have compatible workloads.
      • Maximum Environment Utilization - The goal of these recommendations is to ensure that the resources in the environment are leveraged to their full capacity with no loss of performance.  Essentially, do more with less!!
      • Problem Prevention  - These recommendations prevent situations where a lack of resources caused by resource depletion would affect the performance of a VM.


  • Active/Alert RecommendationsThese are tactical recommendations are that are meant to solve an immediate problem.  Think of these as alert recommendations, where their sole purpose is to resolve virtualization issues (aka put out an immediate fire)  or capacity issues as a result of an alert.  Since VMAN does not use historical data to make real-time recommendation it does not take into account future workloads when making the recommendation. Therefore only 1 hr of polling is required for VMAN to generate any necessary Active Recommendations.  These recommendations can be identified with a NOW icon preceding the recommendation.



Recommendations Walk-through


Header 1Header 2

Once you log into your VMAN integrated Orion Instance  you will immediately notice the updated UI and new Navigation bar.

1. From the My Dashboards drop-down choose Virtualization Summary from the list.


Once on the Virtual Summary page the new Recommendations resource can be found in the upper right hand corner.  The recommendations resource will provide you an at-a-glance view of clusters and their associated recommendations as well as the severity of the recommendation (Critical, Warning , Low).  This will be your gateway to recommendations.  You can access and view recommendations via 2 methods in the resource.

1. All Recommendations link -   This can be found in the upper right hand corner of the resource and will present all individual recommendations for all clusters.

2. Recommendations by Cluster link - This can be found in the third column next to the associated cluster it represents.  Entering recommendations using this link will pre-filter all recommendations to display only those associated to the host.


The severity references the the nature of the problem at hand based on Orion thresholds.


The All Recommendations page provides a high-level overview of individual recommendations.  This is broken out based the problem that needs to be solved on the left with the recommendation to remediate the problem on the right.  The ability to filter by Cluster/Host, Recommendation Type (Active/Predictive), and Problem Severity (Critical, Warning, or Low), or Strategy is available on the left-hand side of the screen.  Tabs across the top of the screen allow you to view current recommendations, scheduled, recommendations currently running, and completed/failed recommendations.


From this view it is easy to identify Active recommendations with the NOW tag preceding the recommendation.



GA-Image 1.png

By selecting an individual recommendation, related contextual details can be reviewed.  The recommendation details clearly break down the problem and the details of a recommendation to assist the administrator in making a decision to execute or ignore the action. Active recommendations will the associated alert that will be resolved by executing the recommendation. 


Additional actions can be found within the Steps To Perform tab such as power on/off the VM prior to performing the action. By default any migration action will not power off the VM unless the admin specifies.  All reconfiguration of Memory & CPU will power off the VM by default unless specified by the admin.




From here you can Apply, Ignore, Export & Schedule the recommendation








By selecting More Actions, an administrator can choose to ignore a recommendation to a later date.  This will remove the recommendation from the list until the specified date and will only return the recommendation if it is still valid.

GA-Image 3.jpg



The Statistics tab will provide advanced graphical data to provide context as to why a recommendation has been created for your environment.  All graphs will have a Now delimiter line in the graph to identify the expected results on the virtual environment after the proposed recommendation is applied. Metrics associated to counters used for the recommendation will provide a current and predicted value.


TIP:  You can zoom in on the graph by selecting a section and sliding your cursor  across the graph.




SImilar to the Steps to Perform tab the recommendation can be applied, ignored or exported.

GA-Image 4.jpg


GA-Image 4-2.jpg

To view running recommendations choose the RUNNING tab on the all recommendations page.  Running will provide you the current status of an in-progress recommendation with a progress bar indicator next to the action being run.  To cancel a running recommendation select Cancel & Revert .


To view all past recommendations choose the HISTORY tab on the all recommendations page.  This will display both successful and failed recommendation attempts as well as time initiated and time completed.


Double click on the completed recommendation to view details such as who executed the action and steps performed in the action.




In the event that a recommendation is no longer required for an entity select Manage Policies from the All Recommendations Page and select the Policies tab.


From here the admin can select the Add Exclusion.  The next screen will provide the option to select the object types you want to exclude (virtual machine, cluster, host, datastore).


After selecting the objects to exclude the exclusion policy can saved.


This will exclude the object from all future recommendation calculations until the exclusion policy is removed.

GA-Image 5.jpg



GA-Image 5-2.jpg


GA-Image 5-3.jpg

By selecting the Strategies Tab the recommendations can be completely disabled.  The individual strategies can be disabled/enabled from this page.


VM Right Sizing




Host Performance & Capacity Assurance - Identifies hosts that will run of CPU or memory resources.

Active recommendations

Predictive recommendations


Storage Capacity Assurance


Balancing VM Workloads on Hosts


Selecting Recalculate Now the recommendation calculations can be manually run.  The default running of the calculations occurs every 12 hrs unless an environment change occurs in which case the recalculation will immediately run.  An environment change includes:

  • add/remove VM
  • add/remove Hosts (including maintenance mode)
  • Add/Remove storage
  • Migration of VMs to another host
  • Migration of VMs to different storage
GA-Image 6.jpg



Existing customers can find the VMAN 7.0 & VIM 7.0 download files from the customer portal and new customers can find the download links here.  Visit the VMAN 7.0 customer support center to find all information related to VMAN 7.0 install and upgrades.


Before upgrading :

  • VMAN 7.0 requires Orion Platform 2016.2, NPM 12.0.1, SAM 6.3, NCM 7.5.1. VIM 7.0 released with VMAN 7.0 includes Orion 2016.2. You must upgrade to Orion Platform 2016.2 products to upgrade to VMAN 7.0.


  • For VMAN integrated with the Orion Web Console, you need to upgrade to VIM 7.0. Regardless of your installed Orion product version (such as NPM 12.0.1 or SAM 6.3), you should run the VIM 7.0 upgrade. This upgrade includes additional feature additions and fixed issues.

The VMAN 7.0 RC 2 install bits can now be downloaded from your Customer Portal.  Please note that the Release Candidates are fully tested and supported releases and are suitable to be run in production. 7.0 RC2 can be run as an upgrade from 7.0 RC1, as well as from the 6.3 installs. If you have problems with the RC, you can file a ticket with Support just as you would for any other Generally Available (GA) version.  To familiarize yourself with new features in 7.0 you can use Welcome to the Virtualization Manager 7.0 Beta 1 as a reference.


VMAN RC2 Button.png


The VMAN team is excited about this release and can't wait to receive your feedback in the Virtualization Manager Release Candidate forum. Make sure to review all documentation prior to the upgrade which can be found on the VMAN 7.0 Support page.



New features and improvements

Read this section for descriptions of the new features and improvements VMAN and VIM offer in this release.



When VMAN identifies a way to optimize VM resources for active and potential issues, it makes a recommendation for one click optimization. Recommendations display in the Orion Web Console with a description for optimizing your network, and provides a series of steps you can apply immediately with a button click or schedule at a later time.

  • Balance the virtual environment for optimal performance. You can spread load over hosts, which optimizes the performance for all virtual machines.
  • Optimize capacity. Virtualization Manager predicts when you will run out of resources on virtualization entities, so you can plan in advance when you have to assign new resources.
  • Predict possible future performance and capacity issues based on past trends.


Web-based License Manager

Easily add, activate, and manage Orion product licenses through the web-based License Manager. Accessing the License Manager on your main polling engine, you can monitor and update full product and evaluation licenses for your main poller, additional pollers, additional web servers, stackable pollers, and high availability pools all through one page. The License Manager also provides automatic online and offline modes for managing licenses. Add and manage evaluations with ease, including HA.

text-document.png Read more about these changes.


Other improvements

Various performance improvements and security fixes

How to upgrade

Use the following resources for planning and upgrading:

Fixed issues

Virtualization Manager 7.0 and VIM 7.0 fix the following issues.





NPM not showing CUP and Memory usage for some ESXi servers


Asset tree is not loading properly


List of Virtual Machines on a host not displaying the OS version for Windows 10



Collector Data Processor keeps crashing


VCenter data is inaccurate


Additional Orion Web Server VM reports do not run


VM to node mapping is not using MAC if integration is enabled

916806 not returning any data - duplicated datastores causing data processing to fail


VCenter status unknown on the Orion Web Console


IVIM schema error on APE SWIS log


Polling Engine Details page shows absolute value of jobs count instead of percent


Issues with vShield Manager and VMs that are natted


Orion Web Server does not display


Unable to start collection jobs


CPU overallocation


VMAN on-demand report displaying incorrect or old data


Integration issue with Datastore and VMAN


VIM appliance not passing data to the Orion server


SSH Server CBC Mode Ciphers enabled


Vcenter status unable to poll


Invalid depletion data shown on Datastore dashboard for VMAN


Vcenter data not being displayed in the Orion Web Console


SSL certificate changes back to default after upgrade


False alerts regarding VM reboots


VMAN application unable to load because postgres service will not start


VMAN crashes when a secondary collector is used


Host rebooting during configuration collection


Blue screen on host when running the configuration wizard, when collection has started


No data displayed in the "" column


Trend widget does not populate when "multi-trend" mode is enabled


VMAN stops working after upgrade to vSphere 6.0


Query does not return the correct number of VMs when searching past 9 days


Intermittent collection


Mast applicance shows ActiveMQ transport "Usage Manager Memory Limit is full errors"


Fatal error occurred during collection


VMAN stopped polling and displaying data


Virtual Machine not appearing in VMAN list



Download VMAN from the Release Candidate section of your Customer Portal.


VMAN RC2 Button.png

Not all virtual environments are alike, the default out-of-the-box configuration of the virtual appliance is not necessarily best suited to environments of all sizes, and those particularly large environments may want to consider adjusting some of those default settings for optimal performance.  To take advantage of the features that have been added to VMAN over the last several releases requires Orion integration, which makes correctly configuring VMAN extremely important for performance and scalability. The VMAN Sizing Guide was created to assist with the preliminary setup and configuration of both the Virtualization Manager appliance and the integrated Orion server. 


To access the guide click here.


The the following items are addressed based on the number of VMs to be polled.


·       Memory, CPU, and storage considerations for the VMAN appliance

·       Memory, CPU, and storage considerations for the Orion server when integration is enabled

·       Identify when federated pollers are needed

·       Identify when to deploy Orion APEs to distribute the workload when integration is enabled

·       Advanced fine tuning of the VMAN appliance for Optimal performance

·       Necessary hotfix install version to solve integration issues

·       Fixes for database size issues



The guide is organized into small, medium, and large deployment recommendations to help you determine the starting configuration size for your VMAN and Orion deployment. Not all possible scenarios are included in this document, so consider the recommendations in this document as guidelines.  This is not an exhaustive list of all the fine tuning and performance tweaks that can be made, if you are still having performance issues than please reach out to your sales engineer or support contact.  They should be able to walk you through some advance tuning recommendations that would be specific to your virtual environment. 


Click the following  button for the VMAN Sizing Guide.

VMAN Sizing Guide.png

I am excited to announce that Server & Application Monitor (SAM) 6.3 Beta 3 is now available . The team at Solarwinds has been hard at work at producing the next release of SAM with some great new features that continue from the SAM 6.3 Beta 1.  The Beta is open to SAM customers currently on active maintenance.  The beta is the best opportunity to provide feedback and have direct input which can affect this release and improve the usability of SAM.  We encourage all to sign-up and kick the tires.  Just as in beta 1 your feedback might just earn you some much deserved Thwack points that can be redeemed for some cool SolarWinds SWAG!


The SAM 6.3 Beta 2 includes some of the features mentioned in the Server & Application Monitor - What we're working on beyond SAM 6.2 post. Don't forget to signup for the Beta and provide your feedback in the Server & Applications Monitor Beta forum!!


Beta 2 Button.png

VMAN 6.3 is now generally available to all customers to download and in the Customer Portal for for current customers.

What is the Goal of this Release

The SolarWinds team has been working diligently to release Virtualization Manger 6.3, which continues the evolution of VMAN to an operational management and monitoring platform for the virtual infrastructure. As you have seen VMAN evolve over the last couple of releases we focused on providing monitoring utility, troubleshooting utility and reporting utility.  Culminating with VMAN 6.2 management utility was added by providing power management actions, snapshot management actions and AppStack support (to name a few features). With the release of Virtualization Manager 6.3 we further extend the operational role of VMAN with the end goal of providing remediation utility to the mix of features we provide. Not only does an administrator have the tools to identify and troubleshoot an issue in the virtualization infrastructure but they can also remediate the problem within VMAN.

What's New in Virtualization Manager 6.3

This is the 1st of several blog posts reviewing the new features of Virtualization manager 6.3. Provided below is a high level overview of what is new in VMAN 6.3:


New Management Actions

In Virtualization Manager (VMAN) 6.3, we further enhanced the existing management functionality by including migration actions, VM removal actions, and change CPU and memory actions.

  • Migration Management Actions
    • Move VM to a different host - Provides the ability to migrate a VMware® or Hyper-V® virtual machine to a different host within VMAN.
    • Move VM to different storage - Provides the ability to migrate VMware or Hyper-V virtual machine storage to a different datastore or Cluster Shared Volume (CSV) from within VMAN.
  • VM Removal Actions
    • Delete VM – Provides complete removal of the VM from the virtual infrastructure once the VM is turned off.
    • Unregister VM – Removes the VM machine files form the hypervisor but leaves behind the VMDK files on disk once a VM is shutdown.
  • Change CPU/Memory Resources Management Actions
    • Add/Remove CPU - Grow or shrink the amount of virtual machine CPU from within VMAN.
    • Add/Remove RAM - Grow or shrink the amount of virtual machine RAM from within VMAN


The Virtual Manager Tools can be found on the virtual machine details page and are conveniently accessible to remediate a virtualization manager alert with out leaving Solarwinds.  For instance an administrator may get a virtualization alert that indicates a VM with high disk latency, they could now initiate a storage vMotion or live migrate the VM to a different datastore or CSV from within Virtualization Manager to resolve the alert.


Execute management actions directly from the Sprawl page

Not only do we alert the administrator to Sprawl issues in the virtual infrastructure we also provide the the appropriate management action to remediate the problem on the Sprawl page.

    • Top 10 VMs by Overallocated vCPUs - Change CPU/Memory Resources
    • Top 10 VMs by Underallocated Memory - Change CPU/Memory Resources
    • Top 10 VMs by Overallocated Memory - Change CPU/Memory Resources
    • Top 10 VMs by Snapshot Disk Usage - Delete Snapshots
    • VMs Powered Off for More than 30 Days - Delete VM
    • VMs Idle for the Last Week - Power off VMs
    • VMs that might benefit from decreasing vCPUs - Change CPU/Memory Resources (Decrease vCPU)
    • Orphaned VMDKs (New Sprawl Resource) - Delete Orphaned VMDKsTop 10 VMs by Underallocated vCPUs - Change CPU/Memory Resources



An administrator monitoring their virtualization environment can use the Sprawl page to inform them of areas in which they can right size to reclaim resources or improve performance.  For an IT team that has has multiple administrators provisioning virtual machines it becomes a task in itself to determine which resources were temporary and no longer needed.  By leveraging the VMs Powered Off for More Than 30 Days alert to identify virtual machines that are no longer needed , the administrator can identify what needs to be deleted and then remove the unnecessary VM from the Sprawl page.

New Sprawl Resource - Orphaned VMDK

This new resource to the Sprawl page alerts to any orphaned VMDKs in the monitored environment.  Orphaned VMDKs are virtual hard-disks that are not connected to a VM. Most likely the result of removing the VM from inventory but never deleting the vmdk file and thereby using valuable datastore capacity.

Orphaned VMDK.jpg
A virtual administrator is alerted that they have multiple orphaned VMDKs files from VMs that were unregistered from the cluster but never deleted from disk.  They can now track and take action using the Orphaned VMDK resource and open up valuable Disk storage by deleting the unneeded VMDK files.

Alert Remediation

Provides the ability to configure an alert to trigger a management action based on a threshold.  By providing management actions as a trigger for an alert the administrator can now choose to automatically remediate any alert that crosses a critical threshold without needing to manual perform the management action.

Alert triggers.jpg

The ability to create an alert with a management actions as a trigger is valuable by ensuring up-time for a VM or maintaining performance of an application hosted on that VM. The administrator in charge of the server infrastructure is always concerned about the next time a threshold is reached, how fast can they react to that issue, and how that may affect the application that resides on the VM.  Creating an alert and setting a management action as a trigger helps to reduce the Time To Resolution for the affected VM without the administrator manually needing to execute the action.  For example, if there is a reporting server that does all its heavy lifting from 12 am - 5 am and application performance is suffering from datastore latency, an alert action can trigger a migration of VM storage to a destination predetermined by the administration if the latency threshold is crossed. This would ensure that the VM has the storage performance that is necessary to complete its workload (reports) before the administrator arrives in the morning.



All Alerts Dashboard Migrated to Orion

All Alerts.jpg

Migration of the all alerts alerting widget from the Virtualization Manager (VMAN) appliance to the Orion® Virtualization Summary, provides customers with a VMAN specific data of the environment from the Summary page. The very useful All Alerts widget is now available in as two resources, All Active Virtualization Alerts and Potential Virtualization issues.  The resource provide virtualization alerting in Orion Out-of the-Box with all VMAN alerts enabled by default when Orion is integrated with VMAN. Each triggered alert provides an alert details page with recommendations to take to resolve the issue, general alert details, and a link to the VM details view.


  • All Active Virtual Alerts -  Provides a view of all triggered virtualization specific alerts with a severity of warning or higher.  All alerts in this resource indicate a problem that is affecting performance or functionality in the virtual infrastructure and should be prioritized accordingly.  These alerts are sorted by active time and provide the following details:
    • Alert name
    • Alert message
    • Triggering Object (i.e VM, datastore, host, etc)






  • Potential Virtualization Issues - All triggered alerts with low severity and grouped by alert name.  These alerts notify the administrator of items that require attention but do not necessarily equate to a critical issue.  The VMs with Bad Tools alert is an example of this scenario, which notifies the administrator that the virtual infrastructure contains VMs that require a VM tools update but this does not necessarily ensure that the VM is having a critical performance issue.


  • Categories without issues - This resource provides Virtualization Manager specific alerts that have not been triggered but do provide a glimpse into what alerts are enable out-of-the box. Unlike the Potential Virtualization Issues resource and the All Active Virtual Alerts resource these alerts are not select-able and do not provide an alerts detail page.

Polling Improvements

We have improved polling performance in Virtualization Manager 6.3 allowing for on demand data polling and improved scaleability. Common use cases that improved polling addresses are situations where the virtual topology changes due to management actions, maintenance, or provisioning but VMAN fails to reflect the new VM to host or datastore association in a timely manner. In VMAN 6.3 once a migration management action is executed, the topology change is reflected within minutes. An administrator who receives a virtualization alert and resolves the alert with a management action will see the results of the action immediately within Virtualization Manager.


SolarWinds Virtualization Manager v6.3 Release Notes

Coming fresh off the Virtualization Manager  (VMAN) 6.2 release in which we added management action functionality (power management and snapshot management) and AppStack support (to name just a few features) the VMAN team is already working on the next set of features. I am excited about what we have planned for VMAN as we transform it into a one stop monitoring and virtual management tool. Here are the highlights of what we have we are currently working on:.


  • New Migration management actions
    • vMotion/Live Migration - Provide the ability to migrate a VM to a different host within VMAN
    • Storage vMotion/Storage Live Migration - Provide the ability to migrate VM disks to a different datastore or shared cluster volume from within VMAN.
  • Sprawl Management Actions
    • Add/Remove CPU - Grow or shrink the amount of virtual machine CPU from within VMAN
    • Add/Remove RAM - Grow or shrink the amount of virtual machine RAM from within VMAN
    • Delete VMs - The ability to remove/ delete unnecessary virtual machines for the purpose of reclaiming resources from within VMAN
    • Delete Orphaned VMDKs - Provide the ability to delete orphaned VMDKs from the Virtualization Sprawl resource “Storage being used by Orphaned VMDKs” so that I can reclaim datastore storage from the alert.
  • The ability to act on virtual sprawl alerts from within the VMAN Sprawl page.
    • Over-allocated & Under-allocated resources - Add/Remove CPU & RAM
    • VMs Powered Off for More than 30 Days - Delete VMs
    • VMs Idle for the Last Week - Shutdown VMs
    • VMs that might benefit from decreasing vCPUs - Decrease vCPU
    • Top 10 VMs by Snapshot Disk Usage - Delete Snapshots
    • Orphaned VMDKs (New alert) - Delete Orphaned VMDK
  • Alert Remediation - Provide the ability to configure an alert to trigger a management action based on a threshold..
  • Red Hat Enterprise Virtualization support
  • Citrix XenServer Support
  • Recommendations - Recommended actions to take to ensure performance, optimal capacity, avoid potential issues, and improve uptime.
  • vCenter and Hyper-V Events
  • Improved scalability and performance of polling


Disclaimer:  Comments given in this forum should not be interpreted as a commitment that SolarWinds will deliver any specific feature in any particular time frame. All discussions of future plans or product roadmaps are base on the product teams intentions, but those plans can change at any time.


If you don't see what you are looking for here, you can always add your idea(s) and vote on features in our Virtualization Manager Feature Requests forum.

The Virtualization Manager 6.2 Release Candidate (RC) is now available in the Customer Portal for customers on active maintenance through 04/01/2015.  Release Candidates can be installed on the production system you have running today and you can contact support with any Release Candidate issues you may encounter. The Product Management team would love to hear your feedback on the RC at the Virtualization Manager RC Forum on Thwack. We also ask that you fill out the following survey to provide us some information regarding your virtual environment.

The latest release of Virtualization Manager (VMAN) is full of new features, some of which were covered in the following post:


  • AppStack
  • Management Actions
  • Co-stop % Counter
  • Web based Reports
  • Web Based Alerts
  • Appliance password Improvements



Stand-Alone Virtualization Manager on Orion

With all the talk of integration with Orion, those customers that only own Virtualization Manager are probably asking "what about me?!!"  The answer is a stand-alone Orion Virtualization Manager Module that integrates with the VMAN virtual appliance.  This stand-alone module does not require NPM or SAM to be installed and provides access to all the goodness we have baked into VMAN for Orion such as baseline thresholds, web based reporting, advanced alerting, and role-based access control to name a few.


The goal of integration with Orion is not to simply have virtualization tabs in Orion but to improve on ease of use and reduce the time to resolution by providing tools available in Orion today.  Your feedback has made it clear that ease of use is paramount and we are addressing this by implementing features in the Orion platform which improve usability. Whether you are an administrator wearing many hats (network admin, sys admin, desktop support) and managing small virtual environment or a virtual administrator trying to get your arms around performance issues of thousands of VMs across multiple data centers, VMAN provides a simple and easy to use interface that will help you diagnose current issues and provide you with useful data to get ahead of future performance problems.

Hotfix Install Improvements

A new hotfix implementation method has been added to the Virtualization Manager appliance.   First Step - Navigate to https://ipaddress:5480/ where IPaddress is the address of the virtual appliance server management page. Once logged in select the SolarWinds Mgmt tab and choose HotFix install.  The hotfix install will let you browse to the install package and install the hotfix automatically.  It is that simple; no more logging into the appliance console and manually typing in command parameters to install a hotfix.


Fixed Issues

IssueCase Number
Virtual hosts are not linked properly to Orion nodes.666113, 735396, 706484, 676201
Host to vCenter mapping does not work correctly.712659
ESX host is displayed as down even when it is running.333590, 395330
Dashboard reports are created with incorrect time frames.566645
Labels cannot be removed from Virtualization Manager.694726
No latency information is collected for Hyper-V CSV datastores.-
Issues with local datastores.630786, 677971
The alert history of a configuration items gets cleared incorrectly.642124
Incorrect information is displayed in Virtualization Manager about connected media devices.576193
Issue with data segments not being displayed on Virtualization Manager charts.585989
Incorrect values are displayed as VM Tools status.610075
When multiple trends are added to a widget, a flat line is displayed for some trends.621536
Sorting on the Trend widget does not work properly.621811
Issues with filtering results by VMware Tools status in Virtualization Manager.625185, 625346
The fitment widget report does not work with custom Resource Containers.619730

Don't forget to leave your RC Feedback at Virtualization Manager RC Forum on Thwack.

Patch Manager 2.1 is now Generally Available and available for download in the customer portal for all customers on active maintenance!!!!! All features described in the Beta post along with multiple bug fixes were addressed in this release.



The team at SolarWinds has been hard at work at producing the next release of Patch Manager with some great new features. It is my pleasure to announce Patch Manager 2.1 Beta which is packed full of features and is open to Patch Manager customers currently on active maintenance. To try it out please fill out this short survey and provide us your feedback in the Patch Manager Beta forum.




Automated 3rd Party Patching and Publishing

Patch Manager currently offers 3rd party patch/updates through our 3PUP catalog so that administrators can simply update their products using Patch Manager as they would for Windows Patches.  In Patch Manager 2.1 we have introduced Automated Third Party Patching and Publishing which will save administrators time by automating the publishing of 3rd party updates to WSUS in the same way Microsoft updates distribution points.  This reduces the number of touches and time required to publish the 3rd party updates by allowing the local Microsoft WSUS server to automatically download 3rd party patch content on a scheduled basis and automatically publish.  An additional option can be set which automatically approves certain patches based on criteria (typically severity) and provide a scope for automatic approval. For a complete list of supported 3rd party updates check out Table of third party patches - updated 1/21/2015Follow the steps below for enabling and configuring Auto-Publish of 3rd Party Updates to WSUS.


Opening the Auto-Publish of 3rd Party Update Wizard

In the Patch Manager Console select Administration and Reporting - Software Publishing - Right click and choose Auto-Publish of 3rd Party Updates to WSUS.  Alternatively you can select Auto-Publish of 3rd Party Updates to WSUS in the actions panel after highlighting Software Publishing.


3rd party3.JPG

Selecting Products and Specify WSUS

Select the WSUS server that will be publishing the 3rd party update and select the software to have published.

3rd party.JPG


The schedule screen allows you to select your Auto-Publishing schedule. You may choose to have a set period of time to publish as a schedule task or auto-publish after every synchronization. In addition email notifications can be configured on this screen as well.






Scheduled Tasks

Once done, you can review and edit you auto-publish task by selecting Scheduled Tasks under Software Publishing

scheduled tasks.jpg




Report Enhancements

Patch Manager contains volumes of data and environment metrics that can be reported. An important aspect of Patch Management is the ability to perform essential reporting of your environment for compliance and remediation purposes.  We have improved the out-of-the-box reporting by replacing dated reports with relevant and more intuitive reporting options. In addition the following reports have been added or modified based on demand from the Thwack user community.



Custom hardware report

Configuration Management Reports - Computer (System Information) - Custom hardware report

You no longer have to build a hardware report from scratch. The Custom hardware report can be configured using any of the existing 19 available data sources with each source having multiple fields.

HW Report.JPG

HW Report 2.JPG

Installed programs and feature basic

Configuration Management Reports - Installed Programs and Feature Basic (MS Products Omitted)

The default Installed Programs and Feature Basic (MS Products Omitted) report can easily be modified to omit MS products specific to your environment.

MS Office Omited.JPG

Approved updates status counts by WSUS server and update source

WSUS Reports - Windows Server Update Services Analytics Approved updates status counts by WSUS server and update source

Provides the WSUS server name, update source and total sum of approved updates in the following categorizations:

  • Approved not installed
  • Approved unknown
  • Approved downloaded
  • Approved failed
  • Approved installed
  • Approved pending reboot
  • Approved total

Computer update status - locally published updates

WSUS Reports - Windows Server Update Services Analytics - Computer update status - locally published updatesThis Out-of-the-box report identifies all updates that do not have Microsoft Update as a source

Computer update status with aggregate counts of install state for approved updates

WSUS Reports - Windows Server Update Services Analytics - Computer update status with aggregate counts of install state for approved updatesThis report provides an aggregate count all approved updates that are applicable to a particular computer/server and in which phase of install.

Computer Update status counts by classification for approved - not installed

WSUS Reports - Windows Server Update Services Analytics - Computer Update status counts by classification for approved - not installedProvides a list of all approved updates that have not been installed on a computer.

Computer Update status - Approved updates with ID and Revision

WSUS Reports - Windows Server Update Services Analytics - Computer Update status - Approved updates with ID and RevisionProvides a comprehensive report of all approved updates and their status as it pertains to each computer/server.

It is important to note that all Out-Of-The-Box reports are configurable with hundreds of data sources and fields. Customization of reporting has been greatly enhanced in Patch Manager 2.1 with the addition of Cross-Datasource Reporting. This provides users with the ability to write reports without worrying about the specific data sources hampering real creativity within the reporting engine. 

Logging Enhancements

We have enhanced the log collection functionality in Patch Manager by centralizing and bundling of logs which will assist in the troubleshooting of Patch Manager.  By extending the existing Orion diagnostic tool an administrator can now collect the relevant logs and review for diagnostic evaluation or submit to support.  This eliminates having to browse to individual directories to gather separate logs.



Windows 2012 R2 and Windows 8.1 Support

Windows 2012 R2 and Windows 8.1 are now OS options when selecting computer properties.

new OS.JPG

Notification Bar Enhancements

A banner notification has been added to the web console to notify the administrator that new patches are available.


Additional Computer Group Scoping Options

You know have 3 three additional grouping options to allow management and task targeting at subnet, AD organizational unit and/or site levels.This provides granular device grouping options depending on the task at hand when creating computer groupings.

Scoping optionsHeader 2
IP Subnet - You now have the option to target a subset of machines based on a specific subnet.



Active Directory Organizational Unit (OU) -  Patch Manager administrators are able to target all computers within an Active Directory Organizational Unit.options.JPG
Active Directory Site -  You can now group computers by Active Directory Sites as a possible element in routing requests to automation servers. Larger environments with multiple Patch Manager servers require automation routing rules to assign tasks to specific Patch Manager servers based on the IP of the machine in question.




That's it for now.  Don't forget to sign up for the Beta and provide your feedback in the Patch Manager Beta forum

The team at Solarwinds has been hard at work at producing the next release of Virtualization Manager with some great new features. It is my pleasure to announce Virtualization Manager 6.2 Beta which is packed full of features and continues VMAN's journey of integration with Orion. The Beta is open to VMAN customers currently on active maintenance, to try it out please fill out this short survey.


VMAN Beta button.png



Beta Requirements

Orion integration with VMAN Beta 1 will require an install of the SAM 6.2 Beta.  Check out the the 3 part blog post (links to the blog posts can be found here) which details the new features of SAM including AppStack support for end-to-end visualization of the environment: App > Server/VM/Host > Storage (datastore).  As a reminder, beta software is for testing only and should not be used in a production environment.



Essential to diagnosing an issue (or preventing one) is understanding dependencies and relationships in a virtual environment.  Most administrators start troubleshooting an issue armed only with the knowledge that an application is slow or a server process is functioning sub-optimally.  AppStack provides an at-a-glance view of environmental relationships by mapping dependencies end to end and providing easily identifiable statuses which can quickly be used to identify root cause.  If a VM is reporting high latency an administrator can quickly identify the datastore, host, and related VMs to determine where the issue may be.  In cases where NPM, SAM, and VMAN are integrated, AppStack can quickly identify if a SAM threshold alert is attributed to network latency or virtual host contention.


AppStack can provide a view of your entire environment with relational dependencies visible end-to-end.  Status from additional integrated SolarWinds products such as SAM, SRM, and WPM are provided and the relationship mapped to the virtual environment.



AppStack is also visible from an individual Virtual Machine's Details View and displays the relational context of that virtual machine only.



Management Actions

A great new feature is the ability to perform virtual management actions without leaving Virtualization Manager.  With all your virtualization monitoring information available you can make a decision to stop, start, or  pause a VM from within VMAN.  In addition to power management options a Virtual Admin can also create and delete snapshots without ever leaving the VMAN console or logging into vCenter. An administrator can now act on an alert they see in the dashboard such as VMs with Old Snapshots and then delete those snapshots from within Virtualization Manager.  The addition of management actions also allows a Virtual Administrator to delegate operational tasks to non-virtual admins or teams (such as helpdesk) without providing access to vCenter.

Mgmt actions 1.JPG


Management ActionsWhat you will see

Power Management Actions

  • Power Off VM
  • Suspend VM
  • Reboot VM

Selecting a power management action will present a pop up confirming your action.


Snapshot Management Actions

  • Take Snapshot of VM
  • Delete Snapshots

Creating a snapshot will present you a pop up to Confirm the snapshot and create a custom name.

Create Snapshot.JPG

Deleting a snapshot will present a pop up to select a snapshot to delete.


Delete snapshot.JPG

Management Action Permissions

To execute management actions, the account used to configure the credentials that SolarWinds will use to contact your Virtual Center, must be given the necessary vCenter Server permissions. The minimum vCenter Server permissions required are:


  • Virtual machine > State > Power Off
  • Virtual machine > State > Power On
  • Virtual machine > State > Reset
  • Virtual machine > State > Suspend
  • Virtual machine > Snapshot management > Create snapshot
  • Virtual Machine > Snapshot management > Remove snapshot

Note: In vCenter Server 5.0 the location of snapshot privileges is below:

  • Virtual machine > State > Create snapshot
  • Virtual Machine > State > Remove snapshot


Managing access to the Management Actions within SolarWinds

Once permissions are set on the account used to connect to vCenter you can delegate access within SolarWinds to execute the management actions. The default permissions for management actions is set to Disallow which disables the virtual machine power management and snapshot management options.  To enable these features for a user or group select Settings in the upper right hand corner of Orion.  Then select Manage Accounts found under User Accounts and select the account or group to edit. Expand Integrated Virtual Infrastructure Monitor Settings and select Allow for the management action you wish to enable.


Mgmt Actions Permissions.JPGVirtual Machine Power Management

     Allow - Enable the options to start, stop, or restart a virtual machine.

     Disallow - Do not enable the options to start, stop, or restart a virtual machine


Snapshot Management

    Allow - Enable the options to take snapshots of a virtual machine, or to delete snapshots.

    Disallow - Do not enable the options to take snapshots of a virtual machine, or to delete snapshots.


If an admin attempts to perform a management action without being provided access within Solarwinds they will receive an error similar to the one below.

failed snapshot.JPG



Co-stop % Counter

A new counter has been added the VM Sprawl dashboard that is useful for detecting when too many vCPUs have been added to a VM thereby resulting in poor performance.  Co-Stop ( %CSTP as it is represented in ESXTOP) identifies the delay incurred by the VM as the result of too many vCPUs deployed in an environment.   Any value for co-stop above 3 indicates that virtual machines configured with multiple vCPUs are experiencing performance slowdowns due to vCPU scheduling. The expected action to take is to reduce the amount of vCPUs or vMotion to a host with less vCPU contention.



CoStop - VIM.JPG


Web Based Reports

Web-based reporting introduced in VMAN 6.1 allowed us to represent all data in the VMAN integration in the web based report writer bringing about an easy way to create powerful customizable reports in an easy to use web interface.  We have extended this functionality to include out--of-the-box web based reports found previously only in the VMAN console. These new web based reports include:


    • Disconnected Hosts
    • High Host CPU Utilization
    • Hosts with Recent Reboots
    • Newly Added Hosts
    • Datastores in Multiple Clusters

    • All VMs
    • Existing VMs with Recent Reboot
    • High VM CPU Utilization - Latest
    • High VM Memory Utilization - Latest
    • Linux VMs
    • Low VM CPU Utilization – Day
    • Low VM Memory Utilization – Day
    • Newly Added VMs
    • Stale VMs – Not Recently Powered On
    • VMs configured for Windows
    • VMs that are not Running
    • VMs Using over 50GB in storage
    • VMs Using Thin Provisioned Virtual Disks
    • VMs With a Bad Tools Status
    • VMs With a Specific Tools Version
    • VMs With Less Than 10% Free Space
    • VMs With Less Than 1GB Free Space
    • VMs With Local Datastore
    • VMs With More Than 20GB Free Space
    • VMs With More Than 2 snapshots
    • VMs With No VMware Tools
    • VMs With old snapshots (older than 30 days)
    • VMs With One Disk Volume
    • VMs With One Virtual CPU
    • VMs With One Virtual Disk
    • VMs With over 2GB in snapshots
    • VMs With RDM Disks
    • VMs With Snapshots
    • Windows VMs
    • High Host Disk Utilization
    • VMs on Full Datastores (Less than 20% Free)
    • VMs Using More Than One Datastore

Web Based Alerts

As discussed in the Virtualization manager 6.1 blog post web based reporting was introduced which allowed virtual administrators to take advantage of baselines and dynamic thresholds. Originally we only included only a small subset of standard VMAN alert out-of-the-box but we now have now extended these out-of-the-box alerts to include:


ClusterHostVMDatastore/Cluster Shared Volume


    • Cluster low VM capacity
    • Cluster predicted disk depletion
    • Cluster predicted CPU depletion
    • Cluster predicted memory depletion

    • Host CPU utilization
    • Host Command Aborts
    • Host Bus Reset
    • Host console memory swap
    • Host memory utilization
    • Hosts - No heartbeats
    • Hosts - No BIOS ID
    • Host to Datastore Latency

    • Guest storage space utilization
    • Inactive VMs - disk
    • Stale VMs
    • VM - No heartbeat
    • VM Memory Limit Configuration
    • VM disk near full
    • VMs with Bad Tools
    • VMs with Connected Media
    • VMs with Large Snapshots
    • VMs with Old Snapshots
    • VMs With More Allocated Space than Used
    • Disk 100% within the week
    • VM Phantom Snapshot Files
    • Datastore Excessive VM Log Files


Appliance Password Improvements

With ease of setup provided by the virtual appliance it is easy to overlook changing the appliance admin account (Linux password) or the Virtualization Manager admin account password.  In Virtualization Manager 6.2 the initial login will now display a password change reminder with links that will easily change both passwords.

Password change.JPG

Linux Password.JPG 

That's it for now.  Don't forget to sign up for the Beta and provide your feedback in the Virtualization Manager Beta forum

VMAN Beta Button 2.png

To receive updates on the Virtualization Manager  roadmap, JOIN thwack and BOOKMARK this page.

We are currently working on Virtualization Manager 6.2 and beyond.  Some of the items we hope to deliver:



  • Stand-alone Virtualization module on Orion Platform. Once installed, you have a "Home" and "Virtualization" tab no NPM or SAM required, though they continue to ship with the virtualization support they have today.
  • Application stack integration and visualization (e.g. visual mapping through the entire application stack to help identify root cause of performance and availability issues)
  • Management resources to allow users to take simple actions in their virtual environment (e.g. Start/Stop/Reboot a VM, Take recommended resource correction (increase/decrease and reboot) as recommended by VM Sprawl, Take/Delete a snapshot)
  • Better handling of Hot Fix installs for VMAN Appliance
  • Add Costop % Counter (VMware)
  • Out-of-the-box (OOTB) reports for VMAN on Orion
  • Port remaining VMAN alerts to Orion
  • Capture per VM HBA and per VM NIC data
  • Add SAM Template for VMAN to SAM for monitoring VMAN (aka "who watches the watchmen")
  • Support for VMware Tags
  • Licensing usage and upgrade messaging improvements
  • Support for vCenter Server Appliance (vCSA)


Disclaimer:  Comments given in this forum should not be interpreted as a commitment that SolarWinds will deliver any specific feature in any particular time frame. All discussions of future plans or product roadmaps are base on the product teams intentions, but those plans can change at any time.


If you don't see what you are looking for here, you can always add your idea(s) and vote on features in our Virtualization Manager Feature Requests forum.

VMAN is now generally available in the Customer Portal for all customers on Active Maintenance. Several important issues were addressed in this Service Release including:


  • Significant security updates to the CentOS version shipped in the virtual appliance and it's 3rd party software
  • Fixed an issue where the Virtualization Manager tabs do not show up in Orion
  • Fixed a discrepancy between the CPU value utilization shown on the vCenter and in IVIM
  • Fixed a performance issue in the Orion Web Console
  • Fixed an issue where Virtualization Manager starts up slowly after upgrading to version 6.1
  • Improved the auto upgrade procedure
  • Fixed an issue with displaying status tool data
  • Improved the efficiency of midnight hourly roll-up operations
  • Improved the usability of the Synchronization Wizard
  • Fixed an issue with account limitations strings incorrectly displayed
  • Fixed an issue with charts not displaying all data for the selected time period
  • Fixed an issue with inconsistent polling source settings
  • Fixed an issue with creating List resources
  • Many other bug fixes and stability improvements!



The update to the Orion Integration Module can also be found under the server downloads in your customer portal.

Customer Portal - IVIM.jpg

Integration with SolarWinds SAM or NPM provides visibility into the application stack from VM to virtual storage performance.

  • VMware® & Hyper-V® performance metrics
  • Capacity, utilization & performance of datastores & Hyper-V storage
  • Storage sub-views show a slice of the VM environment (vCenter, data center, cluster, ESX® hosts & VMs)
  • Metrics to monitor VM sprawl & reclaim CPU, memory & storage resources
  • Virtualization Manager reports & dashboards from Orion console


6.1.1  is available now in your Customer Portal.

Release notes may be found here

Filter Blog

By date: By tag:

SolarWinds uses cookies on its websites to make your online experience easier and better. By using our website, you consent to our use of cookies. For more information on cookies, see our cookie policy.