I've run a similar set up in a non-prod environment and it works well. There's no need to separate out OS types as the endpoint will determine what SU is required. Create an ADR that is then pointed to a new Deployment Package every 12 months to avoid the limit.
I like to keep things as simple as possible but environments scenarios may not cater for this simplicity. On Tue, Oct 21, 2014 at 10:38 AM, sccmfun <[email protected]> wrote: > How do you guys structure your monthly updates? > > > > I’ve created the following ADR’s that download the patches for my OS’es, > which include all the updates from way back when to now. > > > > Win7 – deployed to Win7 Collection > > Windows 2008 – deployed to Win 2008 Collection > > Windows 2012 – deployed to all Win 2012 collection > > All patches / All OS’es (used for overall compliance reporting but not > deployed so I don’t have the 1000 update limit) > > > > I end up with 4 deployments but am struggling the best way to do ongoing > monthly patching. Should I create a 5th ADR called monthly and just add > all patches for all 3 OS’es into that SUG and target one collection that > has all my OS’es in it (All OS collection) ? How do others do it on a > monthly schedule? > > > > I also have all my machines in maintenance windows and used that to > “trigger” the actual deployment time on the machines. > > > > Thanks > >
