Hi Brian,
The following article may help. It exaplains how to enable Apache access loggign.... it sounds like that may be what is happening on that SEPM. Just reverse the steps to disable it:
Symantec Endpoint Protection Manager 12.1 Communication Troubleshooting
Article: TECH160964 | Created: 2011-05-26 | Updated: 2011-12-06 |
Article URL http://www.symantec.com/docs/TECH160964
Enabling and viewing the Access log to check whether the client connects to the management server
You can view the Apache HTTP server Access log on the management server to check whether the client connects to the management server. If the client connects, the client's connection problem is probably not a network issue. Network issues include the firewall blocking access, or networks not connecting to each other. You must first enable the Apache HTTP server Access log before you can view the log.
Note: Disable the log after you view it because the log uses unnecessary CPU resources and hard disk space.
To enable the Apache HTTP server Access log:
1.In a text editor, open the file
C:\Program Files\Symantec\Symantec Endpoint Protection Manager\apache\conf\httpd.conf.
2.In the httpd.conf file, remove the hash mark (#) from the following text string and then save the file:
#CustomLog "logs/access.log" combined
3.Using services.msc, restart the Symantec Endpoint Protection Manager Webserver service (Apache)
Click "Yes" to also restart the SEPM service
To view the Apache HTTP server Access log:
1.On the management server, open
C:\Program Files\Symantec\Symantec Endpoint Protection Manager\apache\access.log
2.Look for a client computer's IP address or host name, which indicates that clients connect to the Apache HTTP server.
3.Disable the Apache HTTP server Access log when done