Skip to content

Anonymous

My feedback

2 results found

  1. 98 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    I agree, we have found even with 200 workstations (not all of which are ever online at one time) it really bogs down our internet bandwidth when tasks commence. Even detecting patches really eats up the upstream bandwidth on our lines until the task is complete. There needs to be a way to control Kace!

  2. 30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    The bottom line is that when you create a label group from the label management tab, choose action, new label group, the label which you just created cannot be used for any scripts or deployments. That is very frustrating because it would make it a lot easier if you could apply that newly created group to scripts. I understand that you can do smart labels but it seems to be the long way around instead of a straightforward group which can be utilized. As best I can tell, the label groups serve only for organizational purposes and cannot be leveraged for anything else.

    Anonymous shared this idea  · 

Feedback and Knowledge Base