Skip to content

KACE Systems Management Appliance (SMA)

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

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

161 results found

  1. Fix the Patch Catalog

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

    10 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)
  2. Patching - ability to display list of patches to be installed

    The option to display "details" of a patch job would be nice. A competitors product was nice in this regard. Key patch testers would know with no clicks just what was to be done to their systems.

    9 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)
  3. Support patching "Microsoft Windows 10 Enterprise for Virtual Desktops x64" OS

    Allow patching "Microsoft Windows 10 Enterprise for Virtual Desktops x64" OS via KACE

    9 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)
  4. Detect newer patches as "patched" rather than not recording them

    When the patch engine changed for v10 this feature was lost. Devices with software that is "newer" (a later version) than the patch that is detecting currently are not in the compliance report at all, as if they do not have the program installed. Newer versions should be detected as "patched" which was how it worked previously

    9 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)
  5. Allow users to patch from the user portal.

    I would like to allow users with laptops to patch at their leisure since they might not have their device powered on at a scheduled time.

    9 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)
  6. Auto reset tries or on button for reset tries of all patchs

    • The ability to define a modifiable schedule in the KACE SMA web interface to clear the number of patch deployment attempts.

    • Or/ and button for reset all tries of all patchs.

    8 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)
  7. Requesting foxit phantom pdf patch for updates on windows

    Kace k1000 has Foxit reader and Foxit enterprise reader patches available. The same software publisher (Foxit) has another pdf product called "Foxit Phantom PDF reader" and these patches are not available. Our firm utilizes both applications, but as of now we cant centrally manage them both with kace patching. This will force us to have to script and test a MSI deployment to update phantom pdf reader; which is not as efficient as the patch management.

    As of right now Foxit version 9.1 is only available via kace for foxit reader and not phantom reader as well.
    *Patch Description
    Foxit…

    7 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)
  8. Patch Settings for Online Source should show info about patches.tgz

    Should at least have the file size. But would also be nice if a summary of the patches was available.
    Since the process of moving new patches to the offline kbox is manual, it would be nice to provide information about whether it needs to be done.

    7 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)
  9. Enable 4/8 hour sleep on reboot option, or customizable options

    Previously to version 10.2, there was an option for 4/8 hour sleep before rebooting, this would push it to the end of the day. This option should be controlled by the administrators, it should be customizable and set to whatever we would like it to be.

    7 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)
  10. Dropdown list of valid label names in smart label definitions.

    When entering a label name in a smart label definition, provide a dropdown list of valid label names to choose from. This would prevent typographical errors from creating an invalid definition. For example we have a smart label of "emergency" patches embedded in our deployment jobs which is usually empty. The label name was misspelled for over a year but not caught until we put a patch in the emergency smart label and it didn't go out as expected.

    7 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)
  11. Patch on Shutdown

    Patches should be applied on a Shutdown. Users complain that they shutdown every night, but patches are not getting applied. Once they restart patches do get applied.

    "About the shutdown/restart process when running patch jobs the K1000 agent only understands the reboot command because that's the command that K1000 SMA server uses to apply any information on devices.
    This is not a bug, but the developers are working to implement also the shutdown option for the agent in that way if someone performs a shutdown, the agent will recognize that process. This will be added in future versions, for now,…

    7 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)
  12. Allow patching/update of VMWare ESXi trough KACE

    There are quite often new updates for ESXi systems released, however, in our company those are currently not being patched as we have no options for it. It would be great if this could be implemented in KACE to allow us to update our ESXi environment using KACE instead of doing it manually or have to use another product for patching.

    6 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)
  13. add a run now module for patching similar to scripting

    I would like to see the an option for patch management similar to scripting where you can chose a patch schedule and run it against a device(s) with out having to run the scheduled schedule along with the run now status

    6 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)
  14. Rerun patch schedules for only the devices that are offline or have errors

    instead of rerunning a patch schedule for all devices, just continue to run the patch schedule on devices that are not completed or have errored out. If you have two schedules one that has no reboots and and one patch schedule with a reboot option. it should reboot the machine instead of bypassing the pending reboot status inorder to patch the missing patch

    6 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)
  15. Please add folders to Patch Management Schedules to organize all the different schedules.

    I have a lot of patch schedules. Some for servers. Some for computers in different locations. It would be helpful if I could organize these into different folders instead of having them all together.

    6 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)
  16. Provide setting to allow Superseded Patches to be Inactivated after a Delay of 30 Days

    Currently we patch all Test/Dev servers following MS Patch Tuesday with all current patches.

    We then patch all Production Servers with those same patches 1 month later.

    Since Microsoft Supersedes patches every month, causing the patches from 1 month to be superseded before the Production Servers get patched, and we tell SMA to Inactivate Superseded Patches, they never get installed on Production Servers.

    If we could have a setting to delay the "Inactivate Superseded Patches" for 1 month or any number of days, we would then be able to patch our Production Servers 1 month behind our Test/Dev servers and…

    6 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)
  17. Pre/post-pend batch or script

    I would like to see an option to pre/post-pend a batch or script command for Patch management, Dell updates, and Agent updates for systems that we have running DeepFreeze. I could use it to issue the CLI thaw/freeze command. It's more variables than I care for to try to coordinate Patch Management and Deep Freeze maintenance windows together, and some of the systems take longer to patch than others.

    6 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)
  18. SMA with Proxy in DMZ

    We want to patch machines that are not on the network but are connected to their wireless at home. This will help with patching compliance. However, I'm told this can only be done by having our internal SMA public facing. This isn't best practice and we'd to have it point to our proxy in our DMZ. I was told this setup isn't currently supported.

    6 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)
  19. 6 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)
  20. Linux Patching: Kace to act as proxy server

    The option to have the KACE server act as a proxy for Linux patches. Similar to how Windows patches are downloaded locally to the appliance.

    6 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)
  • Don't see your idea?

Feedback and Knowledge Base