Yeah, I guess the problem I'm really having is that we are behind in patches so in the scenario of KB2949927, the superseded patches were not currently installed. So when MS pulled 2949927, it did not re-elevate all the patches that it superseded. So if you are only releasing based on the supersedence column and only releasing patches that have not superseded patches or the latest versions of superseded patches, none of the "needed" superseded patches roll out. UGH. So for now, I'm meticulously going through and approving any patch that's "needed" even if it has been superseded. Thanks for your advice. I'm sure once I get to the actual automation piece of this (automating the install of patches on a schedule), I'll have more questions.
-Bo
