You have migrated from a legacy version of Symantec Endpoint Protection to version 12.1 and want to bypass the IIS proxy (ISAPI) that is used to maintain functionality during the transition to the new version.
Version 12.1 uses Apache instead of IIS for providing Web services to the Symantec Endpoint Protection Manager. To make sure that the migration goes smoothly, an ISAPI proxy is used to pass SEP Client communications from IIS to Apache when you upgrade to Symantec Endpoint Protection 12.1. After the migration completes, you can bypass the proxy to improve server performance.
You bypass the ISAPI proxy by editing a pair of Apache and Tomcat configuration files on the Symantec Endpoint Protection Manager, and then turning off IIS. You can use any plain text editor to edit the configuration files.
WARNING: The following procedures have you stop or change ports in IIS. Other applications that rely on IIS will be affected if you stop IIS or reconfigure the ports that other applications are also using.
Start this workflow after you migrate to version 12.1.
NOTE: As an optional step at the end of the workflow, you can uninstall IIS if it is not needed for another application.
Begin by editing the configuration files:
Additional information about the 'listen' statement is available at the following URL: httpd.apache.org/docs/2.2/mod/mpm_common.html#listen
Next, stop IIS from the IIS Control Panel, or if you are using IIS for other applications, change the port numbers for the Symantec Endpoint Protection Manager program.
Complete the workflow by restarting the Symantec Endpoint Protection Manager services:
The IIS (ISAPI) proxy is now disabled and SEP Client communication is now going directly to Apache.
If you do not want to use IIS at all, please do not uninstall it and just disable it.
Symantec Endpoint Protection 12.1 (full version only)