Endpoint Protection

Would someone confirm that HKLM\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\LaunchSmcGui does not exist in RU5 hence the impossibility to stop SMCGUI for each user on TS?

Remove it from SEPM..Show Client in notifiction area.
or  manually create this key in registry..

Yes the value is not present in RU5

If you want you have to manully craete it.

 You need to create this key manually...

thanks
My point is - would disabling "Display the Client" and "Display Notificatio Area Icon"  prevent  SmcGui and ProtectionUtil*** from running for every user on terminal server or I will have to recreate the reg key?

This was fixed in MR3 
Terminal servers run multiple instances of ProtectionUtilSurrogate.exe

Fix ID: 1185648
Symptoms: After installing Symantec Endpoint Protection 11.0 to a Terminal Server, a copy of ProtectionUtilSurrogate.exe is ran for each user that logs on.
Solution: Symantec Endpoint Protection 11.0 now allows for a client to disable the extra components from loading in separate sessions.

 go through page19
http://service1.symantec.com/SUPPORT/ent-security.nsf/2326c6a13572aeb788257363002b62aa/f5e1baf6ca2b5d638025750b00511265/$FILE/07014581.pdf/SEP%20on%20Terminal%20Servers.pdf

yes, I know that but it says to change the reg key LaunchSmcGui which doesn't exist in RU5. Therefore I am curious whether disabling "Display the Client" will do the same?

It should not load smcgui after disabling that..I have tested in my test machine and SmcGui hasn't shown up after disabling "Display client".

that is strange because I still have them running for my account as well as for all the users currenlty logged on. Also will delete ccApp from HKLM\....\run
Will post here the results.

 Try smc -stop and smc -start to see if smcgui goes away..or you can also try renaming the smcgui as suggested in the doc.

smc stop/start didn't help but renamng did.
Now I will have to verify and confirm that SEP is still work in a proper way.
one detail though - before renaming and restarting the service it turned out it has worked for a user who had delted his profilie one week ago.

 Well..may a log off and log back in would have been a better test anyways
Renaming has few drawbacks that is also mentioned in the doc pg 20