hadi Posted October 19, 2014 Report post Posted October 19, 2014 I'm configuring some Automatic deployment rules in SCCM2012R2 .After specifying product updates ,the wizard noticed that just first 1000 update will deployed .So I divided updates in two rules .now I don't have any problem .But the question is that How about the future,after a while maybe two month ,less or more, the number of Updates will get increased,and will become more than 1000 items ,because I've selected option "Add to an existing Software update Group".Should I change it to option "Create New software Update Group" during Automatic deployment wizard ?Or there are some other solutions. Quote Share this post Link to post Share on other sites More sharing options...
Iroqouiz Posted October 24, 2014 Report post Posted October 24, 2014 I'm configuring some Automatic deployment rules in SCCM2012R2 .After specifying product updates ,the wizard noticed that just first 1000 update will deployed .So I divided updates in two rules .now I don't have any problem .But the question is that How about the future,after a while maybe two month ,less or more, the number of Updates will get increased,and will become more than 1000 items ,because I've selected option "Add to an existing Software update Group".Should I change it to option "Create New software Update Group" during Automatic deployment wizard ?Or there are some other solutions. Why are you deploying so many updates? How many products do you have ticked? You shouldn't sync, download and deploy updates that are not required by your clients, it just puts your SQL server under unnecessary load, and it will fragment the SQL DB much much faster. If you have many products which makes the ADRs sync many updates each Patch Tuesday you should create a new software update group each time. I would then make one ADR for each product. Quote Share this post Link to post Share on other sites More sharing options...
