Submit a ticketCall us
Home > Success Center > Network Configuration Manager (NCM) > NCM Documentation > Previous Versions > SolarWinds NCM 7.3.2 Release Notes

SolarWinds NCM 7.3.2 Release Notes

Created by Linda Davis, last modified by MindTouch on Jun 23, 2016

Views: 1,014 Votes: 0 Revisions: 5

Updated 09/22/2014

These release notes provide pre-installation and post-installation guidance for SolarWinds Orion Network Configuration Manager (NCM) 7.3.2



SolarWinds NCM versions 7.3.X and after differ from other SolarWinds NCM releases in that it uses a single database for storing NCM-related data and to manage information such as account information that can be shared across all SolarWinds network monitoring products.

One-time jobs may run unexpectedly after job migration. To mitigate this behavior, manually disable all one-time jobs.

In terms of node management, keep in mind that if you were to remove a node from Orion Platform database that node would be removed with all currently stored data about inventory, configs, etc. In short, DO NOT delete any node from Orion Platform (HOME) for which you want to retain such historical data; unmanage that node instead.

New Features and Improvements

SolarWinds NCM version 7.3.X includes the following new features and improvements:

Version 7.3.2

  • Upgrades Orion Platform (2014.2.1):

    This version includes the latest Orion Platform features and versions of existing components.

  • Includes a Parameter for Specifying a Password Prompt in Device Templates:

    This version enables you to specify the password prompt issued by a device as part of the device template, in case NCM is having trouble recognizing the device's prompt (for example, due to unsupported characters).

  • Enhances Support for SWIS Connections:

    The version modifies NCM software to process SWIS connections to any poller.

  • Accounts for the SolarWinds Alerting Service V2:

    This version fixes a problem with the NCM installer not shutting down a specific Orion Platform service.

  • Restores Test Button:

    This version fixes an error with Test button in Edit Properties resource for a node.

  • Enforces Reserved Words:

    In this version NCM ignores custom property names that include reserved words.

  • Moves a Data Migration Module:

    This version fixes a bug related to the location of data migration code module.

  • Restores "Overall Policy Violations" Resource:

    This release resolves a problem that prevents this resource from displaying.

  • Supports SQL Server 2012 SP2 and SQL Server 2014:

    NCM now supports thse versions of SQL Server.

Version 7.3.1

  • Upgrades Orion Platform:

    This version includes the latest Orion Platform features and versions of existing components.

  • Enables Storing of Config Archives on Network Share:

    This version more effectively enables storing your growing archive of device configs on a permissioned network share.

  • Maintains Job Logs:

    The database maintenance job now remove job logs of a specified size and age.

  • Removes Unnecessary Node Information:

    Orion Platform nodes no longer have a Configs subview under Node Details.

Version 7.3

  • NCM and NPM databases become merged:

    Streamlined node management: Using a single database enables NCM to manage its nodes, adding and removing them, on the Orion Platform HOME page.

    Optimized reading and writing: Merging the NCM into the Orion Platform database, and using a single database schema, facilitates the NCM software’s use of SQL statements to efficiently manage the insertion, retrieval, and modification of data.

    Account limitations applied to jobs: Using a single database enables NCM to apply Orion Platform account limitations in creating and managing jobs.

    Subviews: Using a single database schema allows NCM to efficiently support subviews.

  • Enhanced Configuration Management:

    This version introduces a much more flexible user interface for doing your configuration management work.

  • Enhanced EOL/EOS data and data management.:

    NCM offers additional EOL/EOS inofrmation and higher granularity for tracking the reliability of the data.

  • Enhanced Web Console:

    Remotely edit and update device configs.

    Amins can clear all transfers for all users from the Transfer Status resource.

    Jobs Summary sorts by any column in the table.

    NCM uses SWISv3 to manage the web console’s database transactions.


  • Along with the NCM upgrade to version 7.3.2, you must upgrade an integrated NPM to version 11.0.1.


    Note: If you are running NPM and NCM versions in a non-integrated configuration on the same server, and you attempt to upgrade NPM to version 11.0.X and NCM to 7.3.1, you may encounter an error in the Configuration Wizard that reports an NCM database connection string corruption. You can mitigate the possibility of the error by upgrading NPM first. Should you encounter the problem there is a workaround; however, it requires an OS registry edit that is best done in consultation with SolarWinds.

  • You may need to reboot your NCM server host during the upgrade process.
  • SolarWinds neither verifies nor supports EOS/EOL data; consult your vendor with any data-related issues or questions.
  • You must upgrade both the primary NCM server and each NCM additional polling server for the improvements in this release to work properly.

