IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

App Control: How to Manage Agent Config

App Control: How to Manage Agent Config

Environment

  • App Control Agent: All Supported Versions
  • App Control Console: All Supported Versions

Objective

How to add, modify, or remove an Agent Configuration property in the Console.

Resolution

Modify Existing: (Recommended when possible)
  1. Log in to the Console and navigate to: https://ServerAddress/agent_config.php
  2. Click Show Filters > Value > contains > relevant Value > Apply
  3. Click View Details (pencil icon) and modify accordingly.

Add New:
  1. Log in to the Console and navigate to: https://ServerAddress/agent_config.php
  2. Click Add Agent Config.
  3. Complete all of the desired fields based on Carbon Black's recommendations.

Additional Notes

  • Warning: It's recommended to work with Support anytime a configuration is added.
  • Agent Configs are case sensitive.
  • The authenticated command dascli configprops filter *VALUE* can be used to confirm the Agent Config has been received. Example:
    cd "C:\Program Files (x86)\Bit9\Parity Agent\"
    dascli password GlobalPassword
    dascli configprops filter *usn_journal*
  • macOS and Linux Agents do not currently support Policy specific configurations.
  • Agent Configs can be applied per-Agent, per-Policy, or Globally (Agents in all Policies).
  • If the Agent receives multiple Agent Configs for the same Property the will be honored as follows:
    • per-Agent is ranked highest and will be honored first.
    • per-Policy is ranked next, and will be honored if no per-Agent Property exists.
    • Global is ranked last, and will be honored only if no per-Agent or per-Policy Property exists.
  • It's recommended to only have one type of exclusion per group of devices to prevent confusion or unintentional overlap.
    Ex: Avoid multiple Agent Configs for the same Value where one is Host ID specific, one is Policy specific, and one is All Hosts.

Related Content


Labels (1)
Tags (2)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎12-19-2018
Views:
3118
Contributors