/build/static/layout/Breadcrumb_cap_w.png

Possible Virus Scan conflict

I recently upgraded to 5.3. Today, I experienced a virus scan malfunction on 3 separate systems, where McShield.exe was scanning kinventory.exe (I captured this behavior in a procmon capture) repeatedly. Has anyone else experienced this, or know of any best practices for virus scanners as it relates to the Kace agent? I do not know for sure that there is a correlation, and I am unable to replicate the symptom.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: zookdj 13 years ago
Second Degree Blue Belt
0
McShield and the kbox patching system caused serious performance issues on our older XP systems. We ended up switching to Sophos.
Posted by: jverbosk 13 years ago
Red Belt
0
I ran into the same thing after upgrading to the 5.3.47173 agents with WinXP SP3 running Eset NOD32 (v3) and Win7 x64 SP1 running Eset NOD32 (v4). Particularly noticeable during patch runs, although invenories were also slower.

I created exclusions in the AV config for the following directories and things behaved better afterwards.

XP
C:\Documents and Settings\All Users\Dell\KACE\*.*
C:\Program Files\Dell\KACE\*.*

Win7
C:\Program Files (x86)\Dell\KACE\*.*
C:\ProgramData\Dell\KACE\*.*

I also excluded the IP address of my KBOX in the AV's Web access protection section.

John
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