You can use powershell DSC, it would be good fit for this type scenario.
On Thu, Mar 17, 2016, 8:13 AM Daniel Ratliff <[email protected]> wrote: > Possible? Yeah probably, using a UNC path or some network share. Would I > do it? No. For scenarios like this we have CIs that mark non-compliant > machines as such, then create a collection with a package targeted to it. > Works pretty well. > > > > *Daniel Ratliff* > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Marcum, John > *Sent:* Thursday, March 17, 2016 11:09 AM > *To:* [email protected] > *Subject:* [mssms] CI to Remediate Missing File > > > > Isn’t it possible to have a CI remediate a missing file without having to > deploy the missing file from a package? I can’t seem to figure out where to > attach the file to the CI. Any examples of how to do this would be > appreciated. > > > > > > > > > > > * ------------------------------ * > > * John Marcum* > > MCITP, MCTS, MCSA > * Desktop Architect* > > * Bradley Arant Boult Cummings LLP* > * ------------------------------ * > > [image: MVP] <https://mvp.microsoft.com/en-us/overview> > > [image: MMS] <http://mmsmoa.com/> > > > > > ------------------------------ > > > 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. > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > >
