Showing results for 
Search instead for 
Did you mean: 
Create Post

Scheduling unmanage task for nodes, interfaces and applications

Product Manager

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 setup a unmanage task within web node management in the web console.  With 10.0, this will become 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 allow you to define a time period when a node, interface or application will be down and you do not want to receive alerts on or have it show as down in the UI.

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.


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


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


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


Now once you save the task you will receive a popup dialog indicating it has been saved and copied to the clipboard for use in an upcoming step.


So what does this produce on the backend when I saved it?  Since we are leveraging Windows Task Scheduler to handle the scheduling, this creates a .cmd file which has the appropriate switches and parameters Windows Task Scheduler needs to execute this.


You can either manually navigate to the Windows Task Scheduler or click on the Open Windows Task Scheduler within the Unmanage Utility and click on Add Scheduled Task.  As you walk through the wizard, when you get to the step to select the program to run, navigate to the /Orion/UnmanageUtility/Tasks folder and select the .cmd file you created for this job.


These next dialogs walk you through setting up the start time, date and frequency and which account to run this under.  This is a Windows account, not a SolarWinds account.



And that’s it.  If you want to edit an existing job, you can go into the new unmanage interface and select edit and choose the job you wish to edit and then save it.  If you want to change the frequency or disable the job you can do this with the Windows Task Scheduler interface.

Level 9

Are there way to sort out the nodes names. We have over 2000 servers and when I try to add a server into Unmanaged Task Editor, I have to go look at 2000 servers.


While a step in the right direction, please look at and vote up

This takes the concept several steps further and could be applied to everything.  Define your window in one place and associate servers, groups, applications, alerts, etc. to it.

The common and critical part is defining the Window in one place, one time.  Any modifications are applied in one place and one time and not to 20, 60, 120 or so alerts, monitors, 489 servers, etc.

It is instantly scalable if done by groups...

Level 12

I agree with rollcage. We need our server department to be able to set up these maintenance windows, but giving RDP access to our main SolarWinds server to the entire department is a little ridiculous.

About the Author
I have currently been at SolarWinds for a little over three years and have been in the IT technology field for about 10 years either as an Engineer/IT Admin or working for a software company to help makes those folks lives easier.  I graduated from Texas A&M University with an MIS degree from the Business School and have been in Austin for about 8 years.