We would like to be able to unmanage from of the webconsole a Parent Node of a group and have its children set to unmanage as well. Case # 1171205

Yes!  I think I added similar idea awhile go. This is becoming a big issue and it causes all sorts of trouble with Availability reports, false-positive alarms when forgetting to put a child node into unmanaged mode and worse yet no alarms when a node is missed when placing back into management.

I would go one step further and say this should go with muting alerts too!!!  If a parent node is placed in unmanaged mode or muted status all children nodes should automatically follow suite. And if a parent is scheduled then all children should be scheduled automatically too.

To help make the argument here's an except from the NCM admin guide, Chapter 5 page 227.

"Disabling polling, or setting a node status as Unmanaged, while performing node maintenance, maintains the accuracy of your data and prevents unnecessary alert messages"

This is not true 100% true as all children nodes 1 layer down will alarm and the availability of those node will take a hit during the outage window.  Which in turn are unnecessary alert messages and the accuracy of the data is compromised.