Client Management Suite

 View Only
Expand all | Collapse all

Replication of Changes to Software Detection Rules and Applicability rules

  • 1.  Replication of Changes to Software Detection Rules and Applicability rules

    Posted Apr 16, 2015 09:31 AM

    I've got a hierarchy/replicaiton quirk that I'm trying to learn more about.  Imagine the following:

    You've got a software package with detection and applicability rules.  This package is being delivered by a Managed Software Delivery.  The package, rules, MSD, and associated targets are all happily replicating to child SMPs.

    Then I come in and decide to modify the applicability rules on the parent.  I save the changes, schedule a complete replication to a child server (because there's no simple way that I know of to just replicate software packages and associated info to child servers).  The replication completes just fine.  I then go to a targeted agent, do an update, and... no change to the applicability rule.  I've tried policy updates, delta resource membership updates, running ns.package_refresh, etc.  In my experience, if I let it sit long enough (which is too long for my patience most of the time), the applicability rule will update eventually.

    So, what processes do I need to kick off manually so I can quickly replicate changes to detection/applicability rules to my child NSs and have their agents "see" the change?

    -Prep



  • 2.  RE: Replication of Changes to Software Detection Rules and Applicability rules

    Posted Apr 23, 2015 10:13 AM

    Hi,

    To get changed applicability or detection rules faster, please use new rule for detection or applicability instead changing the existing one.

    Also please use differential replication (it's faster and enough to replicate detection and applicability rules) 

    After rule is changed on Notificaton Server, client will receive it after ~4min automatically, not by policy update (by policy update will be received only new rules). 

    Regards,
    Dmitri