Documentation forServer Configuration Monitor

SCM 2020.2.1 Release Notes

Release date: August 25, 2020

These release notes describe the new features, improvements, and fixed issues in Server Configuration Monitor (SCM) 2020.2.1. They also provide information about upgrades and describe workarounds for known issues.

If you are looking for previous release notes for SCM, see Previous Version documentation.

See also SCM 2020.2.1 System Requirements.

New features and improvements in SCM

Return to top

SCM 2020.2.1 offers new features and improvements compared to previous releases of SCM. You can also compare this release with previous releases of SCM.

Policy compliance

Operationalize policy compliance monitoring for your servers and applications by tracking their compliance percentage across your environment over time. Drill down from policy summaries to nodes to individual rules, and see both a description of what the rule is monitoring and the steps to remediate failed compliance.

Out-of-the-box policies

Three out-of-the-box policies included with SCM are based on a subset of the official standard Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIG) policies.

  • Windows Server 2016 STIG
  • SQL Server 2016 Instance STIG
  • IIS 8.5 Server STIG

Compliance reports

Deliver quick visibility of both overall compliance and the details of every evaluated rule to your security and legal teams.

New alerts

Be alerted when policies fall below a threshold or when an individual rule fails.

Import and export policies

Import and export policies and share them on the SCM Thwack exchange forum.

Orion Platform 2020.2.1 improvements

For details, see the 2020.2.1 Release Notes.


New customer installation

Return to top

For information about installing SCM, review system requirements and use the SolarWinds Orion Installer, which you can download from the SolarWinds Customer Portal. After installation, use the SCM Getting Started Guide and the SCM Administrator Guide to learn about configuring and using SCM.

How to upgrade

With SCM 1.2 and later, you can upgrade your entire Orion deployment, including the main server and all Orion Platform products, from the My Orion Deployment page. Downloading the Orion Installer for future upgrades is no longer necessary.

If you are upgrading from SCM versions earlier than SCM 1.2, use the following procedure:
  1. Use the SolarWinds Orion Installer to simultaneously upgrade one or more Orion Platform products on your main Orion server.
  2. If your scalability engines (additional polling engines, additional web servers, and high availability servers) are able to communicate with the main server, use the centralized upgrade feature to upgrade the rest of your Orion deployment in parallel. For details, see Install or upgrade Orion Platform products.

Fixed issues

Return to top

SCM 2020.2.1 fixes the following issues.

Case Number Description
N/A After importing a profile as a copy, the profile displays with pre-filled elements. When assigned to a node, these elements no longer display an invalid credentials issue.
N/A HW Inventory HardwareInfo element is no longer too noisy for RedHat 7.
N/A

The "World Writeable Files" element of the Linux Security and Permissions SCM profile was improved to prevent scanning remote filesystems. In addition, incorrectly reported files were corrected. For instance, the script will not incorrectly report content as writable if the files were mounted as read-only.

N/A Users can now create custom reports using CustomTable.

Fixed issues in Orion Platform 2020.2.1

Return to top

SCM runs on SolarWinds Orion Platform 2020.2.1. For information on features and improvements, and to learn more about additional changes not listed here that affect all Orion Platform products, see Orion Platform 2020.2.1 release notes.


Known issues

Return to top

Asset inventory does not display operating system information for Linux
Issue: When viewing asset inventory, Linux operating system information is not shown.
Resolution/Work-around: None

 

Warranty data does not appear after Asset Inventory polling of HPE Proliant servers
Issue: Recent changes to HP Warranty servers interrupt periodic polling.
Resolution/Work-around: None. Click here for details.

 

Warranty data does not appear after Asset Inventory polling of Dell servers
Issue: Recent changes to Dell Warranty servers interrupt periodic polling.
Resolution/Work-around: None. Click here for details.

 

Unable to use custom credentials for IIS 8.5 Server STIG policy
Issue: Local admin account cannot be used to poll IIS policy.
Resolution/Work-around: The work-around for this issue is not to use any custom credentials so that the agent uses the LocalSystem account, which works.

 

Alert "Policy compliance % is below threshold" doesn't respect limitations
Issue: The alerting policy is whole policy, and there is no limitation on this object. The alert is triggered when overall compliance is below the threshold. When the user opens the detail, they may see a different compliance percentage value, as assignments to restricted nodes are excluded from the user interface.
Resolution/Work-around: None

 

Custom Discovery step for SCM is not available on additional website
Issue: If the user installs SCM and then also installs an additional website, then navigates to Network Discovery, creates a new one, and clicks Monitoring Settings > Define monitoring settings, there is no discovery step for SCM in the wizard. This is because the SCM Discovery plugin definition is not deployed to the additional website.
Resolution/Work-around: None

 

Out-of-the-box IIS profile incorrectly detects changes for paths that end with a backslash
Issue: The out-of-the-box IIS profile detects changes for paths that end with a backslash when no change has occurred.
Resolution/Work-around: None

End of life

Return to top

Version EoL Announcement EoE Effective Date EoL Effective Date

1.0

1.0.1

1.1

June 4, 2020

End-of-Life (EoL) announcement – Customers on SCM 1.0, SCM 1.0.1, and SCM 1.1 should begin transitioning to the latest version of SCM.

September 4, 2020

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

September 4, 2021

EoL – SolarWinds will no longer provide technical support for SCM 1.0, SCM 1.0.1, and SCM 1.1.

See the End of Life Policy for information about SolarWinds product lifecycle phases. For supported versions and EoL announcements for all SolarWinds products, see Currently supported software versions.


Legal notices

Return to top

© 2020 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.