Updated April 29, 2014
These release notes provide additional guidance for SolarWinds Server & Application Monitor (SAM) version 6.1.1.
As with all modifications to your production environment, it is suggested that you complete the following tasks before implementing any changes:
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.
Important: For customers with additional pollers, please note that the 'Local-Only' setting was removed in SAM 5.5. For more information on how this may impact your environment, see SWKB 4429.
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 this release of SAM. Failure to upgrade in the correct order will result with the Configuration Wizard generating a Database Configuration Failure error.
If you have additional pollers or web consoles, upgrade them at the same time as your SolarWinds 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.
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.
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?
This release of SolarWinds SAM includes the following open issues:
This release of SAM includes the following fixes and additions:
The following table provides the internal Development ID numbers and external support ID numbers for fixed SAM issues as well as new feature requests in this release. Search in the support ID number column for the number assigned to your support case.
|Superscript||Support ID number||Development ID number|
|f, m||594985, 602168||323456, 328549|
|n, p, q||594888, 583631, 601187||323753, 325219, 327131|