Product Blog

8 Posts authored by: peter.ksenzsigh

SolarWinds Server Health Monitor Quick Reference Guide

The SolarWinds® Server Health Monitor (SHM) is a free diagnostic tool that provides basic-level health status server monitoring for up to five servers in a corporate enterprise. You can download it from SolarWinds pages here.

Using Simple Network Management Protocol (SNMP), Windows Management Instrumentation (WMI), and Common Information Model (CIM) calls to your network frameworks and application servers, the tool polls the basic system components in each configured server (such as the power supply, temperature, and fan) and displays a server health overview of all monitored servers in the Dashboard tab. The tool is supported on selected VMware® hypervisors and Dell™, HP®, and IBM® servers.

If you need expert-level health status server monitoring for over 200 applications and 1000 servers in a corporate enterprise, see the SolarWinds Server and Application Monitor.



Installation requirements




Operating system

Microsoft® Windows® 7

Windows 8

Windows 10

Windows Server® 2008 R2  Windows Server 2012 R2

System details

Processor: 2 GHz


Disk Space: 100 MB

.Net: 4.0


Systems supported for monitoring





Dell PowerEdge™ HP ProLiant™

IBM eServer™ xSeries

Blade enclosures

Dell PowerEdge M1000e Blade Enclosure HP BladeSystem c3000 Enclosure

HP BladeSystem c7000 Enclosure


VMware vSphere® ESX Hypervisor  VMware vSphere ESXi™ Hypervisor


Hardware monitoring agent software

Each computer hardware vendor installs hardware monitoring agent software on their systems, which includes a Web server that operates on a unique port.

Remote servers include the hardware monitoring agent software for both SNMP and WMI.

Note: The blade enclosures do not use hardware monitoring agent software.

To ensure that the hardware monitoring agent software is installed on your system, open a Web browser and navigate to the following URL:


where remote_ip_address is the remote server IP address and Port is one of the following ports:


HP: 2381

Dell: 1311

IBM: 423


Install the tool


  1. Download and install the SolarWinds Server Monitor from the SolarWinds Free Tools website.
  2. Double-click the installer icon. The SolarWinds Server Health Monitor Setup Wizard appears.
  3. Click Next.
  4. Follow the prompts on your screen to complete the installation.


Add your monitored servers


  1. Click the Configure tab. The Configure Tab screen appears.
  2. Click  . The Server and Credentials box appears.
  3. In the top field, enter the IP address or host name of the server you want to monitor.
  4. Click the drop-down menu and select the method used to poll the server and gather health monitor details.
  • You can poll the following servers using SNMPv2 or SNMPv3.
    • Dell PowerEdge servers
    • HP ProLiant servers
    • Note: Array and Battery information requires WMI polling.


  • You can poll the following servers using WMI:
    • Dell PowerEdge M1000e Blade Enclosure
    • HP BladeSystem c3000 and c7000 Enclosures
    • HP ProLiant servers
    • IBM eServer xSeries


  • You can poll the following hypervisors with no required polling setup:
    • VMware vSphere ESX
    • VMware vSphere ESXi
    • These hypervisors use the CIM protocol that should be enabled by default after you install the ESX or ESXi hosts.

Configure polling using SNMPv2


  1. Ensure that SNMP is enabled on the monitored server. See your server or VMware documentation for information about configuring SNMP.
  2. Click the drop-down menu and select SNMPv2.
  3. In the Community String field, enter your SNMP credentials.
  4. Click . The monitored server connection is configured, and the tool automatically polls the server for server health data. The polling process may require several minutes to gather the server data.

Configure polling using SNMPv3


  1. Ensure that SNMP is enabled on the monitored server. See your server or VMware documentation for information about configuring SNMP.
  2. Click the drop-down menu and select SNMPv3. The Server and Credentials box appears.
  3. In the Username field, enter the IP address or user name of the server you want to monitor.
  4. In the Context field, enter your SNMP credentials.
  5. In the first drop-down menu, select an encryption algorithm for the polling connection. MD5 (Message Digest) provides a 128-bit hash algorithm. SHA1 (Secure Hash Algorithm) provides a 160-bit hash algorithm.
  6. Click the second drop-down menu and select an encryption cipher for the polling connection.
  7. In the Password field, enter an authentication password.
  8. Select the Password is a key check box to select the algorithm of the encryption. Note: If you select this check box, leave the Context field blank.
  9. Click . The monitored server connection is configured, and the tool automatically polls the server for server health data. The polling process requires one to two minutes.

Configure polling using WMI


  1. Ensure that WMI is enabled on the monitored server. See your server or VMware documentation for information about configuring WMI.
  2. Click the drop-down menu and select WMI. The Servers and Credentials box appears.
  3. In the Username and Password fields, enter your WMI user name and password.
  4. Click . The monitored server connection is configured.



