In our environment we do MS patching in phases. Phase 1, Phase 2, and Phase 3 at different times on that week. We currently are using a process where when the robot is added we put the Patching Phase in the the Tag #2 field of the robot. Than in the UMP we have groups created so that any robot that has a Windows OS and Phase 1 goes into a certain group. Than we apply a maintenance window to that group each month for the selected amount of time.
However we also have e2e tests and URL checks on other robots that are looking and testing certain URLS and apps. So if a web server goes does in Phase 1 but we have another Robot checking that the URL is up and accessible or the app is up and accessible they will fail while the box is being rebooted during patching or is not accessible during patching. We are trying to as much as possible suppress all alarms that might be caused by patching during each phase time duration.
Has anyone come across a more efficient way of applying maintenance mode so that we get as many alarms as possible suppressed in the safest most efficient way?
In addition to what you are already doing , use Pre-Processing rules in NAS to exclude the alerts based on specific filter criteria . You can set the operating period for the rule or assign the rule to a scheduler , Pre-Processing rules are more effective than the maintenance schedules specifically when it comes to suppressing the robot inactive alerts or alerts generated by a specific probe or even based on a message string