Checking The Inbox Logs On The Management Server; Recovering Client Communication Settings By Using The Sylinkdrop Tool - Symantec 20032623 - Endpoint Protection Small Business Edition Implementation Manual

Checking the inbox logs on the management server

Recovering client communication settings by using the SylinkDrop tool

Troubleshooting communication problems between the management server and the client
To check the debug log on the client
1 In the client, click Help > Troubleshooting
2
On the Troubleshooting dialog box, in the column on the left, select Debug
Logs.
3 On the Debug Logs panel, click Edit Debug Log Settings
4 Enter a name for the debug log and then click OK.
You can then click View Log to view the log files.
You can use a Windows registry key to generate logs about activity in the
management server inbox. When you modify the Windows registry key, the
management server generates the logs (ersecreg.log and exsecars.log). You can
view these logs to troubleshoot client and server communication.
See Troubleshooting communication problems between the management server
and the client" on page 316.
See Checking the debug log on the client computer"
To check the inbox logs on the management server
1
On the management server, under
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint
Protection Small Business Edition\SEPM, set the DebugLevel value to 3.
Typically, the inbox appears in the following location on the management
server computer:
\Program Files\Symantec\Symantec Endpoint Protection Manager\data\
inbox\log
2 Open the log with Notepad.
The Sylink.xml file includes communication settings between the client and a
Symantec Endpoint Protection Manager server. If the clients have lost the
communication with a management server, you must replace the old Sylink.xml
file with a new file. The SylinkDrop tool automatically replaces the Sylink.xml
file on the client computer with a new Sylink.xml file.
When you run the SylinkDrop tool, it can also perform the following tasks:
Troubleshooting installation and communication problems
on page 320.
321