Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Scheduling Unmanage Task for Nodes, Interfaces and Applications

Scheduling Unmanage Task for Nodes, Interfaces and Applications

Table of contents

Overview

This is post #2 of our Orion NPM 10.0 Sneak Peak series. Consider the following scenario: every Saturday at 2am we have a policy to reboot xyz devices.
 
Today, a user would have to go in weekly and set up an unmanage task within web node management in the web console.  With 10.0, this becomes much easier as you will be able to define recurring unmanage schedules or recurring maintenance windows. For folks unfamiliar with the concept of “unmanage” (a very Orion specific term), this in essence allows you to define a time period when a node, interface, or application will be down and you do not want to receive alerts on it or have it show as down in the UI.

Environment

  • All NPM versions

Steps

1. When you install or upgrade to 10.0, you will need to go to the additional components of the SolarWinds Customer Support portal where you can download this utility or if you are on the NPM 10.0 Release Candidate and want to check this out, send me a private message via thwack.  Once downloaded, unzip it into your SolarWinds/Orion folder on the Orion server as shown in the screenshot below.

2. Once extracted, open the Unmanage Editor.exe and you will be presented with a welcome and instruction screen as seen below.

 

 

3. Click on Create a new task and select the nodes, interfaces and applications you wish to add.

4. Click add and select the duration or time period you want these item to be unmanaged for and select OK.