Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Virtualization Manager (VMAN) > Virtualization Manager (VMAN) Getting Started Guide > Deploy Virtualization Manager > Plan for a VMAN deployment

Plan for a VMAN deployment

Updated November 18th, 2016


Before you install SolarWinds Virtualization Manager (VMAN), prepare your environment. When installing VMAN, review the requirements for the appliance and integration.

This Getting Started guide provides instructions for integrating with an existing Orion platform.

After deploying the VMAN appliance, you must integrate with the Orion Web Console to fully access all VMAN features, including recommendations.

Install and integrate as a stand-alone VMAN and Orion Platform

VMAN comes with the Orion Platform for a fully stand-alone application. When you unzip the installation file, you receive:

  • VMAN-Appliance-Install-1st.ova - deploys the VMAN appliance. Run this file first when deploying the VMAN appliance to Hyper-V or vSphere servers. A Hyper-V zip file is also available for those servers.
  • VMAN-Orion-Install-2nd.exe - installs the Orion Platform and Virtual Infrastructure Monitor (VIM) for virtualization monitoring.

This stand-alone installation provides all of the VMAN, VIM, and Orion Platform features through one Orion Web Console.

Integrate with an existing Orion Platform

If you have an existing Solarwinds Orion Platform, you can integrate the VMAN appliance with that environment. The orion Platform comes with VMAN and is automatically installed with SolarWinds products such as Network Performance Monitor (NPM), Server & Application Monitor (SAM), or Network Configuration Manager (NCM). This type of installation gives you access to all VMAN features and integrates VMAN with other Orion products.

Virtualization Manager appliance system requirements

Install VMAN on a VM that meets the following requirements. You cannot install VMAN on the same server as the Orion Platform.

software or hardware requirements

Virtualization software

VMware vSphere 5.x or later

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.


2 GHz quad-core

Virtual CPUs

4 vCPUs


8 GB or more

The table below provides the scaling memory recommendations based on the number of monitored ESX hosts and VMs.

number of esx hosts

number of vms




8 GB



10 GB



12 GB



14 GB



16 GB

> 200

> 2000

Contact Support

Disk space

200 GB or more 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.

Virtual NIC

1 Gigabit

Orion Platform integration system requirements

Before you integrate VMAN, make sure the Orion Platform server meets the following requirements.

software or hardware requirement

Operating System

Windows Server 2008 R2 SP1

Windows Server 2012, 2012 R2

Windows Server 2016

For evaluation only:

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 3.0 GHz

8 GB

VMAN Recommendations also require an additional 8GB.

.NET Framework .NET 4.0 and 4.5

SQL Server

SQL Server 2008 without SP

SQL Server 2008 SP1, SP2, SP3, SP4

SQL Server 2008 R2 without SP

SQL Server 2008 R2 SP1, SP2, SP3

SQL Server 2012

SQL Server 2012 SP1, SP2, SP3

SQL Server 2014

SQL Server 2014 SP1

SQL Server 2016


Internet Explorer version 11 and Edge

Mozilla Firefox two latest versions

Google Chrome two latest versions

Port requirements

The following ports are required for the VMAN appliance. If you use a federated collector as a proxy, see the SolarWinds Virtualization Manager Administrator Guide for port requirements.

Required inbound ports on the master appliance

inbound port usage
443 or 80 Performs auto-upgrade or version upgrade on federated collectors if federated collectors are configured
8983 Access from federated collectors to the master appliance during initial setup
443 HTTPS access to the Virtualization Manager user interface
5480 HTTPS access to the Management Console
61616 Active MQ master-collector communication
22 SSH access to the virtual appliance

Required outbound ports on the master appliance

outbound port usage
162 Sends SNMP traps
25 Sends emails through SMTP
389 Active Directory authentication
3268 LDAP authentication

Communicates with the SolarWinds Orion server if the integration with Orion is enabled

If you use Virtualization Manager integrated with NPM or SAM in an environment with multiple polling engines and federated collectors, open TCP port 17778 from the primary collector to every polling engine that is used to poll virtualization data.

123 Uses the NTP service

Virtual machine and server requirements

The VMAN appliance can be installed on VM servers. The virtual machine requirements are identical to the physical server requirements.

Deployment checklist

Verify the following pre-installation steps to prepare for your VMAN deployment.


Verify account permissions.

Set matching account credentials for the Orion Platform, the VMAN appliance, and vCenter, VMware, and Hyper-V systems. Credentials must match to support full communication across the virtual environment for polling and reporting data, applying recommendations, and monitoring status.


Check for antivirus software.

To ensure the best performance for VMAN and the Orion Platform, you may need to exclude specific file paths and directories from anti-virus software scans. See the article Files and directories to exclude from antivirus scanning for an explanation of directories and files to exclude.


Confirm that your deployment environment meets the recommended system requirements.

Use the Local Administrator Account for installation. The Local Administrator Account is not the same as a domain account with local admin rights. A domain account is subject to your domain group policies.


Ensure you have the correct version of the deployment.

The deployment files are available in the Customer Portal, including versions for the appliance, the evaluation, and versions for additional polling engines and additional web servers.


Obtain access and credentials to the Orion SQL Server for your Orion Platform environment.

Contact your SQL Database Administrator for this information.

Learn more...

To install and integrate VMan:

For additional information on installations, federated collectors, and advanced configurations, see the SolarWinds Virtualization Manager Administrator Guide.

Last modified
15:47, 2 Mar 2017