Extreme slowness on a users machine during KACE inventory
We've got a Daily_Detect_All schedule which runs every day at 2am and performs a Detect on all machines. We have about 350 machines and this detect schedule seems to run throughout a large portion of the day despite kicking off in the early morning. One particular user keeps complaining that their applications function extremely slowly while the Inventory process is running (they open up Task Manager and see it) on their machine. None of our other users have mentioned this. Is this something that anyone else has noticed or heard of? I guess I could break it up and have it only hit smaller groups of machines and spread it out over 3 or 4 days so that it hits machines before anyone comes in to work, but are there any issues with only performing an inventory every few days?
I would notate down the time an inventory runs, and then look at the agent log (C:\programfiles\quest\kace\user\kagent.log). There should be several numbered agent log files in there.
See if there are any custom inventory rules maybe that are running on that machine at that time.
Is metering enabled on that machine? If so, turn that off on it.
Are you running OVAL or SCAP scans on that machine?
"We've got a Daily_Detect_All schedule which runs every day at 2am and performs a Detect on all machines.".
Use Labels based on Software and O.S. version installed in your device.( please do not detect all patches, you making the patching process waste time by checking patches for Apps you don't even have, use Smart Labels).
Also there's no need to detect patches all every single day, even if it's outside business hours, plus Are those Desktop Devices? Because If you have Laptops, How do you know your detection did not happen at 2AM, and it was not deferred to the next Online State. (that means when your users login in the morning).
Anyways, see if an AV is blocking the patching process.
Review the KAGENT log, it will tell what is doing when the device is Slow (ask your users when that happens and note the time), if it's patching, AV might be blocking your patching EXEs.
Or you are detecting thousand of patches and the process is still running at 8AM... plus AV auditing the process....