Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Server & Application Monitor (SAM) > SAM 5.2.1 Release Notes

SAM 5.2.1 Release Notes

Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 1 Votes: 0 Revisions: 4

Updated 11/05/2012

Beginning with version 5.0, Orion Application Performance Monitor, (APM), has been renamed to SolarWinds Server & Application Monitor, (SAM). These release notes provide additional guidance for SolarWinds Server & Application Monitor (SAM) version 5.2Sp1.

Installing this Version

As with all modifications to your production environment, it is suggested that you complete the following tasks before implementing any changes:

  • Back up your database.
  • Test the change in a lab environment that mimics your production environment.

If you need a temporary license to install an instance of the software in a lab, please download an evaluation copy of the latest software from our website. Evaluation copies come with a fully functional 30-day license.

Warnings:

  • Additional Orion Web Servers must be able to communicate with the primary SAM server on TCP port 17777. If you are within a secured network and have separated the polling engine component from the Web Console or are using additional pollers, make sure the polling engine is reachable on port 17777.
  • Whenever you upgrade SAM, ensure you first back up your database.

Note:

If you are installing SAM through a terminal server session, use the Add or Remove Programs utility on your server (Start > Control Panel > Add or Remove Programs) to run the SAM installer. For more information, see "Installing Server & Application Monitor" in the SolarWinds Server & Application Monitor Administrator Guide.

Upgrading and Configuring

If you have both NPM and APM installed, upgrade NPM on all SolarWinds servers first, followed by the pollers. Once that is complete, you can successfully upgrade to SAM. Failure to upgrade in the correct order will result with the Configuration Wizard generating a Database Configuration Failure error.

If you have additional APM pollers or web consoles, upgrade them at the same time as your APM server. Update the main poller first, then the additional pollers and/or web consoles. Additional web consoles and pollers communicate with the primary SAM server on port 17777.

SAM 5.2 supports upgrading from APM 4.0.2 and higher. Direct upgrading from APM 3.1 and 3.5 is not supported.

If you have APM 4.0.2, 4.2, or SAM 5.0.1 installed with NPM, then you must first upgrade NPM to 10.3.1 or higher before upgrading SAM.

Follow the appropriate procedure in the section "Upgrading Server & Application Monitor" in the SolarWinds Server & Application Monitor Administrator Guide.

Repeat this procedure for any additional pollers or Web Consoles, making sure to use the correct installers for pollers (SolarWinds-Orion-APM-vx.y.z-Poller.exe) or web consoles (SolarWinds-Orion-APM-vx.y.z-WebOnly.exe), since these are different from the standard installer package.

If you are licensed for additional polling engines or additional web servers, they can be found in your SolarWinds Customer Portal. The additional Poller components must be installed on all additional pollers. The additional web server components should also be installed on all additional web servers. Both the additional poller and web server components should be at the same version as the primary SAM server.

Notes:

  • SolarWinds SAM does not support monitoring interfaces. To monitor interfaces, please explore the features of NPM.
  • If you purchase a SAM license to use with NPM, the additional nodes allowed in the SAM license can monitor CPU, Memory, and response times for nodes, however they cannot monitor interfaces.
  • Downgrades of SolarWinds products are not supported. If you are upgrading or installing multiple SolarWinds products, confirm that you are installing them in the order given in the Upgrade Instructions located in your SolarWinds Customer Portal.

Migrating to Another Server

If you are installing the new SAM version to a new server, but plan to use an existing database, you are required to manually copy the original security certificate to the new server before installing the new SAM version. Otherwise you will need to re-enter passwords for all your SAM credentials. For information about copying the security certificate and a workaround to avoid re-entering passwords (if you migrated without copying the security certificate), refer to the following knowledge base article: How can I migrate my credentials when upgrading Orion APM 3.5 to Orion APM 4.0, or higher, on a new server?

Fixed Issues

Issue Case Number
SAM 5.2 reports degraded performance of disks on HP ESX Server. 353354
Nagios Script Monitor does not display messages. 386292
HTTP(s) Monitor: The URL is converted to lowercase characters. 383467
File monitors use Unicode symbols conversion. 353354
Windows Event Log - Exclusion of multiple Event IDs does not work. 368188
'APM.ApmHardwareDetailsViewID.' Error when adding users. 401806

Legal

Copyright 1995-2012 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.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. 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, the SolarWinds & Design, ipMonitor, LANsurveyor, Orion, and 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.

Last modified
03:02, 23 Jun 2016

Tags

Classifications

Public