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

Comments

Please log in to comment

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

Answers

0
McShield and the kbox patching system caused serious performance issues on our older XP systems. We ended up switching to Sophos.
Answered 09/29/2011 by: zookdj
Second Degree Blue Belt

Please log in to comment
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
Answered 10/04/2011 by: jverbosk
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity