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

160 results found

  1. Add schedule reboot option in patch management jobs

    In patch management under schedule detail, add a 4th reboot option to "Schedule Reboot". Currently the 3 options offered are, "No Reboot", "Prompt User", "Force Reboot". We are a healthcare organization and the window for installing patches and rebooting is very small. Using the install ALL PATCHES option with the "NO REBOOT" option is great because it allows us to install patches during business hours without having to reboot. However, devices are then left in a pending reboot state and we have to manually script when we want to reboot thousand of devices. It would be helpful to add a…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Fix the Automatically Reboot When No One Is Logged In reboots machines when a user is logged in and the machine is in connected stand by.

    KACE does not properly recognize the modern connected stand by that newer computers and operating systems support and reboots the computer even when a user is logged in if the computer is in connected stand by mode when the Automatically Reboot When No One Is Logged In option is checked. If a user is using their computer and stops using it for 15 minutes it goes into connected stand by mode and at that point if a patch schedule runs with the Automatically Reboot When No One Is Logged In option checked the machine will instantly reboot with no warning…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Add support for Microsoft Surface firmware and updates through Patch Management

    It is a real pain to keep having to manually update our surfaces when we have a patch management system that should support it. The firmware and patches come from Windows Update, so it should be an easy addition

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Automatic Patch Detection

    we can already create smart labels or manual labels for patches but it would be nice to have a Software update point schedule for the agent to detect the patches automatically based on the subscription settings and in this way a later deploy job can be made for only missing patches.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Ability to easily see and reset what patches have nodes that have exceed the deploy tries

    We need the ability to see and reset any patch, distribution, script, feature update, etc that has exceeded the "Deploy Tries". Currently, you have to manually go into each and then click Reset Tries. It would be nice to report on and reset the tries in bulk.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Feature Request Deploy Only Option

    I would like the ability under Windows Feature Update to have an Action of "Deploy". Currently, there is only the option to Detect and Deploy or Detect and Stage. We have a current Scheduled task to Detect and Stage and would like the ability to have another Scheduled Task to Deploy Only, without another Detect task. This is similar to the functionality we have with Windows Updates, it has an Action of Deploy.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Patch RUN NOW button has NO CONFIRMATION

    QUEST: I dont care how many votes are made for this, the fact that a person can press run now by mistake on patching and cause 100 servers to restart in the middle of the day is Ludacris! There is zero confirmation on the run now button. Better yet, make it optional to not show the button at all on patching with deployments.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Full Linux Patching/Upgrades + Scheduling Options

    This request would be that KACE has the functionality to upgrade ALL packages and NOT ONLY security patching. Right now, we are seeing that only security level patching is accepted and we would like to have the option to also include non-security related patching take place.

    Additionally, we are seeing that there is not as many options available to linux patching administrators under the "Linux Package Upgrades" feature. We would like to see a minimum that mirrors the patch management scheduling features in the Windows side.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Add multiple tasks per schedule

    Add multiple tasks per schedule:
    task1:
    Month: Jan
    Day: 6
    Time: 20:00
    task2:
    Month: Feb
    Day: 20
    Time: 20:00
    and so on...

    We have devices that never get patch on the same day/week every month.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Separate schedules for Installation - Reboot

    Create two separate schedules for installing patches and rebooting the machines.
    Example:
    Deploy from 13:00 PM - 15:00 PM
    Reboot at 23:00 PM

    It give us the flexibility to pick when we want the patches to be installed and when to have the devices reboot.
    In our environment I know that at 12pm the majority of our devices pcs/laptops will be connected and people start going to lunch so I would have the patches start installing at around 12pm but then have the reboot prompt start at 10pm

    2 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. detect patches installed on managed device, and install those exact patches on a different device

    Detect patches installed on a pc, and deploy those patches to a pc that may be missing them. Currently only way i could accomplish this was to used the device details in the inventory section. there under SECURITY, i could see the result of the patches installed. Had then click on them one by one all 30 and give them a manual label. Then i was able to use that label to deploy. the Patch Smart Label or some way to do this more efficient would be great.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Have an option to only install patches on machines with no user logged in

    I would like to option to only install patches on a machine if no user is logged in. There are numerous patches in KACE that will stop the program if a patch is installed while the program is being used. It would be helpful to have to option to only install those patches when no user is logged into the machine. This would eliminate the risk of a program being shut down while being used. This is important for us because management does not allow us to prompt users for patch installs or reboots.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. kb4052623

    Please figure out how to add kb4052623 to your patch catalog it is a very important part of security for many organizations to have the platform version of windows defender up to date.

    2 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. 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)
  15. Display the Number of Reboots Required on the Notification Panel.

    It would be sweet if there was a reboot count on the notification panel. That way users would know how many reboots patching is going to require. This is especially important for servers and system administrators.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Prompt to close Microsoft 365 apps if patching

    Pop up window to close Office Products during patching or automatically warn and close within 5 minutes to continue to update. Our Microsoft 365 apps are not patching. Summary information for the patches say Office needs to be closed to update.

    1 vote
    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. Ability to enter license for software publishers behind a paid service for access to patches.

    The ability to enter a license key/code for a software that is designed to be "fee based" or "in-app fee based" in order for that software to gain access to future patch downloads for the software when available.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Deprecated patching smart label in v12

    Deprecated patching smart label in v12.

    Please provide an option to report deprecated patching smart labels in v12 like hey were available in v10 via kbin.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Detect security updates from sources.list.d

    Currently for Debian-based systems, Linux Package Upgrade Schedules can only detect security updates from sources listed in the /etc/apt/sources.list file.

    If you have sources under the /etc/apt/sources.list.d/ directory, these are not considered by the SMA despite working correctly when running 'apt-get update' manually on the devices.

    This might not be desirable for organisations that maintain their primary or additional sources under /etc/apt/sources.list.d/

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Detect security updates from sources.list.d

    Currently for Debian-based systems, Linux Package Upgrade Schedules can only detect security updates from sources listed in the /etc/apt/sources.list file.

    If you have sources under the /etc/apt/sources.list.d/ directory, these are not considered by the SMA despite working correctly when running 'apt-get update' manually on the devices.

    This might not be desirable for organisations that maintain their primary or additional sources under /etc/apt/sources.list.d/

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Feedback and Knowledge Base