NCM Scalability

NCM was tested for scalability in a standalone deployment of three servers: One server hosts the main NCM server and the other two servers each host an NCM additional polling engine. The main NCM server manages up to 10K NCM nodes, as do each NCM additional polling engine. The deployment therefore supports up to 30K nodes total.

And while using the NCM web console in a normal way, with the Orion Platform on the main NCM polling for node status at the default rate, the tested deployment supports 2 NCM operations (inventory update, configuration download) being performed per day on all 30K nodes.

Though the main NCM server and each additional polling engine can manage up to 10K nodes, the actual total depends on the system hardware of the server hosts, the types of devices being monitored, and the number of jobs being run concurrently. Should you need to manage more devices, and you decide to add NCM servers, consider consolidating your views of multiple servers with the Orion Enterprise Operations Console. For more information about scaling NCM, please contact your account manager.


Fixed Issues

NCM 7.3.2

Issue Case Number

Modifies NCM software to process SWIS connections to any poller.

Fixes problem with the NCM installer not shutting down a specific Orion Platform service.



Enables you to specify a password in a device template for NCM to use in accessing the relevant network devices..



Fixes an error with Test button in Edit Properties resource for a node.



Respects reserved words in evaluating custom property names.



Fixes a bug related to the location of data migration code module.



Resolves problem that prevents Overall Policy Violations resource from displaying.



NCM 7.3.1

Issue Case Number

Fixes an issue with adding nodes to Orion Platform products when NCM role is set to 'NONE'.


Fixes issues blocking NCM config management from writing to a network drive.


641510, 595141, 513001
Fixes an issue with database synch functions in version 7.X causing failed upgrades to version 7.3.



Fixes an issue with config changes not being detected through config download jobs.


Fixes an issue blocking startup config downloads from Force10 switches.



Fixes an issue with the interface alias appearing blank in CatOS device inventories.



Fixes an issue with Policy Reports not including changes in policy configuration.



Fixes an issue that breaks Syslog Tracking Reports.



Sets SWIS version 3 to work with an 'Any CPU' target value.



Fixes an issue that blocks Orion Web Console pages from loading when NCM creates Orion Custom Properties that include names that SWIS holds in reserve.



Makes assignment of a MinVersion value consistent for OIP tasks.



Resolves issue that interferes with comparing configs for some users.



Ensures that old version of the NCM-NPM integration module are removed before upgrade.



Fixes an issue with Config Change Report job logs as completed while showing a status of 'Running'.



Fixes Date/Time inconsistency on Configuration Management page.



Resolves an issue with not showing an error message in Config Management when an additonal poller is down.



Fixes the non-scalable storage of the Config Archive in the NCM installation directory.



Fixes a database migration failure due to corrupted Primary Keys on RoutTable in the old NCM database.



Fixes an issue with display of search results and selected node(s) in Configuration Management resource.



NCM 7.3

Issue Case Number

NCM removed a third-party component "GigaSoft ProEssentials 3D Sci-Graph"(C:\Program Files\Common Files\SolarWinds\Pe3do32c.ocx) that caused a PEstrarg1 Heap Overflow Remote Code Execution Vulnerability

Andrea Micalizzi (aka rgod), working on HP's Zero Day Initiative, discovered this vulnerability; CVE-2014-3459.


Fixed an issue in which 'Default' or 'None' were the only options when trying to associate a custom summary view with a specific user account.


Fixed an issue with managing views (NCM resources in subviews sometimes get moved to a different subview) .


Fixed an issue with configs for Cisco ACE devices not getting backed up to file.


Fixed an issue that obstructed simultaneous Downloads/Uploads option from working.


Resolved an issue in which user could see jobs after upgrade when having NCM Admin role but not Orion Admin role.


Fixed a problem with a Request Approval Email not being sent via HTTPS.


Fixed an issue with dynamic Node Selection not having a "view selected nodes" option.


Fixed an inability to create compliance rules.


