We structure ours according to groups of servers and their function rather than by OS as this corresponds better with the time and date of your maintenance window. For example a group of lab computers may have different OS's in that group but you may want to patch them all at the same time.
We use the following search criteria for getting required updates with the ADR (from www.windows-noob.com guides): [cid:[email protected]] We then use maintenance windows to ensure the patches only deploy when we need them to. Hope this helps. Andrew Hurst Systems Engineer Mourant Ozannes BVI | CAYMAN ISLANDS | GUERNSEY | HONG KONG | JERSEY | LONDON D +44 1534 676 772 | T +44 1534 676 000 | F +44 1534 676 333 mourantozannes.com<http://www.mourantozannes.com/> From: [email protected] [mailto:[email protected]] On Behalf Of sccmfun Sent: 21 October 2014 10:38 To: [email protected] Subject: [mssms] Software Updates - ADR 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 The information contained in this e-mail (and any attachments) is strictly confidential and may also be legally privileged. If you are not the intended recipient of this e-mail please do not read, print, re-transmit, store, or act in reliance on it or any attachments. Instead, please notify the sender by return e-mail and then immediately permanently delete it from your system. We are not liable for any views or opinions expressed by the sender where this is a non-business e-mail. We may monitor email communications in accordance with applicable law and regulations. Mourant Ozannes is a Jersey partnership. A list of partners' names is open to inspection at 22 Grenville Street, St Helier, Jersey JE4 8PX, Channel Islands. Additional terms and conditions and information on other Mourant Ozannes network members are available on our website: www.mourantozannes.com
