I'm making a new SUG every month but adding the updates to the same package. I plan to prune this package to keep the number of updates from getting too high.
Ideally, I'd love for one rule to run and add all the updates to this Package and SUG, then push it out to DPs. Then, I'd specify my ADR's to create deployments for this for me to all the various collections with their various different reboot/deadlines etc. On Tue, Mar 18, 2014 at 9:43 AM, Mote, Todd <[email protected]> wrote: > Do you create a new SUG every month or reuse the same one? > > > > I reuse the same SUG, and every month, my ADR cleans it up, puts the new > updates in it, then updates each deployment using that SUG. > > > > Todd > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Stephen Owen > *Sent:* Tuesday, March 18, 2014 8:37 AM > *To:* [email protected] > *Subject:* [mssms] 2012 Updates ADR Question > > > > Hello gents, > > > > I've currently got one ADR in my 2012 environment which is working great > downloading updates based on the rules I've set. The only issue I've > encountered is that it looks like I have to manually update the Deployment > Package once a month, and everything else is done for me. Anyone know how > to get ConfigMgr to update the Package for me? > > > > I'd like to deploy this same Update Group to a number of different > groups of computers, each with different deployment settings. Whats the > best way to do this? If you could point me to some resources, I would > appreciate it. > > > > Thanks, > > > >
