Here are some basic instructions on how to gather console, client (target) side logs, and agent logs for Protect 8.x and 9.x. These should work for most console and agent type issues.
Protect 9.X console logging:
1. Please open the Protect GUI and then go to Tools > Options > Logging and change logging to “All” for both user interface and services.
a. If you are unable to set logging via the GUI see this doc: http://community.shavlik.com/docs/DOC-22938
2. Close the Protect GUI.
3. Stop the Shavlik Protect Console Service.
4. Delete all the logs from
a. Windows 7, 8, 2008, 2012 & Vista: C:\ProgramData\LANDesk\Shavlik Protect\Logs
b. Earlier OS’s: C:\Documents and Settings\All Users\Application Data\LANDesk\Shavlik Protect\Logs
5. Start the console service and open the Protect GUI.
6. Attempt to reproduce the issue. Please document steps to reproduce.
a. Collect the logs from the Logs folder mentioned earlier in step 4 (please zip if possible)
b. [Deployment issues only] On the target system please zip and send a copy of the entire C:\Windows\Propatches folder and its contents (you can leave out the Patches sub-folder).
7. Zip and send all the logs.
Protect 9.x agent logging:
1. Open the agent policy assigned to the machine we are gathering logs from.
2. Change the logging level to ‘All’ and Save and update Agents. Choose to update agents if prompted.
3. Go to the target machine, close the agent GUI and stop the services:
o The services start with Shavlik or ST.
4. Delete all the logs from:
o Vista & Later: C:\ProgramData\LANDesk\Shavlik Protect\Logs
o Earlier OS’s: C:\Documents and Settings\All Users\Application Data\ LANDesk\Shavlik Protect\Logs
5. Start services.
6. Attempt to reproduce the issue. Please note the steps to reproduce.
7. Take applicable screenshots.
8. Zip and send all the logs and screenshots. (from the previous specified folders above)
Deployment Logs (All current supported versions)
(For agentless deployment)
It may be best to enable target side verbose logging before obtaining these logs. See the following document on how to do so:
http://community.shavlik.com/docs/DOC-23048
- On the machine you are deploying to navigate to C:\Windows\ProPatches
- Locate the CL5.log, dplyevts.log, and Safereboot.log and copy to a new folder on the desktop.
- Navigate to C:\Windows\ProPatches\Scheduler.
- Locate the Scheduler.log and add it to the folder created in step 2 so all logs are together.
- Zip and send all the logs.
Protect 8.X console logging:
1. Please open the Protect GUI and then go to Tools > Options > Logging and change logging to “All” for both user interface and services.
a. If you are unable to enable logging via the GUI see doc: http://community.shavlik.com/docs/DOC-22938
2. Close the Protect GUI.
3. Stop all of the services:
a. For Protect 8.X, the service name starts with VMware vCenter Protect.
4. Delete all the logs from:
a. Vista & Later: C:\ProgramData\Shavlik Technologies\Logs
b. Earlier OS’s: C:\Documents and Settings\All Users\Application Data\Shavlik Technologies\Logs
5. Start services and open the Protect GUI.
6. Attempt to reproduce the issue. (please note how to reproduce)
7. Take applicable screenshots.
8. Zip and send all the logs and screenshots. (from the previous specified folders above)
Protect 8.X agent logging:
1. Open your agent policy assigned to the machine we are gather logs from.
2. Change the logging level to ‘All’ and Save and update Agents.
3. Go to the target machine, close the agent GUI and stop the services:
o For Protect 8.X, the service name starts with VMware vCenter Protect.
4. Delete all the logs from:
o Vista & Later: C:\ProgramData\Shavlik Technologies\Logs
o Earlier OS’s: C:\Documents and Settings\All Users\Application Data\Shavlik Technologies\Logs
5. Start services.
6. Attempt to reproduce the issue. Please note the steps to reproduce.
7. Take applicable screenshots.
8. Zip and send all the logs and screenshots. (from the previous specified folders above
Additional Logging for Threat Protection/Antivirus Issues:
There is additional logging that can be obtained for Threat Protection/Antivirus related issues, such as detection of false positives. See the following document for the steps to obtain this addtional logging: