SAM 6.6 Release Notes

Updated February 15, 2019

These release notes describe the new features, improvements, and fixed issues in Server & Application Monitor 6.6. They also provide information about upgrades and describe workarounds for known issues.

For detailed system requirements, see SAM 6.6 system requirements.

New features and improvements

Read this section for descriptions of new features and improvements offered in this release. For previous release information, see SAM Previous Versions. You can also compare this release with previous releases of SAM.

SAM 6.6 is an Orion Platform product that consumes Orion Platform 2017.3.

Application Dependencies

The SAM Application Dependencies feature provides a holistic view of application and server connections, expanding monitoring by detecting how applications and nodes interact with each other. You can use data gathered during Application Dependencies polling to:

  • Understand which applications, application processes, and nodes connect with each another.
  • Ensure that the most important data for specific applications is monitored.
  • Identify unmonitored applications and processes that require attention.
  • Leverage latency and packet loss metrics to determine if an issue is caused by an application or the network.

This contextual visibility of relationships between applications and physical/virtual servers also reduces troubleshooting time. For example, instead of searching through many applications, nodes, and component monitors to determine why an application is slow, you can navigate to the new Incoming Connections resource on the Application and Node Details pages to analyze application dependencies and pinpoint the source of the issue.

To learn about supported environments, Orion Platform settings, and recommended monitoring limits related to the new Application Dependencies feature, see the SAM Administrator Guide.

Other improvements

  • Monitor performance and availability of IBM® AIX® Power Systems with the Orion Agent. Click here to read more about this new feature in our online IT community, THWACK.
  • Updated templates for Microsoft® Windows Server® 2016.

New customer installation

Return to top

Use the SolarWinds Orion Installer to install and upgrade one or more Orion Platform products simultaneously in your environment. When installing new products into an existing Orion environment, the Orion Installer verifies compatibility between the product versions and notifies you if additional steps are needed.

.NET 4.6 is required to use the new installer and will be downloaded when you run the installer. Do not stop the installation after installing .NET 4.6 due to compatibility issues with older versions of SolarWinds software. A reboot may be required after installing .NET.

To eliminate compatibility issues, all required Orion Platform products are upgraded when you complete the Orion Installer.

The installer:

  • Installs or upgrades all products from a single screen. You do not need to download files for each product.
  • Provides an easy-to-follow install path when required. If you upgrade from an older product version, the installer provides upgrade paths custom-made for your current environment so you can complete complex upgrades and installations with ease.
  • Runs preflight checks to ensure your environment specifications match the system requirements for selected product installs. If changes are needed, the installer provides guidance for required versions.
  • Automatically starts the Configuration Wizard as needed after product installs to complete database and configuration tasks.

Before you upgrade

If upgrading from a previous version of SAM, be aware of the following considerations:

  • To ensure a smooth upgrade, do the following:
  • This release candidate will not work on a FIPS-enabled version of Microsoft Windows.
  • If NPM and SAM are on the same server, you will be prompted to upgrade to NPM 12.2 before upgrading to SAM 6.6.
  • If you added a site binding to a host name in an earlier SAM version, you must bind the Orion Web Console to a fully-qualified domain name (FQDN). See this article.
  • Microsoft Azure sometimes uses different terms for the same value in its user interface and documentation. If you plan to monitor Azure VMs, see this article for tips about adding Azure accounts.
  • If you plan to exceed SolarWinds recommendations and monitor 2000 or more Microsoft Azure VMs, see this article if the Orion Platform receives a Status Code 503 - Service Unavailable message when adding an Azure account.
  • To monitor Exchange Server 2016, PowerShell 2.0 or later must be installed and Administrator rights must be granted.

How to upgrade


Fixed issues

Return to top

SAM 6.6.1 fixes the following issues.

Case Number Description

1258420

Asset Details for network interfaces and physical network adapters (vmnics) are consistent between the similar nodes

00025509, 00024449

Updated client libraries to support configuration of WebLogic monitoring.

1231923

Orion Server can authenticate Radius User Experience Monitor. Workaround in this Success Center article no longer needed.

1335417, 1208228

Linux CPU Monitoring Perl template polls nodes with properties that include non-ASCII characters.

1221078

Correct property display names appear in AppInsight for Exchange.

1350045

Asset Inventory polls display warranty dates.

1209647, 1075129, 1142193, 1245162

Statistic thresholds subsist after editing monitoring templates.

See also Orion Platform 2017.3 Release Notes.

Known issues

Return to top

Issue: Apache process monitors templates do not display connections discovered by Application Dependency Mapping.

Workaround: N/A. Updated templates will be provided before GA.

Issue: The Warranty Status for HP servers displays as Unknown in Asset Inventory resource accessible from the Node details page. HP changed the HTML structure of data in its warranty status table. SAM's HPWarrantyPoller will be updated to gather data in the revised format.

Workaround: Refer to the HP Customer Support - Product Warranty Check (© 2018 HP Development Company, L.P., obtained on February 4, 2018).


End of life

See the End of Life Policy for details about life cycles for SolarWinds products.

EoL Annoucements EoE Effective Dates EoL Effective Dates

April 6, 2018

End-of-Life (EoL) announcement – Customers on SAM 6.3 should begin transitioning to the latest version of SAM.

June 6, 2018

End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SAM 6.3 will no longer be actively supported by SolarWinds.

June 6, 2020

End-of-Life (EoL) – SolarWinds will no longer provide technical support for SAM 6.3.

See Currently supported software versions for more information.


Legal notices

Return to top

© 2019 SolarWinds Worldwide, LLC. All rights reserved.

This document may not 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 prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.