I believe it is a client setting--although with managed corporate versions,
perhaps the setting can be controlled centrally--I'm afraid I don't have any
clients using the version which have this setting as yet.
--
"Kelli" <(E-Mail Removed)> wrote in message
news

72B3F71-97BF-4FD6-B242-(E-Mail Removed)...
> Is this optional Symantec feature you talk about on the client or the
> server?
> I will also search this group for more symantec information. Thank you!
>
> Kelli
>
> "Bill Sanderson MVP" wrote:
>
>> There are a number of posts, some with thoughful information on this
>> issue--in this very group, I believe.
>>
>> If you find these log messages troublesome, you can either turn off the
>> optional Symantec feature which is generating them, or uninstall Windows
>> Defender. Neither app seems to be harmed by this interaction.
>>
>> --
>>
>> "Kelli" <(E-Mail Removed)> wrote in message
>> news:E4327376-B596-47AE-BC0D-(E-Mail Removed)...
>> > What is with all the errors in my application log relating to defender
>> > and
>> > symantec? We are running Defender Beta 2 (.1347) and Symantec
>> > Antivirus
>> > (v10)
>> >
>> > Here are all of the errors (occur at startup):
>> >
>> > SYMANTEC TAMPER PROTECTION ALERT
>> > Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe
>> > Event Info: Open Process
>> > Action Taken: Blocked
>> > Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID1248)
>> > Time: Tuesday, May 26, 2006 12:37:20 PM
>> >
>> > SYMANTEC TAMPER PROTECTION ALERT
>> > Target: C:\Progra~1\Symant~1\VPTray.exe
>> > Event Info: Open Process
>> > Action Taken: Blocked
>> > Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID1248)
>> > Time: Tuesday, May 26, 2006 12:37:20 PM
>> >
>> > SYMANTEC TAMPER PROTECTION ALERT
>> > Target: C:\Program Files\Common Files\Symantec Shared\ccSetMgr.exe
>> > Event Info: Open Process
>> > Action Taken: Blocked
>> > Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID1248)
>> > Time: Tuesday, May 26, 2006 12:41:09 PM
>> >
>> > SYMANTEC TAMPER PROTECTION ALERT
>> > Target: C:\Program Files\Common Files\Symantec
>> > Shared\SPBBC\SPBBCSvc.exe
>> > Event Info: Open Process
>> > Action Taken: Blocked
>> > Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID1248)
>> > Time: Tuesday, May 26, 2006 12:41:09 PM
>> >
>> > SYMANTEC TAMPER PROTECTION ALERT
>> > Target: C:\Program Files\Common Files\Symantec Shared\ccEvtMgr.exe
>> > Event Info: Open Process
>> > Action Taken: Blocked
>> > Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID1248)
>> > Time: Tuesday, May 26, 2006 12:41:10 PM
>> >
>> > SYMANTEC TAMPER PROTECTION ALERT
>> > Target: C:\Program Files\Symantec AntiVirus\DefWatch.exe
>> > Event Info: Open Process
>> > Action Taken: Blocked
>> > Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID1248)
>> > Time: Tuesday, May 26, 2006 12:41:10 PM
>> >
>> > SYMANTEC TAMPER PROTECTION ALERT
>> > Target: C:\Program Files\Symantec AntiVirus\SavRoam.exe
>> > Event Info: Open Process
>> > Action Taken: Blocked
>> > Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID1248)
>> > Time: Tuesday, May 26, 2006 12:41:10 PM
>> >
>> > SYMANTEC TAMPER PROTECTION ALERT
>> > Target: C:\Program Files\Symantec AntiVirus\Rtcscan.exe
>> > Event Info: Open Process
>> > Action Taken: Blocked
>> > Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID1248)
>> > Time: Tuesday, May 26, 2006 12:41:11 PM
>> >
>> > Any ideas on why there are so many 'errors' between the two?
>> >
>> > Kelli
>>
>>
>>