Windows-noob.com has a great article on how to achieve this and get a better understanding of the whole process: https://goo.gl/XiKKOx
HTH 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 Kevin Johnston Sent: 12 January 2016 14:40 To: '[email protected]' Subject: [mssms] SCCM Patching - rebuild? A few years ago a consultant who was helping us setup configmgr created 1 ADR for patching. This ADR points to a pilot collection of a few servers and workstations. Every patch Tuesday this ADR kicks off and those pilot machines are patched. We do this for testing. This deployment creates a new SUG each time and is only 1 Deployment package. We then were told during our patching weekend to go into our SUGs, find the date that these were applied, and then deploy them to either our production workstation or server collection. Yes we have no maintenance windows or anything, I manually do it, as well as all the rebooting. Every update is in this 1 deployment package which I know is a big no-no, so I am trying to fix this and get myself on track to have a smarter patching system. When we build out a new DP we have to copy this monstrous 40+ gig update file, which is painful to say the least! So after all that my question is: If I create a new ADR that is monthly (so I am breaking up the chunks) if the updates are already on the DP's will it just use those, or will I have to remove all 40gigs on each DP and then redistribute those files in the new ADR? Basically I am trying to start new without actually removing everything (if I can avoid it). I want to have this cleaned up best I can before upgrading to 1115. KEVIN JOHNSTON 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
