Specifications and Requirements

This section provides information on software, hardware and port requirements, account requirements and supported third-party integrations.

Software requirements

Virtualization and Cloud Platforms Supported

VMware vSphere 6.5, 6.0, 5.5, 5.1, 5.0

Microsoft® System Center Virtual Machine Manager (SCVMM) 2012 R2 Update Rollup 12

Amazon Web Services

Microsoft Azure Resource Manager (ARM)

Microsoft Azure Service Manager (ASM)

Operating Systems Supported for vCommander Installation

Microsoft Windows Server 2016

Microsoft Windows Server 2012 R2

Microsoft Windows Server 2012

Microsoft Windows Server 2008 R2 or higher

NotePencil-smallvCommander does not support Azure subscriptions that contain both Azure Classic and ARM resources. To learn how to migrate resources to ARM, see Migrate Classic Resources to Azure Resource Manager in the Microsoft documentation.

Languages Supported

English

Recommended Databases

Microsoft SQL Server 2016

Microsoft SQL Server 2014

Microsoft SQL Server 2012

Microsoft SQL Server 2008 R2

NotePencil-smallThe default Cardinality Estimator used for Microsoft SQL Server 2014 and 2016 increases query compile time, which can reduce the vCommander Dashboard display speed. To increase the display speed of the Dashboard, you should change the SQL Server's compatibility level to SQL Server 2012 (110), then restart vCommander service. To learn how to change the SQL Server compatibility level, see View or Change the Compatibility Level of a Database in the Microsoft documentation.

Default Database

PostgreSQL is included with vCommander for evaluation environments

Browser Recommended

Mozilla Firefox 57

Browsers Supported

Mozilla Firefox 57, 56

Microsoft Internet Explorer 11, 10

Google Chrome 62, 61

Microsoft Edge (experimental)

NotePencil-smallTo use Internet Explorer 10, you must edit the security configuration in new installations of vCommander. To learn how to enable the use of Internet Explorer 10 with vCommander, see the Knowledge Base article Modifying vCommander's SSL Ciphers.

Network

Gigabit Ethernet Minimum

Licensing

For more information about licensing, please refer to the terms in your license agreement or contact your Embotics® representative.

NotePencil-smallWhen vCommander is installed, an application called Erlang OTP is also installed, and it will appear in the list of installed programs on the vCommander host. Erlang OTP should not be uninstalled.

Hardware requirements

The following table provides Embotics® vCommander® deployment tiers based on typical use. See Scaling Embotics® vCommander® Hardware Requirements for more details. You can also contact Embotics® Support to discuss requirements further, if you have any questions or unique configurations.

Profile

Description

Base Requirements

Evaluation

A single-vCPU deployment used to evaluate vCommander's feature set. It will not grow significantly beyond original occupancy, and it is not expected to be upgraded to production.

2 vCPU / 2.0 GHz dual core

8.0 GB Memory

2.0 GB disk space

Default Postgres database

Small

A single-vCPU production deployment for static environments of fewer than 500 VMs, supporting fewer than 10 concurrent users, with infrequent reporting.

2 vCPU / 2.0 GHz quad core

8.0 GB Memory

1.0 GB disk space (installation)

4.0 GB disk space (data partition)

Dedicated application server

Microsoft SQL Database

Medium

A dual-vCPU production deployment for dynamic environments with fewer than 1500 VMs, supporting fewer than 30 concurrent users, with frequent reporting.

2 vCPU / 2.0 GHz quad core

8.0 GB Memory

1.0 GB disk space (installation)

10.0 GB disk space (data partition)

Dedicated application server

Separate Microsoft SQL Database

DB data file (mdf) and log file (ldf) stored on separate disks

Enterprise

A dual-vCPU production deployment for dynamic environments with more than 1500 VMs, supporting more than 30 concurrent users, with frequent reporting.

2 vCPU / 2.0 GHz quad core

8.0 GB Memory

1.0 GB disk space (installation)

10.0 GB disk space (data partition)

JVM memory increased to 6 GB

Dedicated application server

Separate Microsoft SQL Database

SAN backing for database files

vCommander VM Access Proxy Hardware Requirements

Minimum requirements:

2 CPUs

Note that the higher the number of CPUs available, the more concurrent connections the VM Access Proxy can handle.

2 GB Memory

7 GB disk space

The template archive size is approximately 2.5 GB.

Network requirements

The following ports are used by the various vCommander components. You configure some of these ports during installation, and you can also configure ports after installation using the vCommander Control Panel. Certain ports can be configured only through a system property; for more information, contact support@embotics.com.

IMPORTANT: To protect the security of the vCommander system, all ports must be firewalled, with the exception of ports that are required to be inbound.

NotePencil-small Where the direction is outbound, this implies a corresponding inbound connection to the target.

Table: Network Requirements - Basic Operations

Connection

Ports

Protocol

Direction

Description

vCommander Webserver

443

TCP

Inbound

Access to vCommander admin console, Service Portal and REST API.

vCommander Microsoft SQL Server

1433

TCP

Outbound

Access to the vCommander database. Additional ports may be required depending on the configuration of your SQL server.

vCenter

443

TCP

Outbound

Communications with individual vCenters or their external Platform Services Controllers.

vCenter Hosts

443

TCP

Outbound

Access to the vCenter hosts for VM Guest OS file copy operations.

Amazon Web Services

443

TCP

