GravityZone Troubleshoot - PRODUCT GENERAL ISSUES (high verbosity Logging) GENERIC

GravityZone Troubleshoot - PRODUCT GENERAL ISSUES (high verbosity Logging) GENERIC

1. Open a CMD prompt with administrative privileges and type (or copy&paste) the following commands:

•      cd C:\Program Files\Bitdefender\Endpoint Security
•      product.console.exe /c Support.StartSession scenario=generic
•      Leave the logging enabled for 20-30 minutes
•      product.console.exe /c Support.EndSession

You may upload the logs here: https://upload.bitdefender.net/

    • Related Articles

    • GravityZone Troubleshoot - Advanced EDR logs from the endpoint

      Please provide a new set of Advanced EDR logs from the endpoint, with reproduction of the behavior, after the sources and ports and whitelisted, for analysis: - Open CMD with Administrator privileges and run: - cd C:\Program ...

    • GravityZone Troubleshoot - Verbose Device Control Logs

      To properly investigate the issue they require a set of Verbose Device Control Logs gathered while the issue is being reproduced (insert devices and remove them a few times) as well as the device names / IDs for the devices that are allowed in spite ...

    • Completed - Gravityzone Product Implementation (Cloud)

      Hello Sir, Thank you for your valuable time. Today we have completed the Bitdefender GravityZone (cloud) implementation successfully, we performed the below activity in the session: Activation done. Created a new package and guided how to send the ...

    • GravityZone Troubleshooting - Advanced CONTENT CONTROL / FIREWALL logs from the endpoint

      Please provide a new set of Advanced Content control logs from the endpoint, with reproduction of the behavior, after the blocked from Web access control, for analysis: - Open CMD with Administrator privileges and run:- cd C:\Program ...

    • SIEM Intergration with Bitdefender GravityZone

      Requirements Access to Bitdefender GravityZone Console. Ubuntu 24.04 LTS server with the following hardware configuration: Must be on the same network as the SIEM (On-Premises) or able to communicate with SIEM (Cloud). 2 CPU, 4 GB RAM, 80 GB HDD. ...