Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Issue with Orion installer version mismatch with VMan appliance when upgrading Orion VMan from 8.1 to 8.2

So when upgrading SAM, SRM and Orion VMan to the latest available versions, the installer prompts a warning that our appliance is at 8.1

Doesn't look like there is an 8.2 Upgrade ISO for VMan appliances, so a false alarm there?

Find more posts tagged with

Accepted answers

All comments

prawij

Time to open a ticket: the aftermath in the Orion GUI...

serena

With VMAN 8.0 and later, using the appliance at all is unnecessary. Switch your polling over to be Orion based, and those errors will resolve themselves in the UI.

p.darila

Hello,

warning says something like: if there is no new version of vman appliance, you can ignore the message - you are right, there is no new version of VMAN appliance 8.2, so you can ignore the warning. Everything should be working with VMAN appliance 8.1 as before.
Are you sure your adobe flash player is updated? Could you try this on another browser?

prawij

Hi, yes the Flash warnings were related to Chrome, the resources are working ok in IE, so no real issue there.

prawij

Hi Serena, we tried switching over to Orion VMan polling, then discovered that the charge back feature was missing, and had to go back to the appliance.

Edited to add: Re: Old VMAN features missing in Orion

serena

I'm super curious how you're utilizing the chargeback feature for your organization. Do you mind if I schedule a call with you?

prawij

Hi Serena,

I can't really get into the details, but what we do is have each app area in a folder, and then we keep track of that cost in the Cloud Cost (EC2) view. So it's more of a virtual chargeback to keep track of how much each app is costing to support - there are no actual chargebacks in our scenario.