Cb Defense: Troubleshooting Performance and Interop Issues with the Sensor
Cb Defense (formerly Confer) - All
This document provides information on how to troubleshoot to performance and Interop Issues with the Sensor for Windows and MAC
If a sensor is installed on a machine and any variety of issues is present, do not uninstall the sensor. Removal of the Sensor de-registers the device and log files are no longer accessible. A performance or interoperability issue may be that a program seems to be taking a long time to open or a program or operation is being delayed or blocked. The best approach when troubleshooting any issues that are directly or indirectly related with the sensor is to enable bypass. Bypass or passive mode or Passthru are synonyms that are used in various places. When a Sensor is in bypass, it runs in the background but does not collect any information or perform any operations.
If an issue occurs where an installation is being blocked, a program seems to be launching or running slowly, or a program does not seem to be behaving properly, the workflow to troubleshoot is:
Log what the user was doing and what time the event occurred. Collect all relevant information about that point in time (i.e. Machine Hostname, software, date and time, etc)
Put the sensor into bypass so the user may continue using the system without any further issues.
Notify Technical Support via a case.
Technical Support will request and collect the log files from the UI for investigation.
Other information may be required during the investigation, but Technical Support will ultimately outline what is required and when the device can resume normal and non-bypassed operation.
To put a machine into Bypass:
From the Enrollment page, click the checkbox in the respective row for that device.
Click Actions - "Enable Bypass"
In the back-end, this request is queued.
When the sensor checks in, the request will be processed and the device will go into bypass.
Verify that the device shows as Bypass-Enabled in the UI in Enrollment