CLOUD SOLUTIONS

Identify which GravityZone module is causing an incompatibility issue

When there is an incompatibility on endpoint between an application and a certain GravityZone module enabled in the Bitdefender security agent follow the next steps.

Issue

Sometimes, the Bitdefender security agent may be incompatible with different applications running on the endpoint due to certain modules enabled from the GravityZone console. This case except the situations where false positive detection returns messages in the Bitdefender agent interface.

Solution

To properly identify which module is causing this issue, follow these steps:

  1. In the GravityZone policy settings, disable one module at a time.

    Example: Advanced Threat Control disabled in policy

    15678_1.png
  2. Check if the issue reproduces with that module disabled.

    • If it does not reproduces anymore, enable the module in the policy and configure an exclusion for the application in the exclusions section of the identified module.

    • If the issue persists, proceed and disable from the policy one more module, until you find the module responsible.

    • If the issue persists with all the modules disabled from policy, uninstall one module at a time using the Reconfigure Client task. For details, refer to Use Reconfigure Client task to install or uninstall endpoint modules.Use Reconfigure Client task to install or uninstall endpoint modules

    • Once you identify the module, contact Bitdefender Enterprise Support Team.