This guide details the methods for retrieving historical logs from a Carbon Black Cloud endpoint. It covers both local collection and remote extraction using Live Response.
Carbon Black Cloud now uses SymDiag. See Download SymDiag v3 to detect product issues
cd "C:\Program Files\Confer"
repcli capture <LocalOutputPath>
-- Example: repcli capture C:\Users\%USERNAME%\DesktopCarbon Black Cloud now uses SymDiag.
mkdir c:\temp\SymDiag
cd c:\temp\SymDiagput c:\temp\SymDiagexecfg SymDiagWin sd-s sd-base C:\temp\SymDiag sd-dest --dir "C:\temp\SymDiag" sd-log logget <filename>.sdz3cd C:\Program Files\Confer
execfg repcli capture c:\temp -- Change to desired writeable location
get c:\temp\psc_sensor.zip -- Change to location specified in previous command
sudo /opt/carbonblack/psc/bin/collectdiags.sh --verbose --debug --output-dir <Destination_Directory>execfg sudo /opt/carbonblack/psc/bin/collectdiags.sh --verbose --debug --output-dir <Destination_Directory>diags_{hostname}_{epoch_time}_{random}.tgzget <Destination_Directory>/diags_{hostname}_{epoch_time}_{random}.tgzsudo /Applications/VMware\ Carbon\ Black\ Cloud/repcli.bundle/Contents/MacOS/repcli capture <Uninstall_Code> <Destination_Directory>execfg sudo "/Applications/VMware Carbon Black Cloud/repcli.bundle/Contents/MacOS/repcli" capture <GlobalDeregistrationCode> <DestinationDirectory>get <Destination_Directory>/confer.zipIf the file does not automatically download using Live Response, this may be due: