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 > Orion Platform > Orion - Knowledgebase Articles > Upgrade Failure - Installer Detecting Older version of Virtualization Manager

Upgrade Failure - Installer Detecting Older version of Virtualization Manager

Updated: December 13, 2017


***Make sure customer has upgraded Virtualization Manager and NCM to a compatible version with the version of NPM you are trying to install. The resolution will depend on if the VMAN server is upgraded accordingly. *****


This article explains an issue where the Orion installer detects a incorrect version of Virtualization Manager than what is actually installed on the Virtualization Manager server.



  • All



This issue is caused by a bug in the Orion integration holding on the initial version the integration that it was currently working with.



  1. Navigate to the web console > Settings --> Virtualization Settings.
  3. Navigate to the Orion server.
  4. Open up Add/Remove Programs from the Control panel.
  5. Uninstall the 'SolarWinds Virtual Infrastructure Monitor' module.
  6. When the Configuration Wizard app pops up please run until finished (Please run if it does not pop up automatically).
  7. This should resolve the install issue. Please re-run the installer and finish accordingly.





Last modified