Table of installed module versions with Hotfixes for all APEs and AWEs

We would like to see a table of all installed module versions and hot-fixes for all additional polling engines and additional web engines so we can easily identify and versions that are out-of-date or missing hot-fixes.

A single easy to read table would be very helpful.

Find more posts tagged with

installer

sam

udt

vim

npm

ncm

awe

ape

Status: None

Comments

shuth

It's not pretty but check out the OrionServers table in the database (not sure what version this was added but it's definitely in Orion 2017.1.3). There is a Details column that will list the modules installed for each engine.

To view this information on the web console, add a Custom Query resource and use the following SWQL query (remove/rearrange columns as desired):

SELECT ServerType, Hostname, SWAKeepAlive, SWAVersion, Details FROM Orion.OrionServers

Edit: I've seen it be a bit flaky with hotfixes (i.e. I installed an NCM hotfix but it still says "HotfixVersionNumber":null ). You can look at the installed updates manually on each server (Programs and Features -> View installed updates) but obviously this means logging on to each server. If you're running SAM, you might be able to use Agent Inventory and create a report...

The below screenshot is of a system that has a number of hotfixes installed but the table only says the Orion Platform has a hotfix (NPM 12.1 HF1, NCM 7.6 HF1, Netpath 1.1 HF1 are also installed).

serena

The new orion installer shows you the upgrade path and what's installed on the main primary poller. Some of the improvements we're working on for the new scalability engines installer will allow you to see this as well. In addition, in NPM 12.0.1 http://oriondemo.solarwinds.com/ui/ha/summary would show you if there are discrepancies of what's installed on your scalability engines.

foonly

It's good to see that info at install time.

Now, if we could get this info onto the Orion Platform Details Page, that would help all customers later discuss what versions and hotfixes they have when discussing symptoms in Thwack. We shouldn't have to do a query or decode a string of numbers to translate into the friendly form that everyone uses - Vx.y HFz.

Thanks,

=seymour=