/build/static/layout/Breadcrumb_cap_w.png
08/27/2019 202 views

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?

0 Comments   [ + ] Show comments

Comments


All Answers

1

I have orgs so if you do not have orgs it will be under the general settings

Mine is located under Org Detail

Z

Answered 08/28/2019 by: SMal.tmcc
Red Belt

  • I don't have Orgs, and I do not have a Communication and Agent Settings section at all under General Settings or anywhere else under Settings
1

googled the user manual

Z

Answered 08/28/2019 by: SMal.tmcc
Red Belt

  • way different place on non-org sma's
1

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?

Answered 08/27/2019 by: brucegoose03
Fourth Degree Black Belt

  • I tried modifying the Detect All process to start earlier and I changed it from All Patches to a smart label of only critical stuff we need, however it looks like the inventory still kicked off at the same time and the user is having the same problem again at the same time of day. So let me ask this, what causes the Inventory process to run on a machine? I haven't set up any custom inventory stuff, and last night/today there are no schedules/patches/scripts going out that would trigger a detect, other than the Detect All schedule.
    I'm looking through the kagent log on the users machines, what am I looking for? I'm not seeing anything really jump out at me, except a few entries like this:
    [2019-08-28.08:41:16][KInventory:CInventoryData::AddIt] KInventory Error: InventoryData AddItem : Could not find map in 'IEVersion' for 'Version,svcVersion'
    • under settings there is a setting for the inventory cycle as well as other communication items
      • Where is it? I just looked through everything under Settings and don't see anything for Inventory Cycle
1

Not good:

"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....

See:
https://support.quest.com/kace-systems-management-appliance/kb/111785/which-directories-and-files-do-i-need-to-whitelist-for-the-sma-agent-

Answered 08/27/2019 by: Channeler
Red Belt

  • Ah, good point thanks! This Detect All Schedule came with KACE when it was given to our organization so I assumed it was configured in a reasonable way, but I see that I should update it to waste less resources