KACE Product Support Question

Way to exclude IP range from nightly polling?

07/25/2018 781 views
Greetings all,

I'm looking into an issue where nightly polling of kace agents is happening to a sister companies VM host cluster and driving up the CPU due to the limited amount of resources on the 3 hosts. Is there a way I can exclude the IP ranges of the three hosts so it won't get polled? I looked in the discovery schedules but that seems to be more aimed at discovering new vm's.
3 Comments   [ + ] Show comments


  • I'm not sure I understand what you mean by "polling of agents." Are you referring to Provisioning agents, agents performing Inventory on computers, network Discoveries, or something else?
  • Sorry, Agents performing inventory on computers. It looks like it hits all the hosts at the same time of the night so I'd either want to exclude them or stagger them on a schedule or exclude their subnets all together. Sorry for the confusion, I just took over from an older admin and they didn't document the KACE solution very much.
  • No problem. We're all here to help each other.
    Agent Inventory happens on an interval, which you can set in Settings > Provisioning > Communication Settings. Additionally, it's performed by the agent installed on the computer, and the results are sent back to the KACE server.
    If it really is Inventory, you could force an Inventory on each computer through the Device Inventory in the KACE interface, and that would reset that interval.
    If something is happening on many computers at once, I would be more inclined to think it's something that's scheduled to run at a specific time, like a Script or Patching.

Be the first to answer this question

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