Can share some inside on the code? Are you using built-in SCCM cmdlet or did you build it using WMI?
I know there is copy option in the ADR cmdlet that can be used to update the ADR. Cesar On Oct 28, 2014 9:35 AM, "Wilbers, Scott" <scott_wilb...@ctsinc.biz> wrote: > We have separate SU Group and packages for each month and couldn’t get > the ADR process to handle this out of the box. I wrote a PowerShell script > to handle all of it. It will create a new package and modify the ADR to > use the new package, and then invoke the ADR. I also wanted more control > over which updates get flagged when the ADR runs, so the script will also > modify the search criteria each time it runs. > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *s kissel > *Sent:* Monday, October 27, 2014 3:27 PM > *To:* mssms@lists.myitforum.com > *Subject:* [mssms] ADR and Dynamic Deployment Packages > > > > Hi - Suppose you had an ADR that created a new SU Group every month. You > can set the ADR up to download the updates into a new SU package, or a > previously created one. However, suppose you wanted the ADR to create a new > SU package each month, using variables such as %Month% or something along > those lines. Is this even possible? > > > > The main driver for this is that with 160 DPs spread worldwide and some > with very, very low bandwidth available, it's become increasingly difficult > to push 6 and 9 GB packages across WAN links repeatedly, and even more so > as a few new DPs are stood up every month. > > > > Regards, > > -S > > > > > ************************************************************************************************** > Note: > The information contained in this message may be privileged and > confidential and > protected from disclosure. If the reader of this message is not the > intended > recipient, or an employee or agent responsible for delivering this message > to > the intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. If > you > have received this communication in error, please notify us immediately > by > replying to the message and deleting it from your computer. > > ************************************************************************************************** > >
