04.03.2013 Views

OfficeScan 10.6 Administrator's Guide - Trend Micro™ Online Help

OfficeScan 10.6 Administrator's Guide - Trend Micro™ Online Help

OfficeScan 10.6 Administrator's Guide - Trend Micro™ Online Help

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Trend</strong> Micro <strong>OfficeScan</strong> <strong>10.6</strong> Administrator’s <strong>Guide</strong><br />

<strong>OfficeScan</strong> Client Logs<br />

17-16<br />

Use client logs (such as debug logs) to troubleshoot client issues.<br />

WARNING! Debug logs may affect client performance and consume a large amount of<br />

disk space. Enable debug logging only when necessary and promptly disable<br />

it if you no longer need debug data. Remove the log file if the file size<br />

becomes huge.<br />

Client Debug Logs using LogServer.exe<br />

To enable debug logging for the <strong>OfficeScan</strong> client:<br />

1. Create a file named ofcdebug.ini with the following content:<br />

[Debug]<br />

Debuglog=C:\ofcdebug.log<br />

debuglevel=9<br />

debugLevel_new=D<br />

debugSplitSize=10485760<br />

debugSplitPeriod=12<br />

debugRemoveAfterSplit=1<br />

2. Send ofcdebug.ini to client users, instructing them to save the file to C:\.<br />

LogServer.exe automatically runs each time the client computer starts. Instruct<br />

users NOT to close the LogServer.exe command window that opens when the<br />

computer starts as this prompts <strong>OfficeScan</strong> to stop debug logging. If users close the<br />

command window, they can start debug logging again by running LogServer.exe<br />

located in .<br />

3. For each client computer, check ofcdebug.log in C:\.<br />

To disable debug logging for the <strong>OfficeScan</strong> client:<br />

Delete ofcdebug.ini.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!