Adding Software Updates to Software Groups After Deployment

Question

Hi all -
I went through and created 3 software update groups (for 2013, 2014, and 2015), and then distributed all three of them to a certain collection (and to all DPs). After that point, I then realized I had forgotten a number of updates for each software
update group. I downloaded the software updates and edited their membership so they would be a part of the existing software groups. When I did that their statuses said they were deployed. However, when I look at content distribution I don't see
anything changing. Almost like the new updates didn't go out to the DPs.
Do you need to redeploy the software update groups after adding new software updates? Or should this automatically distribute the new updates as part of the existing deployments.
Kind of unrelated, and not really part of my main question. Is there a best practice on the maximum number of software updates for a group? My largest group has 632 updates. I realize the dependency on reporting and all that, I am purely speak from a performance
or issues best practice.
Thanks,
--Julius

Answer 1

A software update group and a deployment package are two different things. When you download the updates, you download them to your deployment package. To look at the status of that process you can look at
Content Status node in the console or the distmgr.log
file.
The best-practice maximum number of updates per update group is a 1000, see also:
https://technet.microsoft.com/en-us/library/hh692394.aspx.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude