jeremytbjones Posted November 12, 2012 Report post Posted November 12, 2012 I am testing patch deployment with SCCM 2012 in hopes to replace our existing WSUS environment. I have configured a Windows 7 ADR which is working perfectly, with one exception. I configured a 14 day deadline for patch installs on the ADR. The deadline start date seems to be the creation of the ADR and not 14 days from when it runs (it is configured to run weekely on wednesdays). So it works great for the initial roll out but after 2 weeks any new clients added to the collection to which the ADR is targeted will immediately start installing the patches since the 2 week deadline has already passed (from creation of the deadline). Is there anyway to make it 2 weeks from either its weekely run cycle or 2 weeks from when a client first recieves the ADR setting? Quote Share this post Link to post Share on other sites More sharing options...
jazzlara Posted January 13, 2013 Report post Posted January 13, 2013 I too would like to know how to handle this. I suppose you can go in each month after the deadline and just update it and run the rule again. Is that an options? I ended up saying As Soon as Possible and creating a Maintenance Schedule. Hardly a perfect solution. What is best practice for either Creating new Packages each month or Add to Existing? If each Update Group is seperated by OS, might it be possible to only create new Packages say every 6 months or so? Thanks! Quote Share this post Link to post Share on other sites More sharing options...
jazzlara Posted January 17, 2013 Report post Posted January 17, 2013 Bump Quote Share this post Link to post Share on other sites More sharing options...