View your server health

When you click the Dashboard tab, the tool polls the monitored servers and displays a health status overview of all servers. The overview includes a pie chart, node count, and summary information of all monitored servers.

The polling process requires up to two minutes to complete, depending on your network configuration. During the polling process, Processing appears at the bottom of the window.

The Node Count lists the number of monitored nodes and the corresponding status. The Summary lists all monitored servers and their corresponding status.

The following table provides descriptions of each status.







All monitored components are functioning properly.


One or more components are in working condition, but a failure may exist.


One or more components failed, requiring imme- diate attention.


One or more components have a status that the tool cannot recognize.


View server details

When you click an IP address (or host name) in the Dashboard tab, the Server Details window appears. This window displays the IP address (or host name), current health status, and additional information about the selected server.


The Current Server Health section lists the sensors polled by the tool. Maximize a sensor name to view the status and corresponding value. The server and current health details listed in the window may vary for each server.

To return to the Dashboard tab, click Back to Summary.

Update the polling interval

The Update Polling Interval setting in the Configure tab allows you to select the time interval (between 5-60 minutes) when the tool polls the monitored servers for health status information.




View additional resources

The Resources tab provides links to resources for managing your corporate enterprise.


Troubleshoot error messages

The following table lists error messages that may appear after you configure your devices in the Configure tab.




Error Message

Description and Resolution

Unable to resolve the host name. Please use the IP address

The host name is spelled incorrectly or DNS could not resolve the host name to an IP address.

To resolve this issue, ensure that:


  • The host name in the Configure tab is correct.
  • The DNS server is configured properly with corresponding host name and IP addresses.
  • The IP address is entered in the correct format.

An unknown error occurred.

The tool experienced an issue with monitoring the targeted server.

To resolve this issue:


  1. Open the %ALLUSERPROFILE% directory.
  2. Navigate to the following directory: SolarWinds\ServerHealthMonitor
  3. In the directory, locate the followin file. ServerHealthMonitor.log
  4. Open the file in a text editor (such as Notepad) and search for an error (for example, a disabled WMI service).

Not a supported server type. For a list of sup- ported server types, see Help for details.

The targeted device is not supported by this tool.

See Hardware requirements for a list of supported servers, blade enclosures, and hypervisors.

Different polling method required.

The tool could not poll the device based on the selected polling method specified in the Configure tab.

To resolve this issue, select a different polling method that is appropriate for the targeted device.

The user credentials are wrong.

The user does not have remote access to the computer through a DCOM

The tool does not have Distributed Component Object Model (DCOM) permissions to access the targeted Windows server. WMI uses the DCOM protocol to communicate directly over a network with Windows-enabled servers.

To resolve this issue, ensure that:


  • The server credentials are entered correctly in the Configure tab.
  • DCOM is enabled on the targeted server.

See the Microsoft TechNet website for information about enabling and disabling DCOM on servers running Windows Server 2008 R2 and Windows 2012 R2 operating systems.

The computer really doesn't exist.

The Windows Firewall is blocking the connection.

To resolve this issue, ensure that:


  • The targeted server is running and connected to the network.
  • The Windows Firewall is deactivated on the targeted server.

Polling of chassis (CIM_Chassis class) failed. Unable to estab- lish session with all provided credentials.

The VMware credentials are incorrect.

To resolve this issue, ensure that the VMware server credentials in the Configure tab are correct.

Polling of chassis (CIM_Chassis class) failed. Unable to con- nect to the remote server.

The selected polling method is not supported on the targeted server.

To resolve this issue, ensure that the selected polling method in the Configure tab is correct. If the

issue still exists, change the polling type method and poll the server.

Unable to find the server type. Could be due to incorrect cre- dentials or the server type is not supported.

The credentials in the Configuration tab are incorrect or the server type is not supported.

To resolve this issue, ensure that:

  • The server credentials in the Configure tab are
  • The server is listed in the hardware requirements as a supported server.






Copyright © 2015 SolarWinds Worldwide, LLC. All rights reserved worldwide.

No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of SolarWinds. All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.



other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies. Microsoft®, Windows®, and SQL Server® are registered trademarks of Microsoft Corporation in the United States and/or other countries.

We're pleased to announce the availability of UDT 3.2.2 in your customer portal. 3.2.2 now includes the same version of Orion Core as in NPM 11.5.1 in addition to UDT bug fixes.

Naturally, features and improvements introduced in User Device Tracker 3.2.1 are also present in this latest and greatest version of UDT.

Looking forward to your feedback!

Following recent UDT 3.2.2 Service release in which we added Web alerting and brought back the ability to manage nodes without a re-discovery, the development team is already working on new features for next release. Below is a highlight of some of these items in the pipeline.


