SMA (K1000)

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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Increase reboot text and import jpeg for logos

    Option to increase the text for the reboot. 255 characters is very limited.
    Ability to import a jpeg for the logo.
    Ability to have multiple logos or ability to uncheck the logo where not applicable. We have unique groups within our customer that don't want the corporate logo because they were divested but still under our support.
    Ability to set the reboot time instead of snooze. Example instead of snooze, reboot in 1,2,4 hrs.
    Ability to only popup an alert that patching is completed for server OS, so the admin knows the patches are installed and ready for a reboot. …

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. Security Patches should not be superseded by non security patches

    In our environment, we use Kace to deliver Microsoft security patches to our Windows Servers. We also use the setting to inactivate superseded patches to reduce patch installation redundancy.

    I found the July Windows Server 2016 cummulative update, KB4025339, was superseded a week later by KB4025334, which is a non-security update. This completely messes up my patching workflow.

    My current options, as I see it, are to either included non-security updates in my patching catalog and figure out which ones I am going to allow, or to allow superseded patches to remain active.

    Based on this, in my opinion, a…

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Fix the Patch Catalog

    Monthly Quality roll-ups do not supersede Monthly Security-only roll-ups as they should.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Notification if patch subscription is expired

    It would be nice if you could set KACE to alert you with an email or otherwise if your patch subscription expires for one reason or another so you can take action immediately.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Change Windows Update last check after patching

    Following the "Wannacrypt" panic in my company, an admin invited all users to "manually" update their computer. But many of them were angry against the admins team when they seen the last Windows Update check was one year ago.
    Actually, the K1000 appliance is patching the client computers daily, but the "Windows Update last check" date is not modified, so the users think updates are not applied.
    It could be appreciated if this "flag" can be upadted after patching through Kace.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Firmware Patching

    Currently Kace patches Dell firmware. Surface Pro systems have several firmware updates in the windows updates.

    When can we get the Surface Pro (and others) to have firmware included in patching?

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support Windows 10 Feature Update installations via KACE patching.

    With the new model of Windows updates, we need to be able to easily push these feature updates such as Anniversary Edition via the KACE in order for it to fully replace the current functionality of a WSUS server.

    501 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  8. Need to be able to patch 2016 Servers

    Please add the Microsoft patches so we can patch our Microsoft 2016 Servers

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. Hard Drive Encryption

    Please see if we can inject a script before patching starts to turn off login for encryption (Symantec Endpoint Encryption) and a script to turn back on after patching is done.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Patching reboot options default behaviour

    We have Microsoft patching set to prompt the end user about rebooting now or later so they can choose when to restart so it does not affect their work process. While the majority of reboots are prompted and go as planned, over the past couple of years we have seen several occasions where the user is definitely not prompted to restart at patching completion and KACE just restarts the system on its own accord. The most recent time it occurred I lodged a SR with Quest (SR Number:3918626) and a technician checked the logs and between us we concluded that…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  11. Suspend BitLocker as part of the Patch Detect & Deploy Jobs

    K1000 should (through inventory detection) be able to determine that the machine has BitLocker enabled and during a patch deployment of that machine, there should be an option to suspend BitLocker (manage-bde –protectors –disable c:) before the reboot so the patch job does not get stuck at waiting for a user to enter the BitLocker PIN. If multiple reboots are required the K1000 can continue to disable BitLocker in a Detect & Deploy job until all patches have been installed. After which BitLocker can be resumed. This would be a HUGE help if it can be added to the product.…

    256 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. Minimize Patch Notification

    It would be a nice feature to allow the user the option to minimize a patch notification other than disabling it completely.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  13. Change Patch Deployment scheduling so that Notify acceptance is required before deploying patches

    Currently, the NOTIFY section says:
    Display an alert dialog to offer the console user a chance to delay or cancel the action before it executes. If no user is logged on to the console, schedule run immediately.

    However, in practical sense, this is not good. I only discovered this after having a session with tech support, and this behavior does not work for us. We have a maintenance window for our servers which require manual intervention to allow reboot of the server during a maintenance window. I was planning on setting up the Kace patch deployment to display a notification…

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  14. Enable function to allow client to initiate patch deployment process to itself

    Enable client to initiate patch deployment process to itself. You can add it to the user console page of the Kace appliance. In the same way as there is a Downloads module for software deployment, Kace should add a new Patch module to allow clients to click on to install all patches defined for deployment to the client, and/or the client can select the patches they want to get deployed to itself.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  15. xps

    Please add the XPS 12 9Q33 to Dell Update Catalog.

    Missing for too long..

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  16. Dell Update Schedules

    Can you change the standard behavior in schedules whereas, 1) no Device Label is specified and 2) the "All Devices" checkbox is left unchecked, that the schedule will actually deploy to no devices? This is the logical, more intuitive, behavior.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  17. When patching fails with "error", tell us what the problem is!

    What a concept. It says "error" and error only. Tell us what the error is and why it's failing, maybe a solution??

    41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  18. Patches are assigned to incorrect OS.

    When setting up a smart label for patches and using the field of "Operating System" I then set that to a value of "Win 2012 R2 SP0 x64" which will incorrectly include patches for Server 2012. Most patches are labeled as applying to both OS. Which isn't correct. For example. KB3161561 has a patch for 2012 and another one for 2012R2. Both are classified as applying to both OS when it should be a one to one relationship.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add Publishers - Ability to add our own Publishers

    Ability to add publishers so we can add more software to be updated.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  20. Run again option for failed patch deployments

    There has to be a better way to run patches against failed deployments. In a large organization when a schedule fails for 30 of 600 machines I need a simple way to redeploy to those that failed. As of now I only see the way of copying the failed machines and entering them into a different schedule to retry. That's fine if you only have 1000 machines, but when the numbers climb it's very time consuming and also skews the results percentage in the original run.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base