Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > NCM Compliance Rule RegEx at the end of the line

NCM Compliance Rule RegEx at the end of the line

Table of contents
Created by Bill Corgey, last modified by MindTouch on Jun 23, 2016

Views: 1,004 Votes: 0 Revisions: 5

Updated June 6, 2016


This article provides  brief information on how Policy Rule validations can be written:

  • Find a string
  • RegEx

Using \r  to match the CRLF can produce inconsistent  results.



All NCM versions


Using the \r in NCM is not necessary and could produce inconsistent results due to the format the configuration is received from the device.  

One config may have the CRLF returned directly after the line and the next config from the same device may have white space between the end of the line and the CRLF, so no matter where the \r is placed, results may be varied and logically it is correct.

Example:  hostname bas-3750CRLF  vs.  hostname bas-3750 CRLF

Note:  the CRLF is not visible in NCM. A text editor that allows the view of all characters must be used. 


SInce NCM examines line by line the use of the \r is not needed unless one is specifically looking for the CRLF to be in a specific position.


It is not recommended to use  \r for Policy Rules in NCM.



Last modified