Scenario:
Added two nodes and set my custom property BackupSchedule to GENERIC. Fired up Unmanage Task Editor, sorted by BackupSchedule and selected all GENERIC and saved the task with the same name. I searched the C:\Program Files (x86)\Solarwinds\Orion\UnmanageUtility\Jobs folder for the nodes I just added and could not find them.
At this point I ran my unmanage job and then the report of unmanaged nodes. Indeed I had not unmanaged the two servers I just added. It was a little painful searching for the servers among the thousand or so others (feature request?) via the Unmanage Task Editor, but the Report Writer showed me that my newest nodes were not among the unmanaged. At least Report Writer PDFs are searchable.
I updated the Report Writer schema from the Custom Property Editor and then used Unmanage Task Editor and sorted by type netSNMP. I saw my two newest nodes at the bottom of this list.
I think updating the Report Writer schema after populating my BackupSchedule property finally made my new nodes appear in Unmanage Task Editor. Normally, one only does that after creation of a new custom property. Are there any known bugs with respect to Unmanage Task Editor?
Perhaps if there was a built-in find feature in Unmanage Task Editor, it would make searching the XML file it generates unnecessary. With thousands of nodes falling under the custom property value, it's tough to prove the most recently added nodes have the proper alert suppression during backup cycles. Searching XML files and running reports seem like too manual of a method of verifying alert suppression is in place every time I add a node.