Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Failed to start the VMAN virtual appliance after importing the .ovf file on the ESXi host

Failed to start the VMAN virtual appliance after importing the .ovf file on the ESXi host

Updated March 11th, 2016 

Overview

The VMAN appliance cannot power ON after importing the .ovf file on the ESXi host.

Environment

VMAN 6.3

Cause 

This issue occurs when a standalone virtual machine has the vApp options enabled but is not a member of a vApp.

Last modified

Tags

Classifications

Public