Iolair

Thanks for the reply. IE11 hadn't been shown as an update since it came out, but that changed in May. We always run a month behind on updates to allow kinks to be ironed out before we apply the updates to clients. By default there is no severity classification on most of the updates, so we have a rule in the ADR that states anything but "Low" severity updates are included, and if we don't want an update to be included in the update group we put a custom severity of "Low" onto that update so it is excluded. This has worked fine in the past, and I set this severity on IE11 on Friday, however come Saturday, when the ADR ran and created the Software Update Group for May, the rule was ignored and IE11 included. The very scenario you suggested had previously happened with IE10. Microsoft had changed the classification from a Security Update to an Update Rollup, and it slipped through that way, hence why we have been especially careful about IE11, and so the frustration over this (*use polite words....) "hiccup".

Hi, Firstly, great tutorials, very useful indeed. Have a weird one that has occurred today. We have an ADR set that includes severities so that we can set a custom severity of "low" to exclude any updates that are pushed out to the clients. However, in the latest batch of updates, I had marked up IE11 as low, and for some reason I cannot fathom, it was included in the deployment and so was released out onto our clients. Obviously, this isn't ideal, and has resulted in me running around trying to figure out why it's happened, however my co-workers and I cannot find a flaw in the logic of the rule, so I am opening up to the gestalt to see if anyone else might have some idea as the reason behind this. Thanks in advance for any brainstorm that can be provided. All the best, Iolair