I like it. On Sun, Mar 19, 2017 at 11:03 AM, Adam Juelich <acjuel...@gmail.com> wrote:
> Thinking about this more, it may be better to utilize the Application > Method. That way I can chain the Dependencies in the proper order. > Otherwise, I'd have to craft the SUG's accordingly, deploy them and wait > for compliance, and then deploy the next one. > > > 1. .NET 4.6.2 > 2. WMF 5.1 > 3. WUA Update > 4. Servicing Stack > 5. Convenience Roll-up > 6. March Rollup > 7. Start ADR > > > On Fri, Mar 17, 2017 at 10:44 AM, Adam Juelich <acjuel...@gmail.com> > wrote: > >> So, I created a SUG with the Servicing Stack Updates (Which was >> superseded with a newer one) and the July WUA. I then created another SUG >> with the Convenience Rollup. Can I deploy both of these at the same time >> or should I do the first one, once I hit good compliance then deploy the >> Rollup? >> >> On Fri, Mar 17, 2017 at 8:27 AM, Adam Juelich <acjuel...@gmail.com> >> wrote: >> >>> Are your classifications correct in your SUP settings? >>> >>> On Fri, Mar 17, 2017 at 1:15 AM, Shane Alexander < >>> shane_alexan...@hotmail.com> wrote: >>> >>>> Update regarding importing Convenience Rollup Update KB3125574 into >>>> WSUS, and then sync'ing expecting to see it in ConfigMgr SUP. >>>> >>>> >>>> It imports OK to WSUS, but doesn't seem to sync across into ConfigMgr >>>> SUP. >>>> >>>> >>>> Was expecting it would just like KB2775511, as per below link. >>>> >>>> https://blogs.technet.microsoft.com/michaelgriswold/2013/03/ >>>> 13/kb2775511-deployment-for-the-sccm-admin/ >>>> >>>> >>>> However have just done this for KB3125574, but cannot see it. >>>> >>>> Did same steps for KB2775511, which I can see. >>>> >>>> >>>> Shane >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------ >>>> *From:* listsad...@lists.myitforum.com <listsad...@lists.myitforum.com> >>>> on behalf of Shane Alexander <shane_alexan...@hotmail.com> >>>> *Sent:* Friday, 17 March 2017 10:51 AM >>>> >>>> *To:* mssms@lists.myitforum.com >>>> *Subject:* Re: [mssms] Catching up on patching >>>> >>>> >>>> Agree getting WUA updated would be a good place to start, then you have >>>> a known baseline for scanning against. >>>> >>>> >>>> Thing is, latest unique individual update for the WUA on W7 SP1 is >>>> KB3138612 from March 2016. >>>> >>>> The Convenience Rollup Update actually has a newer WUA in it, and after >>>> that WUA, e.g. from June 2016 onwards, the WUA is updated as it is included >>>> in the Monthly Update Rollups >>>> >>>> Versions below. >>>> >>>> http://www.potentengineer.com/windows-update-agent-build-num >>>> bers-for-windows-7/ >>>> >>>> >>>> Agree that installing Convenience Rollup Update KB3125574 on all >>>> existing W7 SP1's would create a good known baseline and then you can patch >>>> from there onwards, like with IE, .Net, & Monthly Rollups. >>>> >>>> Something to note is the "Known issues" listed in KB3125574, you can >>>> stop most of the issues before installing KB3125574. >>>> >>>> >>>> Regarding installing KB3125574 as an Update (through Software Updates >>>> vs as an Apllication), you'd have to import KB3125574 directly into your >>>> top WSUS (yes WSUS), and ensure you are sync'ing for the "Updates" >>>> Classification, and ensure a full sync is done. >>>> >>>> You'll also then have many individual updates appearing as Superseded >>>> (a good thing). >>>> >>>> >>>> >>>> Shane >>>> >>>> >>>> >>>> >>>> ------------------------------ >>>> *From:* listsad...@lists.myitforum.com <listsad...@lists.myitforum.com> >>>> on behalf of Sherry Kissinger <sherrylkissin...@gmail.com> >>>> *Sent:* Friday, 17 March 2017 4:36 AM >>>> *To:* mssms@lists.myitforum.com >>>> *Subject:* Re: [mssms] Catching up on patching >>>> >>>> Todd has a very good point: windows update agent--if they haven't been >>>> patching, they possibly haven't been paying attention to their windows >>>> update agent version. There are some updates which just don't install or >>>> detect correctly unless you have the latest WUA. So research what versions >>>> of that you have out there, and get that to the latest version; otherwise >>>> you might be chasing patching installation issues that end up being "latest >>>> wua required" >>>> >>>> On Thu, Mar 16, 2017 at 10:45 AM, Adam Juelich <acjuel...@gmail.com> >>>> wrote: >>>> >>>>> Nope. Just me, myself, and I. >>>>> >>>>> On Thu, Mar 16, 2017 at 10:36 AM, Todd Hemsell <hems...@gmail.com> >>>>> wrote: >>>>> >>>>>> I thought you were with tanium? >>>>>> >>>>>> >>>>>> On Thu, Mar 16, 2017 at 9:17 AM, Daniel Ratliff <dratl...@humana.com> >>>>>> wrote: >>>>>> >>>>>>> Why deploy the convenience rollup as an Application? Why not an >>>>>>> update? >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Daniel Ratliff* >>>>>>> >>>>>>> >>>>>>> >>>>>>> *From:* listsad...@lists.myitforum.com [mailto: >>>>>>> listsad...@lists.myitforum.com] *On Behalf Of *Adam Juelich >>>>>>> *Sent:* Thursday, March 16, 2017 10:07 AM >>>>>>> *To:* mssms@lists.myitforum.com; Patch Management Mailing List < >>>>>>> patchmanagem...@listserv.patchmanagement.org> >>>>>>> *Subject:* [mssms] Catching up on patching >>>>>>> >>>>>>> >>>>>>> >>>>>>> Hello Everyone, >>>>>>> >>>>>>> >>>>>>> >>>>>>> A hypothetical scenario for you that I am actually facing, assuming >>>>>>> Windows 7 SP1: >>>>>>> >>>>>>> >>>>>>> >>>>>>> What would you do if you came into an environment where patching was >>>>>>> sparse and erratic over the past few years and documentation and >>>>>>> historical >>>>>>> knowledge was uncertain? >>>>>>> >>>>>>> >>>>>>> >>>>>>> I was thinking about deploying the Convenience Roll-up as an >>>>>>> Application in ConfigMgr. After that is complete create a Software >>>>>>> Update >>>>>>> Group for the roll-ups since then. After that, create the monthly ADRs >>>>>>> to >>>>>>> stay compliant. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Does that sound like a good plan or would you guys attack it in a >>>>>>> different manner? >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> >>>>>>> >>>>>>> The information transmitted is intended only for the person or >>>>>>> entity to which it is addressed >>>>>>> and may contain CONFIDENTIAL material. If you receive this >>>>>>> material/information in error, >>>>>>> please contact the sender and delete or destroy the >>>>>>> material/information. >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thank you, >>>> >>>> Sherry Kissinger >>>> >>>> My Parameters: Standardize. Simplify. Automate >>>> Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry >>>> -kissinger, http://www.smguru.org >>>> >>>> >>>> >>>> >>> >>> >> >> > >