Improved Juniper support

Web Reporting

Whitelisting improvements

Err-disabled port status in UI

Cross-product Integration

  • NTA endpoint details displayed in UDT and vice versa


Disclaimer: Comments given in this forum should not be interpreted as a commitment that SolarWinds will deliver any specific feature in any particular time frame. All discussions of future plans or product roadmaps are based on the product teams intentions, but those plans can change at any time.

User Device Tracker (UDT) 3.2.1 Release Candidate is now available in your SolarWinds Customer Portal.


UDT 3.2.1 brings back ability to monitor new switches and routers without a need to do re-discovery. You can now simply go to Port management page =>


... and choose from a new dropdown to see devices not monitored with UDT (e.g. anything you’ve just added to NCM, NPM etc.).


Selecting desired nodes and clicking on Monitor with UDT will make all their ports monitored within one polling interval (default is 30min).


The Release Candidate is a fully tested and supported release and you can upgrade to the RC from your previous version of UDT.

Should you need assistance during the installation, feel free to contact SolarWinds support or you can use dedicated RC Thwack space.

Looking forwards your feedback!

UDT team

Thanks to the great feedback regarding UDT node discovery, we found several ways we could streamline importing nodes into UDT. As many customers prefer manually adding nodes already present in Orion database, we wanted to make it easier to do so, in addition to the existing Network Sonar option. Below we'll walk through the new flow to add existing Orion managed nodes into UDT, regardless if they are NPM, NCM or devices managed by other Orion products.


As the primary reason for adding nodes is the port monitoring, we decided to make this flow start at Port Management page under UDT settings.


A new drop down menu allows you to work with existing monitored ports and nodes already managed by UDT in addition to selecting those managed by other products.



Once selected from the list of unmanaged nodes, you can continue the import by clicking on new button: Monitor Node by UDT


New nodes will be imported in the background so you can keep working without the need to wait until the process is finished.

Once the import is completed, an Event message about the success is displayed.

Apart from adding this new import option, we are also looking at future improvements to the Polling of VLANs. Newly, suspended VLANs will not be polled, saving system and node resources especially in bigger and more complex networks with more VLANs.

Dear Network Admin,

It's a pleasure for the whole User Device Tracker product team to announce that UDT 3.1 is now Generally available at the customer portal!


This latest UDT release brings some significant improvements to the existing Discovery as well as new features so let's recap what is included:


As you can see, we absorbed a lot of your feedback and we plan to continue... Therefore, please feel encouraged to submit even more feature requests so we can make the product even better!

A special thanks goes to Beta and RC takers who sacrificed a bit of their time to help us make the product more stable...


Best Regards

Peter Ksenzsigh

Good news everyone!

It is my pleasure to announce General Availability of Solarwinds Engineer's Toolset (ETS) v11, the most innovative release in many years history of this product. First, let's take a look at what is completely new in v11:


Toolset on the Web

As many of you requested tighter integration of ETS to our single plane of glass platform - Orion - we are happy to introduce you 5 new tools accessible directly from the Web console:

  • Real-time Interface Monitor
  • Real-time Memory Monitor
  • Real-time CPU Monitor
  • Response Time Monitor
  • Trace route

The biggest difference between these new ETS Real-time monitors and standard Orion monitors is higher data granularity. Thanks to the reworked polling and charts, you will be able to display data in shorter configurable intervals (up to 5sec polling). All new tools can be found at a new Toolset tab....


...or even better, by clicking on dropdown menu present in many Orion resources. Note that tools suggested in the drop down will change depending on the context - e.g. if troubleshooting interface, dropdown list will contain only tools related to interface and will not bother you with CPU monitoring option.


After calling any of new monitors to action, you will get to the Configuration Wizard where you can edit your selection before getting to results page. Here, you can even temporarily add a node otherwise unmonitored by your Orion and perform ad-hoc discovery of ports/CPUs/memory... All you need is to add the right IP and SNMP credentials. This option doesn't have any impact on how nodes are counted for other products licensing purposes, as the non-Orion node will be forgotten once a tool is closed.


Default view type is a chart, with a possibility to switch to the table display if more elements needs to be monitored than it's practical to visualize on the chart. Every chart instance is capable of rendering max.12 lines either for one node interface or 12 different ones. Since the history retention is 10 000 points, you also don't have to worry about several hours monitoring with the 5 sec. polling interval. There is also detailed statistics table available under the chart to help you see the Max/Min/Average values. Naturally, you can export results to PDF/CSV...


Admin is by default assigned first Toolset on the Web "seat", assigns Toolset rights to specific Orion users and also can change global settings for everyone. Each user can personalize polling interval, SNMP credentials, thresholds for every tool and metrics available for selection in the chart view.


