We create new ADR SUGs for different platforms each month with an automatic deployment to our test systems. After that testing, we change the deployments to a Pilot collection for further validation. Once complete, we change the current month's updates' membership to a full year SUG that goes out to production and update those deployments' schedules accordingly. We then delete the now empty ADR SUGs and deployments.
Still a lot of work for updates but at least we don't need to create lists and download manually and the expired updates get removed automatically, so the tasks that took the most time are happily eliminated! Cheers, Russell ________________________________________ From: listsadmin@lists.myitforum.com <listsadmin@lists.myitforum.com> on behalf of Schwan, Phil <psch...@projectleadership.net> Sent: Friday, April 15, 2016 9:29 AM To: ms...@lists.myitforum.com Subject: [mssms] RE: Monthly ADRs for patching Do you just delete the deployments at the end of that month's cycle and then recreate them each month? -Phil -----Original Message----- From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Marcum, John Sent: Friday, April 15, 2016 12:13 PM To: ms...@lists.myitforum.com Subject: [mssms] RE: Monthly ADRs for patching I don't even create new SUG's, I just reuse the old one. -----Original Message----- From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Schwan, Phil Sent: Friday, April 15, 2016 8:04 AM To: ms...@lists.myitforum.com Subject: [mssms] RE: Monthly ADRs for patching Quick terminology clarification: ADRs do not get created, SUGs do. The ADR is creating a SUG when it runs that is named the same as the ADR plus a time stamp, and those SUGs are what get deployed. Just want to clarify because I've actually had customers who literally did create a new ADR on a monthly basis :) Your best bet is to modify the existing ADR and change the evaluation cycle to occur monthly on the second Tuesday at 3:00pm*, and change the Date Released or Revised to last 28 days. Going forward, that will create one new SUG once a month on Patch Tuesday that should include the PT updates as well as anything out-of-band that was released in the interim. *Note - this Evaluation Schedule assumes your Software Update Point is configured to run at a time when it will see the newly released Patch Tuesday updates. You may need to adjust accordingly. _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Microsoft VTSP (b-phs...@microsoft.com) Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 -----Original Message----- From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Kevin Johnston Sent: Friday, April 15, 2016 7:22 AM To: 'ms...@lists.myitforum.com' <ms...@lists.myitforum.com> Subject: [mssms] Monthly ADRs for patching We have an ADR that was created by a consultant a few years back and for a long time I just dealt with it, and now I want to clean it up. It is as follows: Date Released or Revised Last 1 week (7 days) Product (this includes server OS, Office, Windows OS, runtimes, SQL Server, defender, Silverlight, etc...) Title -Embedded OR -Itanium Update Classification - Critical Updates OR Security Updates OR Updates Evaluation Cycle Occurs every 1 week on Tuesday effective 6/21/2013 3:00PM The issue I have with this is every "Patch Month" I have about 3 ADRs that are created... So I have to deploy these 3 ADRs to the same Patching collections every month. Is there any way to only have only 1 ADR get created per month, or maybe combine them if they happen to be the same month? Or maybe I should manually add them all together? I realize that patches are not always released on Patch Tuesday, but it just seems like a lot of extra work to have to deploy 3 ADRs for 1 month to 7 collections 3 times. We always deploy our patches to production 1 month behind, unless there is a critical must have patch. And current month patches get deployed to a few staging servers and workstations to ensure everything works. KEVIN JOHNSTON ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