Outbound

Communications with Amazon Web Services API.

Microsoft Azure

443

TCP

Outbound

Communications with Microsoft Azure API.

Windows Guest OS Features

135

139

445

TCP

Outbound

Access to Windows VMs for issuing WMI commands and file copy operations.

Linux Guest OS Features

22

TCP

Outbound

Access to Linux VMs for issuing SSH commands.

Datastore Scanning

443

TCP

Outbound

Access to VMware hosts through HTTPS to collect file layout.

Legacy Datastore Scanning

22

TCP

Outbound

Access to VMware hosts through SSH to collect file layout. Only used when HTTPS access is not available.

Table: Network Requirements - Authentication

Connection

Ports

Protocol

Direction

Description

Kerberos Key Distribution Center

88

TCP

Outbound

Access to authenticate against an Active Directory or LDAP server.

Active Directory Domain Controller for Remote LDAP Traffic

389

TCP

UDP

Outbound

Access to authenticate against an Active Directory or LDAP server.

Active Directory Domain Controller for Remote Global Catalog Traffic

3268

TCP

Outbound

Access to query the global catalog of an Active Directory or LDAP server.

Active Directory Domain Controller for Remote Secure LDAP Traffic

686

TCP

Outbound

Access to authenticate against a secure Active Directory or a secure LDAP server.

Active Directory Domain Controller for Remote Secure Global Catalog Traffic

3269

TCP

Outbound

Access to query the global catalog of a secure Active Directory or secure LDAP server.

Table: Network Requirements - Optional

Connection

Ports

Protocol

Direction

Description

Splunk Server

8089

TCP

Outbound

Communications with Splunk server for retrieval of guest OS performance metrics.

BlueCat™ Server

80

TCP

Outbound

Communications with BlueCat™ IP address management server for addressing assignments.

Table: Network Requirements - Client Connections

All of these connections go from the client browser to the respective servers.

Connection

Ports

Protocol

Direction

Description

VM Access (Remote Desktop)

3389

TCP

Inbound

Access to remote control VMs using RDP.

VM Access (Virtual Network Computing)

5900

TCP

Inbound

Access to remote control VMs using VNC.

VMware Console - WebMKS (HTML5)

9443 (vCenter 6.0)

7343 (vCenter 5.5)

TCP

Inbound

Access to remote control VMs using WebMKS Console.

VMware Console - Plug-in

443 (vCenter)

902 (ESX)

TCP

Inbound

Access to remote control VMs using VMware Remote Console (VMRC) Plug-in.

Table: Network Requirements – Advanced Configuration

Connection

Ports

Protocol

Direction

Description

VM Access Proxy Appliances – Web Server

443

TCP

Inbound

Publishing listener for WebMKS open console sessions.

VM Access Proxy Appliances – Web Server

8443

TCP

Inbound

Publishing listener for RDP, VNC, SSH and plug-in-based open console sessions.

VM Access (Hyper-V Console)

2179

TCP

Outbound

Access to remote control VMs using the Hyper-V console.

Guest OS Scanning Port Requirements

Guest OS scanning of Windows VMs requires firewall rules to handle a dynamic range of ports that are opened for the response when vCommander queries the VMs on TCP port 135. To avoid opening a large range of high ports, refer to the following Knowledge Base articles for instructions on how to configure the Windows Firewall to enable these ports:

Configuring Windows for Guest OS Scans Using Group Policy

Configuring Windows for Guest OS Scans

Account on each managed system

vCommander requires an administrative account on each managed system. The account must have full administrative access on the entire managed system. Administrator privileges are required for a number of functions that vCommander performs. These functions include retrieving VM and infrastructure information, managing VM identity, powering VMs on and off, and other policy actions.

Embotics® recommends that you create a uniquely identifiable administrative account on each managed system (for example, Embot). Creating a unique account name allows you easily to track vCommander commands sent to the managed system by vCommander or by vCommander users.

NotePencil-smallvCommander does not make use of VMware's Linked Mode feature. vCommander communicates with each vCenter directly.

Third-party integrations

The following table provides a list of third-party software that can be integrated with vCommander, including supported versions where applicable.

Table: Third-Party Integrations

Integration Category

Supported Systems and Protocols

Integration Type

Authentication

Active Directory®

Bundled

LDAP

Bundled

SAML2 WebSSO

Bundled

Windows SSO

Bundled

Configuration Management and Application Deployment/Automation

Chef™ 12.15.7

Bundled

Puppet™ Enterprise 2017.1.1

Bundled

SCCM 2012 R2

Scripted

Jenkins CI with PowerShell plug-in

Scripted

ServiceNow or ServiceNow Express, with REST API access

Scripted

Zerto Virtual Manager (ZVM) Replication 4.5u1 (vCenter only)

Scripted

Docker 1.11.2

Scripted

vCommander REST API plus Windows Task Scheduler (and similar)

Scripted

vCenter metadata synchronization, for all vCenter versions supported by vCommander

Scripted

IPAM

BlueCat™ IPAM 4.1

Bundled

Application Monitoring

Splunk® 6.2, 6.1 (with HTTPS protocol)

Bundled

Notification

SNMP 2

Bundled

SMTP

Bundled

Backup

Veeam Backup & Replication 8.0

Additional download required

Workflow Automation

vCommander REST API client for PowerShell 4, 3 with .NET Framework 4.5 or higher

Additional download required