Thanks to the integration with Orion Web console, you can now run new tools from literally anywhere you have access to your Orion server - even if it is your mobile. Min. recommended hardware in this case is a mobile/tablet with 2 cores and 1gb of RAM. Mobile views are supported on both major OS types - Android and iOS and their default browsers.



Engineer's Toolset Licensing

Another big change in this release is a move from "singleton" licensing to the seat based model. This change was necessary to satisfy users who want to use Desktop Toolset on a different machine than Toolset on the Web (which will be ideally installed on the Orion server). In other words, starting today you will see 2 different activation keys in your customer portal - one key for a Desktop and one for Web installer. To allow more users to use Toolset on the Web, you need to activate respective number off keys on your Orion server using License Manager application.

As some of you own multiple Toolset licenses and v11 brings extra set of Web keys, we have decided to make your life a bit easier also when managing increased number of activation keys. With the license merging function, you can request a merge of your licenses to one multi-seat license for all your Desktop Toolsets and one for Toolsets on the Web in Solarwinds customer portal. All criteria for merging are described in this video: Engineer's Toolset v11 License Overview - YouTube

Installation and Getting started

In order to enjoy new features in v11, install and activate both installers included in the download package. For customers owning also another Orion based product, it is recommended to use the existing SQL database during installation of Toolset on the Web. Others can install Toolset on the Web even on a clean server, as the installer contains Orion core and SQL database. Ability to manage 10 nodes comes for free with the Orion resources, so you can try out these core features together with new tools even if ETS is your only Solarwinds product.

Extra installers for additional pollers and additional web sites are also available for download on your customer portal. Once installed, Orion Admin is assigned first seat and ability to assign other available seats (depending on the number of seats activated) to existing Orion users.

Please feel free to leave your feedback using comments and/or request more tools to be integrated with Orion using Engineer's Toolset Feature Requests ...

Thanks and have a great day!

Peter Ksenzsigh


Fellow Engineers,

Starting today, you will have a new and shiny Engineer's Toolset (ETS) v11 RC available for a download at your portal. This version brings a lot of changes, so please read carefully following lines on how to install and activate it...


First of all, you may wonder: What's new?

Feature-wise, there are 5 new Web tools that you can run either standalone or integrated with an Orion console and the list includes:

  • Real-time Interface Monitor
  • Real-time Memory Monitor
  • Real-time CPU Monitor
  • Response Time Monitor
  • Trace route


These real-time monitoring and troubleshooting tools can render data on the chart in 5 sec intervals with the retention of 10000 points, therefore allowing you to gather hours of granular statistics for one interface, or even 12 interfaces in one chart if you need. Also, you can run up to 3 concurrent tools in the same browser. If a maximum of 12 metrics monitored is not enough for you, there is always an option to switch from the chart to a table view, where hundreds of different metrics can be displayed simultaneously for dozens of interfaces/nodes.


Thanks to the native Orion integration, new Toolset on the Web will be accessible also from mobile devices (please note that higher-end devices, with at least 1gb of memory are recommended for the seamless experience (e.g. Samsung S3 will work, iPhone 3 won't...)



In v11 there also completely new installation and activation steps, summed below in order of importance:

The download package contains 2 installers - 1 for the classic ETS and 1 installer for Toolset on the Web (which includes also Orion core and SQL database). 2 Installers exist because you may wish to install on 2 different machines (e.g. your PC and Orion server). Still, you can install both on Orion server/pc only...



Since there are 2 installers, there are also 2 activation keys (named respectively) in the licensing section of your customer portal. If you wish to install both, Desktop and Orion Toolset, you will need to use both keys. These RC keys are timebombed and after they expire, your ETS will automatically start using proper v11 keys.


Once ETS Web is installed, you should log into the Orion console as Admin to allow other users to run new tools. By default, Admin is the only user given the ability to assign seats to other users. Depending on the number of your Toolset licenses, you will be able to assign respective number of available seats to existing Orion users. Since you can share the credentials between multiple users, we've decided to implement cookies-based access limitation, so you won't be able to run Toolset on the Web from 2 browsers using the same username..


Apart from the access administration, you may wish to change default SNMP credentials, metrics which can be monitored or optional thresholds.



Should you have any difficulties to activate or use the new v11, please don't hesitate create a thread in the Engineer's Toolset Release Candidate group on the Thwack , contact our support or even ask me directly for an assisted installation with the Dev team.

Looking forward your feedback!

Peter Ksenzsigh

Product Manager

Filter Blog

By date: By tag:

SolarWinds uses cookies on its websites to make your online experience easier and better. By using our website, you consent to our use of cookies. For more information on cookies, see our cookie policy.