Steps to follow when Symantec Technical Support has requested to enable "VPdebug logging" on a Symantec Endpoint Protection client.
VPdebug logging can be enabled either from the Symantec Endpoint Protection GUI, or by adding an entry to the Windows Registry. The "VPdebug.log" file will be created in
\ProgramData\Symantec\Symantec Endpoint Protection\<version_number>\Data\Logs by default
To enable "VPdebug logging" on a Symantec Endpoint Protection client from the GUI, follow the below steps:
To enable "VPdebug logging" on a Symantec Endpoint Protection client by adding an entry to the Windows Registry, follow the below steps:
NOTE:
On 64 bit systems, the correct key is HKEY_LOCAL_MACHINE\SOFTWARE\WoW6432Node\Symantec\Symantec Endpoint Protection\AV\ProductControl.
If Tamper Protection is enabled, you will need to first disable Tamper Protection to make the registry changes.
To enable "VPdebug logging" on a Symantec Endpoint Protection for Linux.
For SEP client version 14.3 RU1 and later:
Stop SEP services
/usr/lib/symantec/stop.sh
Edit both these files:
/opt/Symantec/sdcssagent/AMD/system/AntiMalware.ini.1
/opt/Symantec/sdcssagent/AMD/system/AntiMalware.ini
In each of these files change the line to:
amdmanagement.antimalware.trace.level=trace
Restart the SEP services
/usr/lib/symantec/start.sh
The log files will be in /var/log/sdcsslog/amdlog/sisamd_0.log.
Note: By default, the AMD logging level is info. You can change the logging level to trace, to warning, or to error.
For SEP client version 14.3 MP1 and earlier:
Use the following command to enable vpdebug logging:
# ./symcfg add --key '\Symantec Endpoint Protection\AV\ProductControl\' --value 'Debug' --data 'ALL' --type REG_SZ
Repeat the same command with no value for data to turn it OFF:
# ./symcfg add --key '\Symantec Endpoint Protection\AV\ProductControl\' --value 'Debug' --data '' --type REG_SZ