Not really. That's kinda of the point of an exclude rule; it's a collection-specific configuration, not something you can blanket apply to multiple collections.
In theory, you could change the limiting collections for all of your production software updates collections to one that itself has the Exclusions collection excluded...but that's a rather convoluted way to go about it. The reality is that your production SU collections should not be changing much, so adding the exclude rule should be essentially a one-time adjustment. Do you have any Maintenance Windows in place for your Exclusions collection? -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Microsoft VTSP ([email protected]<mailto:[email protected]>) Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 [speaker2]<http://mmsmoa.com/>[linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Monday, April 4, 2016 9:14 AM To: [email protected] Subject: [mssms] Exclude Rules Good day, I have an Exclusions collection I use to exclude devices from my production software updates collection. It has been reported that some devices that are a member of the exclude collection is getting rebooted. After examining collections this device was a member of, I realized there are other collections (such as 3rd party updates) that this device is also a member of. Currently, I am not suppressing reboots on these deployments. Is there a better way to manage the Exclude Rules across the board w/o having to go into every single collection and create the Exclude Rule on a target collection that has deployments setup that will reboot said devices? Thank you, Brian M.
