Skip to content

KACE Systems Management Appliance (SMA)

← Customer Feedback for Quest KACE

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

How can we improve the SMA?

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

6 results found

  1. Support for multiple active directory domains

    Being able to connect to more than one active directory for single sign on would be an amazing feature. I have a setup where I have multiple active directory forests and MUST keep them separate and disconnected. I use multiple orgs and am enjoying it, but without being able to join to each active directory with single sign on, I am afraid user adoption of the portal will be minimal and not worth the effort. Please add this as soon as possible.

    91 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…)
    under review  ·  3 comments  ·  Single-Sign-On  ·  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. Azure AD Provider SSO

    Build some nice and easy SSO integration for Azure AD similar to salesforce. Would be very nice to be able to do this like you can with salesforce etc, I'm very surprised that in the re-design for SSO that it wasnt brought in.

    58 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…)
    2 comments  ·  Single-Sign-On  ·  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

  3. allow users to change organizations

    When users login using SSO they get the default organization. They do not have a way to change to another organization. A fast organization change like the admins have would correct this issue.

    33 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…)
    1 comment  ·  Single-Sign-On  ·  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

  4. Ability to track kace user last login into KACE appliance and disable the inactive accounts

    We need to able to track last user login into the KACE appliances, if the user has not logged in last 30 days, it would be disabled. We need this for PCI compliance to avoid fines.

    19 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…)
    0 comments  ·  Single-Sign-On  ·  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

  5. Change the UPN of the user created by enabling SSO

    The user account that is created when enabling SSO has a forward slash in the User Principal Name (UPN).

    Azure does not like the forward slash and this causes a 'Data Validation Error'.

    I'd like to request a change to the format of the user logon name that is created by the Kace SMA when it joins to the domain.

    12 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…)
    0 comments  ·  Single-Sign-On  ·  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

  6. Kerberos SSO Limit to IP Range

    About half of our workforce is off-site, many of them on Chromebooks where there is no Kerberos authentication. Please add a feature where Kerberos SSO can be enabled on a per-IP range basis so that we can enable SSO for on-prem users only. If Kerberos is enabled for computers that aren't using Kerberos, they see two login prompts and have to login twice.

    Example
    Enable Kerberos: Yes
    Limit Kerberos to IP Range(s): 10.10.5.0/22

    This would allow us to use Kerberos for on-prem end-users but prevent the double login prompt for appearing for off-site VPN users (about half of our workforce).

    3 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…)
    0 comments  ·  Single-Sign-On  ·  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 Management Appliance (SMA)

Categories

Feedback and Knowledge Base

(thinking…)