I guess that you could build a collection based upon compliance with CI1 and only deploy CI2 to the collection.
Either this or you could create a script to watch for compliance > On 11 Apr 2014, at 08:27, "Julius Roschach" <[email protected]> wrote: > > Dear All, > > If it is poor form to bump old list posts please let me know! > > > Hi Andy, > > Did you make any progress with this problem? I too have a similar scenario. > We have 3 settings that read an XML file for parameters. This XML file often > gets cleared so we have a separate setting that repairs the incorrect file > but the other settings try to read it first. > > Regards, > > Julius > > >> On Sat, Jun 29, 2013 at 11:08 PM, Craig Andrew (OIZ) >> <[email protected]> wrote: >> Hi All, >> >> >> >> Am I correct in thinking I can’t specify the order in which compliance items >> in a baseline in Configmgr 2012 are evaluated? >> >> >> >> I’d like the client to evaluate a certain item first because the remediation >> is pertinent to another item. Maybe I could be clearer, a CI might fail if >> the other CI has not yet be evaluated and remedied. >> >> Do I have to nest baselines on compliance collections? >> >> >> >> Does anyone else handle this? I could wrap both items in one CI but that’s >> not so pretty and I like granularity. >> >> Is it something you can configure with CI relationships? >> >> >> >> Or am I missing the point? It is Saturday after all. >> >> >> >> Thanks >> >> Andy >> > >
