that's not a recommended limit, it's a hard limit, the recommendation would be to NOT have so many updates in a software update package, see this from Jason githens
*Why do I need to group them? I understand the limit has been raised to 1,000 per deployment, but why can’t I just create one update-group deployment of all previously released updates? I guess I don’t understand the need for a limit.* Yes, the update limit has been increased to 1,000, and this is a hard limit – unlike Configuration Manager 2007 where it was a documented limit (of 500 updates). This limit exists for good reason — it is set to mitigate performance degradation, both server-side (for summarizing such large deployments, and for rendering reports), as well as on client-side, for clients processing large policy-bodies containing more than 1,000 updates. As for the server-side piece, there is a tremendous amount of SQL processing required to correlate deployment and compliance states across all updates in a group, relative to all clients in your environment. This limit is to help keep that summarization processing under control, hence the requirement of creating deployed update groups that do not exceed this limit. Also, you really want to avoid frequently modifying deployed update-groups by adding/removing updates to them, as this causes a lot of overhead client-side with policy processing, and server-side with SQL processing. http://blogs.technet.com/b/server-cloud/archive/2012/02/20/managing-software-updates-in-configuration-manager-2012.aspx On Mon, Mar 16, 2015 at 2:00 PM, Paul Winstanley <[email protected]> wrote: > James > It's 1000 > > > > On 16 Mar 2015, at 12:52, Beardsley, James <[email protected]> > wrote: > > What is the recommended limit on Software Update Groups in terms of how > many updates can be added before I should create a new one? I think it was > 10,000 but can someone clarify? > > > > Thanks! > > > > *James Beardsley |* Firm Technology Group > > Dixon Hughes Goodman LLP > > > > <image001.png> <http://www.dhgllp.com/> > > > ------------------------------ > > *Confidentiality Notice:* This e-mail is intended only for the addressee > named above. It contains information that is privileged, confidential or > otherwise protected from use and disclosure. If you are not the intended > recipient, you are hereby notified that any review, disclosure, copying, or > dissemination of this transmission, or taking of any action in reliance on > its contents, or other use is strictly prohibited. If you have received > this transmission in error, please reply to the sender listed above > immediately and permanently delete this message from your inbox. Thank you > for your cooperation. > > >
