Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Virtualization Manager (VMAN) > Vitualizaton Manager (VMAN) Installation Guide > VMAN system requirements

VMAN system requirements

Updated: 6-1-2017 | VMAN Installation Guide

The following requirements are for installing the VMAN appliance on a VM and Orion Platform. Additional requirements include port requirements and account permissions.

If you are adding VMAN to an existing Orion Platform with multiple Orion Platform products, see the Multi-module system guidelines.

When deploying VMAN, you fully install:

  • VMAN appliance on a VM
  • VMAN on a stand-alone server or existing Orion Server

Deployment sizes and requirements

When determining the deployment size and requirements for your VMAN deployment, consider the following:

  • In medium and large deployments, SolarWinds recommends that you deploy federated collectors or Additional Polling Engines (APE) for each 2000-3000 virtual machines, and split the collection load in a way that each collector or APE collects similar amounts of data.
  • In medium and large deployments, delegate all collection jobs to federated collectors and APEs from the Virtualization Manager master appliance and the Orion Server.
  • If you collect data from large vCenters containing more than 4000-5000 VMs, increase the memory assigned to the federated collector that collects from the vCenter.
  • Any one of the deployment factors could cause the recommended size to grow from small to medium to large. For example, the number of VMs per vCenter significantly affects the amount of resources you need.

As environments grow, you can scale your Virtualization Manager deployment without extensive migration. You can expand disk space, assign additional shared or dedicated CPU and RAM resources, and the virtual appliance dynamically takes advantage of these new resources.

To install federated collectors, see <xref href="VMAN-Install-Federated Collectors.htm">Install federated collectors in VMAN</xref>.

VMAN appliance requirements

The appliance cannot be installed on a Windows server, or on the same server with the Orion Platform.

Software/Hardware Requirements

Virtualization software

VMware vSphere 5.x or later

VMware vCenter 6.5

VMware vCenter Server Appliance (vCSA) 6.5

VMware ESX or ESXi 5.x or later, managed or unmanaged hosts

Microsoft Hyper-V Server 2008 R2

Microsoft Hyper-V Server 2012

Microsoft Hyper-V Server 2012 R2*

Microsoft Hyper-V Server 2016

Virtualization Manager only supports the default, English localization of Hyper-V.

*Not supported with this software:

  • vm.processorSocketCount
  • vm.processorCoresPerSocket
  • vm.processorCount
  • host.vSwitch.maxChimneyOffloads
  • host.vSwitch.numLearnableAddresses
  • host.vSwitch.port.accessVlan
  • host.vSwitch.port.defaultVLAN
  • host.vSwitch.port.nativeVLAN

Class replacements for configuration and performance collections against 2012 R2 servers include:

  • Msvm_SwitchLANEndpoint class replaced by Msvm_LANEndpoint
  • Msvm_VirtualSwitch class replaced by Msvm_VirtualEthernetSwitch
  • Msvm_VmLANEndpoint class replaced by Msvm_LANEndpoint
  • Msvm_SwitchPort class replaced by Msvm_EthernetSwitchPort
  • Msvm_VLANEndpointSettingData class replaced by Msvm_EthernetSwitchPortVlanSettingData
  • Msvm_ResourceAllocationSettingData class replaced by Msvm_StorageAllocationSettingData


Quad Core, 2 GHz

Virtual CPUs

4 vCPUs


8 GB or more

number of esx hosts

number of vms




8 GB



10 GB



12 GB



14 GB



16 GB

> 200

> 2000

Contact Support

To review the requirements for integration with the Orion Platform and Virtual Infrastructure Monitor, see Orion Platform recommended requirements for VMAN. Recommendations requirements are available in that section.

To learn more about memory requirements, see Reduce the memory requirements of Virtualization Manager.

Disk space

200 GB or more.

At least 200 GB of disk space is recommended. At the default collection interval, a virtualized environment containing 1000 VMs and 100 hosts requires 40 GB of storage during the first month, and an additional 60 GB of storage over the next five years.

To estimate the disk space requirements over time, download the SolarWinds Virtualization Manager Storage Calculator.

To learn more about disk space requirements, see Expand the provisioned disk size on VMware<.

Virtual NIC

1 Gigabit vNIC

Supported browsers

Internet Explorer 8 or later

Mozilla Firefox two latest versions

Google Chrome two latest versions

Adobe Flash Adobe Flash Player 9 or later

