ADR's will always not work like 2 months out of the year unless something has changed since the last time I looked at them.
Typos compliments of Siri Sent from my iOS device > On Apr 15, 2016, at 6:27 AM, Kevin Johnston <kjohns...@halogensoftware.com> > wrote: > > 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.
