Citrix and terminal server best practices for Endpoint Protection
|Article:TECH91070|||||Created: 2008-01-24|||||Updated: 2014-11-21|||||Article URL http://www.symantec.com/docs/TECH91070|
This article describes best practices for configuring Symantec Endpoint Protection (SEP) with Terminal Server and Citrix solutions.
The following white paper provides information on the best configuration of Symantec Endpoint Protection in Terminal Server and Citrix environments.
These recommendations apply to Symantec Endpoint Protection 11 and with minor differences also to Symantec Endpoint Protection 12.1.
In Symantec Endpoint Protection 12.1 some processes have changed on the client:
- ccApp.exe and Rtvscan.exe are no longer present. Their functionality has been moved into ccSvcHost.exe.
- SmcGui.exe will only be running if the user launches the Symantec Endpoint Protection GUI and it should only be launched for that user session.
- The ccSvcHst.exe handles the system tray icon which is supposed to run in every session.
The start of these multiple instances can be prevented by modifying the registry value for LaunchSmcGui as described in the document.
Prevent the process from starting by changing the registry value:
- Click Start, Run and type “regedit” then click OK
- Browse to HKLM\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC
- Find the entry LaunchSmcGui and change it from DWORD 1 to DWORD 0 (add it if it is not already present)
Note: When LaunchSmcGui is disabled, the Help (or Help and Support) > Troubleshooting window will show the server as offline. However, the client will still update policies/content as needed. The Policy Serial Number can be verified by viewing the SerialNumber string in the registry editor (HKLM\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\Sylink).
If you are unable to modify the listed registry keys, you can temporarily disable Tamper Protection.
Article URL http://www.symantec.com/docs/TECH91070