Fixed the limitation that, when using dynamic node selection in NCM jobs, there was no option to verify the nodes selected. (For executing a command script, for example, it is very important for one to verify the nodes selected prior to pushing a change.


Resolved an issue with a disabled job being executed if SolarWinds services fail.


Fixed a problem with the Download/Backup config functionality.


Fixed an issue with the Config Change Report being empty.


Fixed a limitation the prevented specifying that a job should run Daily, Every X days, does not work. NA
EOC 1.3 can now poll NCM (7.3). NA
"Start Now" job execution works in supported NCM 7.3 integration of NCM/NPM NA
Fixed an issue with adding nodes to a nightly config backup job. 517289
Resolved slow config backup with Fortigate devices. -
Resolved issue with Huawei loging prompt obstructing NCM config management. -
Resolved an issue with licensing the limited NCM access to one user. 523105
Resolved an issue with Realt-time Change Detection not emailing changed configs. 523752
Resolved issue with email notifications when PDF is attaached. 462498

Open Issues

Issue Case Number

One-time jobs may run unexpectedly after job migration. To mitigate this behavior, manually disable all one-time jobs.

Post-back driven resources stop working when moved.

Includes: Node List, Search NCM, Inventory Details, Compare Configs, Download, and all charts.

A page refresh often restores functionality.

Error when placing NCM resource on NTA node or interface detail page.


Several protocols/settings/encryption algorithms were not tested:
  • AES256 encryption for IPV6 nodes
  • SNMP config transfer for Catalyst MIB devices
  • Config transfer using Blowfish and CAST128 encryption algorithms
NCM resources do not work correctly when they are on same view as PaM's resources NA
Node List Loads Slowly in NCM Application


The list loads slowly with a large number (10K) of nodes in the database and if the nodes are not grouped.

Browser Script Error


A script fails when loading a node list that contains a group with 30K or more nodes.

Physical Entities (Serial Number) report loads slowly


When there is a large number of records (a million or more) this report loads slowly. However, if you select the sort on a single column option (Settings > NCM Settings > Advanced Settings) then the report runs normally.

Access to Orion Web Console Blocked After NCM Installation


This happens if the SQL account you have assigned to your Orion Platform database has not been configured with apppropriate permissions. You must create a new SQL account with required permissions as detailed in thisKnowledge Base article.

Config Download Aborts


When downloading a config from a device, if the config line (for example, the hostname on a line by itself in the banner text) exactly matches the length of the device's prompt, the download ends.

Since the issue is almost always triggered by banner text, make sure that you surround any such text with comment operators. For example, if your hostname appears in the banner text as LGC6509E, you would change it to "*LGC6509E*

NCM Repair and Change Processes


If you are running NCM server on Windows 2008, and you need to repair NCM or change its installation, follow the steps in this Knowledge Base article.

Telnet Icon in NCM Node Details (IE)


The Telnet icon on the NCM Node Details page and the Configuration Change Report results page of the SolarWinds NCM Web Console does not launch the Telnet window. To correct this issue, add the following registry value:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_DISABLE_TELNET_PROTOCOL] "iexplore.exe"=dword:00000000. This is a known issue with Internet Explorer 7.

NCM Search Does Not Find Partial Word Values (IE)


Due to the use of Full-Text Search, partial word searches are not supported. You can find the beginning of a word, but you cannot specify the middle or end of a word on which to search.

Importance of policy updates (Cisco Energywise)


Currently, the importance of policy updates is hard coded to 100. At this time, this is caused by a limitation imposed by the EnergyWise MIB data collection mechanism.

Time returned by device (EnergyWise)


The time returned by and EnergyWise device is based on the device time. Therefore, recurrence policies (based on chron jobs) respect the time set on the device, not the time of SolarWinds NPM or SolarWinds NCM.

Recurrence Policy and Chron Jobs


Do not use a 7 to represent Sunday in the day of the week option of your recurrence policy. At this time, 7 is not recognized by SolarWinds NPM as Sunday and will cause problems with your EnergyWise Policy Overview Calendar.

International time format


A number of areas in the Local Client application, the Web Console, and the SolarWinds NCM Integration for SolarWinds NPM display the wrong time format when you change the system settings to display an international time setting. This is a known issue and will be corrected in an upcoming release.

NCM resources added to NPM

Adding SolarWinds NPM summary or node details resources to SolarWinds NCM views can result in the SolarWinds NPM resources no longer respecting node filtering, essentially providing a network-wide view.


Installing or Upgrading this Version

Installing this Version

Note:: Do not install NCM on a machine with a hostname containing more than 15 characters.

You do not need to uninstall your previous version before installing this version of SolarWinds NCM. Shutdown any running SolarWinds NCM applications, and then run the setup program. The setup program will detect and uninstall your previous version without a loss of customizations, other than customizations to the toolbar. Toolbar customizations are overwritten to ensure new toolbar options are included.

