Confusion as how to handle monthly software updates

Question

I'm struggling to wrap my head around the proper way of handling software update delivery through Configuration Manager 2012 R2.  I'm hoping you guys and gals and
can set me straight.  Anyway, here is my question.
I have a ADR configured that grabs all
updates released or revised in the past 1 month.  For the month of October the ADR grabbed all updates released in October, however, it also grabbed updates that were revised in October but were originally released in September.  So, now the same
update exists in my software update groups (and same deployment package) for both September and October.  I've also had an instance in August where some updates were revised that were originally released in 2011.  In that case, I had updates existing
in my August 2014 software group as well as my 2011 group (and two different deployment packages).  What is the proper way of handling this scenario?  Does it hurt that these updates exist in multiple groups?  Should I perform some type of cleanup?
 Please help me understand this.  Thanks :)

Answer 1

"So, now the same update exists in my software update groups (and same deployment package) for both September and October."
So? (Sorry, not trying to be harsh, just don't know how else to say it.)
There's nothing wrong with having updates in multiple groups. If a client already has it installed, then it won't do anything for that update no different for any other non-applicable update.
As for the update package, same thing. The update will only be downloaded once (if the ADRs point to the same update package) and will only de distributed to your DPs once regardless of update package.
Although keep in mind revisions are usually accompanied by new binaries so can be thought of as new and distinct updates which means what you have happening is exactly what should happen.
So, no, it doesn't hurt anything at all and no there's nothing special for you to do.
Jason | http://blog.configmgrftw.com | @jasonsandys
Hey Jason, thanks for the reply.  You didn't sound harsh at all.  That's exactly what I wanted to hear.  Introducing SCCM into a network when I've never used SCCM has been a learning experience.  The software update model is different
than what I'm used to with WSUS.  I was afraid I may have organized things wrong and didn't know if duplicate updates were normal behavior.  Thanks for setting me straight.  I always worry too much when it comes to these things :)