- #Symantec endpoint protection icon green dot how to
- #Symantec endpoint protection icon green dot update
So here’s a Step-By-Step instruction on how to accomplish this. That was easy enough. Even after a reboot I now have up to date definition files and I have an extra GB of data on my system disk where the files used to be. I stopped the SEP client, copied the entire Definitions folder to a location on my persistent disk, made my registry changes and started the client. There are a number of values that need to be changed but I’ll get to that later. The path to this folder is located in the HKLM registry. You can tell by the little arrow symbol on the folder: The CurrentVersion folder is actually a symbolic link to the folder named after the SEP version (in this case. If the files are out of date, updates will be downloaded to the corresponding subfolders.
After the SEP service starts the client checks the current files, which are located in this folder: C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Definitions.
#Symantec endpoint protection icon green dot update
Here’s how I did it: The solutionįirst I figured out how the update process works within the SEP client. So I decided to create my own redirection solution. The problem is that the SEP client does not have a configuration option that will allow you to do that. The obvious solution to this unwanted behavior is to move the definition files to a location on the persistent disk attached to the VM. This means that, each day since the last vDisk version, the client will have to re-download all definition files after every reboot. Since a non-persistent desktop loses all updates after a reboot the Symantec Endpoint Protection (SEP) clients’ virus definitions also resets to the moment you last updated the definition files in your image. Citrix PVS is used to stream a read-only vDisk to VM’s on a XenServer infrastructure. Prevents errors on Citrix servers and Terminal Servers.I’m currently working in a Citrix XenDesktop environment with pooled, non-persistent desktops. LaunchSmcGui_Explain="Set to Disabled to prevent SmcGui.exe from launching. KEYNAME "SOFTWARE\Symantec\Symantec Endpoint Protection\SMC" Just save the following to a file (whatever.adm) and add to administrative templates in group policy.
Hopefully this will help someone else along the way. I created a custom administrative template file that will allow these settings to be pushed out with group policy. Woohoo! Turns out we already had the proper maintenance pack installed, so I tested adding the registry key and it worked great. Too much wasted time on that forum thread!!!Īfter some more googling (sp?) I came across this Symantec knowledge base article. Reading this thread leads to nasty hacks like renaming the SmcGui.exe executable file (which doesn't work), replacing the file (which sometimes works), and some other issues. Problem: Even if you setup a policy via the SEP Management Console to disable the system tray icon, the server still launches SmcGui.exe, and fails to close the process when they logout.Ī quick google of SmcGui.exe and Citrix yeilds a terribly log thread on the issue over at Symantec's forums. Disable the icon.Ĭonfigure a policy on the SEP server for terminal servers to disable the system tray icon and the gui. Upon closing their published application (any application), the little yellow shield, as well as the SmcGui.exe process, stay running in the background. This also puts a SEP icon (little yellow shield) in the users system tray. We have been experiencing some issues with Symantec Endpoint Protection (SEP) and Citrix.īy default, when users would launch a published application via Citrix, the Symantec Management Client (smc.exe) service launches a process called SmcGui.exe.