Upgrading to SolarWinds NCM 7.3



  • Along with the NCM upgrade to version 7.3.x, you must upgrade an integrated NPM to version 11.0.1.


    Note: If you are running NPM and NCM versions in a non-integrated configuration on the same server, and you attempt to upgrade NPM to version 11.0.X and NCM to 7.3.1, you may encounter an error in the Configuration Wizard that reports an NCM database connection string corruption. You can mitigate the possibility of the error by upgrading NPM first. Should you encounter the problem there is a workaround; however, it requires an OS registry edit that is best done in consultation with SolarWinds.

  • 7.3 is a major upgrade of the NCM software. SolarWinds strongly recommends consulting the SolarWinds Network Configuration Manager Admininstrator Guide for the detailed instructions on upgrading NCM to version 7.3.


  • This version of SolarWinds NCM does not support upgrade in a separate server deployment.

    You must migrate to a single server deployment (integrated or non-integrated) as part of upgrading to NCM 7.3.

  • There is no distinction between the Orion Platform poller and the NCM poller in NCM version 7.3. The host on which you install/upgrade the NCM Server software becomes the main poller and performs all node-related polling and NCM operations. If you have other Orion Platform products installed on the same host (and so integrated) with NCM, the same poller manages nodes for all Orion Platform products combined.

    Similarly, if you divide managed nodes among the main poller and additional pollers, then you should expect each poller to handle all relevant node-polling, NCM-related work (scheduled config downloads, etc.), and other work related to the Orion Platform modules (NPM, NTA, etc.) installed on the additional polling host.

    As part of setting up additional pollers in your environment, so that device templates are available on the relevant poller hosts, you must install the NCM Additional Poller software on each additional poller host. You may also need to open firewall ports on the additional poller hosts to enable the NCM software to operate successfully.

  • You may need to reboot your NCM server host during the upgrade process.
  • Backup your database before performing any upgrade of SolarWinds NCM.
  • In upgrading a deployment that is already integrated with SolarWinds NPM, the SolarWinds NCM installer will shutdown all SolarWinds services on the host machine where SolarWinds NPM is running.

    Bear this in mind in choosing a time to perform your upgrade.

  • The Orion Platform software components does not support multiple address types associated with a node. So if in NCM you have an IPV4 and an IPV6 address associated with an NCM node, when you upgrade to NCM 7.3, only the IPV4 address will be retained in the Orion Platform database for the node.

If you are an existing customer, and your current version does not qualify for a direct upgrade to SolarWinds NCM version 7.3, you first need to install the versions of SolarWinds NCM that at least bring your installation to SolarWinds NCM version 7.2. For example, if you were running SolarWinds NCM version 6.0, you would need to install SolarWinds NCM versions 7.0 and 7.2 before you can install SolarWinds NCM 7.3. Additionally, in this case, should you want to gain access to the latest NCM/NPM integration features, you would need to upgrade your SolarWinds Network Performance Manager software to version 10.7.

Custom properties you created in NCM prior to version 7.0 will not be merged into the Orion Platform database. If you are upgrading from NCM version 6.X, you should run a Node report before you upgrade. You can then recreate your NCM custom properties in the Orion Web Console in version 7.0 and use your report to assign appropriate values. For details on creating custom properties, see the section “Creating a Custom Property” in the SolarWinds Network Configuration Manager Administrator Guide.

If you need previous versions of SolarWinds NCM, Contact Customer Service and Support (



NCM 7.3 uses an Orion Platform of core components shared by all SolarWinds network monitoring and management products. If NCM is installed on a server with another of these products the installer automatically integrates them.


Licensing SolarWinds NCM

See "Obtaining a Software License Key" in the Orion Network Configuration Administrator Guide for details on licensing SolarWinds NCM.


SolarWinds End of Life Policy

In order to continue to drive innovation and new functionality into our products, SolarWinds must transition customers from legacy versions of software to our current versions. Please review the below support schedule:

  • 05/27/2014 End-of-Life announcement (EoL) – Customers on SolarWinds NCM v7.0.2 or older should begin transitioning to SolarWinds NCM 7.3.
  • 8/31/2014 End-of-Engineering (EoE) – Service release, bug fixes, workarounds, and service packs for SolarWinds NCM v7.0.2 or older will no longer actively be supported by SolarWinds.
  • 8/31/2015: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds NCM v7.0.2 or older.

View the SolarWinds EOL Policy online.


Copyright 2014 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.


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