Skip to content

KACE Systems Deployment Appliance (SDA)

← Customer Feedback for Quest KACE

Please tell us how you’d like to see the KACE System Deployment Appliance product improved!

How can we improve the SDA?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

2 results found

  1. Role-based access control (RBAC)

    Regulate access to various functionality based on user roles and permissions. This would include granular access to capabilities such as:

    • Logon to KBE
    • Access to specific production images
    • Server/workstation roles
    • Samba share access
    • Differentiate between access to deploy images, and access to log into connected machines as an admin.
    272 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  30 comments  ·  New Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Object History tracking for security auditing

    The KACE SDA currently has no way to audit changes made to any imaging-related objects, including:

    • KBEs
    • System images
    • Pre/Mid/Post install tasks
    • Task Groups

    Coupled with the "all or nothing" approach to permissions in the SDA, this creates an information gap that results in a security concern: how do you know what object or setting change was made, when it was made, and who made it?

    Consider the worst case scenario: a disgruntled SDA Admin on their final day at the company adds a malicious script or application to a post-install task.

    The risks that come with the current model:

    …

    57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  New Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?

KACE Systems Deployment Appliance (SDA)

Categories

Feedback and Knowledge Base

(thinking…)