With the below criteria, you *will* miss updates. Specifically, any updates released before the last month that are now required for whatever reason like a new system is brought online, an admin uninstalls an update, etc. I highly recommend never using both the date and required criteria together because of this. Use one or the other, not both.
I generally don't like the required criteria at all because it is reactive and assumes *all* clients have actually reported in by the time the ADR runs. This of course isn't true for OSD and so breaks down there also. J From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Beardsley, James Sent: Friday, April 15, 2016 1:10 PM To: ms...@lists.myitforum.com Subject: RE: [mssms] Software Updates Sure, here are the server and workstation ADR rules. I wait to run them until Wed evening to give the machines time to run a scan cycle against the new updates released 24 hours earlier and that way the ADR only downloads "Required > 0" into the packages. Then every three months, I set a reminder for myself to go into each ADR and change the download settings from putting new updates into an existing package to "Create a new deployment package" for the new quarter. Once the ADR is run and the new quarter package is populated, I change it back to adding to an existing package (the new one) until that quarter is complete and you do it all over again. This process has worked great for me for the past 2 years or so. [cid:image002.png@01D1971E.43314310] From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Linkey, Mike Sent: Friday, April 15, 2016 11:49 AM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: RE: [mssms] Software Updates I like this idea. Would you be willing to share how you have your ADR's setup? From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Beardsley, James Sent: Wednesday, April 13, 2016 4:18 PM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: RE: [mssms] Software Updates I have ADR's that every month creates a new SUG for PC's and one for servers that contains OS and Office and anything else that's required. Then I do a new package for each quarter. After 4-5 months, I'll roll all of the older SUGs into a yearly group so they look like this. Actually, its about time to create a 2015 package for workstations and servers and consolidate these. [cid:image003.png@01D1971E.43314310] From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Augustine, Greg Sent: Tuesday, April 12, 2016 3:59 PM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: [mssms] Software Updates How do you all handle software updates? Do you all break them apart by OS? Do you create separate packages for Office? Do you create a massive package with everything in it? Just curious. Greg Augustine Office of Administration Information Technology Services Division - State Data Center (573)-751-4714 ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation. CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents accompanying such) may contain confidential information. Such information is intended only for the use of the individual or entity named above. If you are not the named or intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of such information is strictly prohibited. If you have received this email in error, please notify the sender and then delete the email. Thank you for your cooperation. ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