Reduce the memory requirements of Virtualization Manager

The minimum memory requirement is 8 GB, but more memory might be necessary to handle peak demands. You can reduce the memory requirement for collecting from multiple vCenters (VC) in these ways:

  • Schedule the configuration data collection jobs for the different VCs in a way that they do not overlap, by setting the start times at least three hours apart. This also means reducing the frequency of configuration collection to one or two times per day.
  • Instead of using the actual total number of ESX hosts in the environment, calculate an approximate number of hosts according to the formula:
    1. Take the largest number of hosts managed by a single VC instance.
    2. Add 15% for each additional VC in your environment, regardless of its size.

For example, if you have three VCs and the largest VC manages 90 hosts, your "proxy number of hosts" is 117.

117 = 90 + 0.15 x 90 + 0.15 x 90

The number of ESX hosts above is guidance only, and is based on a typical virtualization environment with approximately 10 VMs and one datastore per ESX host server. More dense environments require larger memory sizes.

Expand the provisioned disk size on VMware

The VMware appliance might allow thin provisioning to let you install with less than 200 GB of free disk space. SolarWinds Virtualization Manager stops collecting data when less than 1 GB of storage space remains. At that point, increase the available storage space, and change the provisioned size or the virtual hard disk.

  1. Increase the provisioned size of Hard disk 2 of the appliance.
    1. Run the vSphere client, and connect to the vCenter that hosts the appliance.
    2. Select the SolarWinds Virtualization Manager appliance, and edit the settings.
    3. Increase the Provisioned Size of Hard disk 2.
  2. Restart the appliance virtual machine.

To expand the disk on Microsoft Hyper-V, contact Support.

Orion Platform recommended requirements for VMAN

The following requirements are for the stand-alone Orion Platform with Virtual Infrastructure Monitor (VIM) installation.

If integrating VMAN into an existing Orion environment with multiple modules, see the <xref href="Core-Multi-Module-System-Guidelines.htm">Multi-module system guidelines</xref>.

software/hardware requirement

Operating System


Evaluation Only

Windows Server 2008 R2 SP1

Windows Server 2012, 2012 R2

Windows Server 2016

Windows 7 SP1

Windows 8 (except Standard edition)

Windows 8.1 (except Standard edition)

Windows 8.1 Update 1 (except Standard edition)

Windows 10

CPU Quad Core, 3.0 GHz

8 GB

Recommendations feature also requires an additional 8 GB


10 GB minimum

SolarWinds recommends higher disk allowance for database growth.

.NET Framework .NET 4.0 and 4.5

SQL Server

SQL Server 2008, 2008 SP1, 2008 SP2, 2008 SP3, or 2008 SP4

SQL Server 2008 R2, 2008 R2 SP1, 2008 R2 SP2, or 2008 R2 SP3

SQL Server 2012

SQL Server 2012 SP1, SP2, SP3

SQL Server 2014

SQL Server 2014 SP1

SQL Server 2016


Microsoft Internet Explorer version 11 or later with Active scripting

Microsoft Edge

Firefox 45.0 or later (Toolset Integration is not supported on Firefox)

Chrome 49.0 or later

Use the table to determine how to modify your VMware and Hyper-V environments for integration with your Orion platform product.

orion polling method

vmware (host)

hyper-v (host)

vmware (guest)

hyper-v (guest)

No Status













Not applicable for ESX hosts and the vCenter appliance.





Deprecated on ESX hosts and the vCenter appliance.


Depending on your polling method and Virtualization Manager environment, you might get different results.

Deprecated software versions

Be aware of the following hardware, software, and features deprecation notices. The Microsoft SQL Server and Windows Server versions are still supported with VIM 7.1. Future versions will no longer support the listed versions.

Microsoft SQL Server

Support for SQL 2008 and 2008 R2 is deprecated as of this release.

Future releases will no longer support using SQL 2008 or 2008 R2 as your database server.

SolarWinds recommends that you upgrade directly to SQL 2016 at your earliest convenience.

Microsoft Windows Server

Support for Windows Server 2008 R2 is deprecated as of this release.

Future releases will no longer support installing on Windows Server 2008 R2, though you can continue to monitor computers running Windows Server 2008 R2.

SolarWinds recommends that you upgrade to Windows Server 2012, 2012 R2, or 2016 at your earliest convenience.

Last modified
14:15, 31 May 2017


This page has no custom tags.