Deployment Filter Script for Schedules

I would like to add a request for making a Filter Script option within the Maintenance section of schedules, similar to the Filter Script functionality that already exists for Target Type selection.

Current Limitation
When configuring maintenance schedules, we are limited to two options:

  • Full Maintenance, which runs everything
  • Limit to a specific maintenance item, which runs exactly one deployment

There is currently no way to say:

  • Run everything except these specific deployments

Why This Matters
We manage global deployments across multiple tenants and occasionally need to exclude specific deployments during scheduled maintenance. This would be a huge time saver and value add, since it would eliminate the need to change a global deployment of “adobe” to be tenant specific for everyone except the new client.

Proposed Solution
Adding a “Filter Script” option to the Maintenance section that allows PowerShell logic to include or exclude deployments dynamically. This could work the same way Target Type filtering already does and it fits really well with ImmyBot’s automation-first approach.

Related Community Discussions
I’ve seen a few other folks asking for more scheduling flexibility in different ways:

This would be exactly the flexibility we need. It would be awesome if we could use the same filter script approach that’s already working so well for target selection, just applied to which deployments run.

While I do realize you can set an ignore for deployments in the specific tenant. I think this could be a more scalable/versatile option if you especially if you wanted to do multiple exclusions across multiple tenant schedules.

This would also allow for improved automated 3rd party application patching!

Say you have a schedule and you have some deployments that need a reboot and some that don’t. You’re not going to want to hit apply on connect because the deployments that do need a reboot might negatively impact the user.

But if you are able to use filter scripts then you just need to make 2 schedules, one that target applications that don’t require reboot and you can set to apply on connect, the other that targets application/windows os updates that need a reboot and you can set to skip if not online.

This would allow for scalable schedules instead of schedule sprawl.