Hi Sherry, this is pure WSUS - what I’m expecting is intelligence in the scan to say, hey I know, I only need January’s, cause it’s cumulative and has all I need.
HNY btw :) On 13 Jan 2017, at 13:52, Sherry Kissinger <[email protected]<mailto:[email protected]>> wrote: My Guess; and it's just a guess... Superseded <> Expired If you have those superseded updates in your deployment update group, depending upon where in the install chain that particular client chose to install an update, it *might* install November, December, than January. Instead of "January", then "oh, I have November and December already, moving on" Which is what you want to happen. If you want to avoid that, remove the superseded updates from your update group, so only the latest is available. On Fri, Jan 13, 2017 at 5:04 AM, Stuart Watret <[email protected]<mailto:[email protected]>> wrote: I try not to think about patching too much, I’ve been fairly successful. I thought the new patch paradigm was cumulative? I was refreshing a reference image in MDT yesterday, a couple of days after January’s patches were out. The screen cap below shows my client picking up Novembers patches, clearly marked as superseded in the wsus console. Have I got it wrong? Cheers Stuart <unknown.png> -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com<http://www.mofmaster.com/>, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org<http://www.smguru.org/>
