I have run into a situation where I would like the ability to ignore the conflicting process and force close it when the device is in a maintenance window. But then also still maintain the conflicting process method when outside the maintenance window. As Cody Mathis put it "Interactive if outside the MW, and force close inside the MW."
               
            
          
+3
+3, this would resolve an issue we're seeing in our org right now where we have multiple sites where some have maintenance windows for workstations which want updates to close conflicting processes automatically, and others do not and let updates through during business hours where we want the notification and defer after timeout.
I had briefly explored the idea of a pre-script which checks for an active maintenance window in WMI/CIM CCM_ServiceWindow class and killing processes if a window was detected, but doing that for every application would be a pain to say the least! Having this functionality would help a lot 👍
I need more votes..