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. Allow for incremental updates to Bios in K1000 Dell Updates.

    Some of our machines currently have the bios that came on them from the factory, in this case A00.
    The Dell Update catalog on the K1000 has bios A07.
    You cannot jump from A00 to A07 without another bios in between.
    Perhaps having all available bios's available in the Dell Update catalog would be good so that updates wouldn't be broken in this situation.

    21 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 →
  2. 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 →
  3. Smart Label patches on type/category

    Let it be possible to also create patch lables on the criteria WHICH category it belongs to.
    Example: Smart Label which only contains Service Packs for Windows 7.
    MS is using this "form" in their WSUS solution. See screenshot.

    20 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 →
  4. Ask user to confirm before rebooting

    On the reboot prompt, ask user if they are sure they want to reboot. Some users don't see the window pop up and hit enter and reboot by mistake without a chance to close their work.

    20 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 →
  5. 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 →
  6. "Lock" a patch label

    Our current patching procedure involves running a test job of newly released patches from our smart labels on the Wed. following Patch Tues. We run this test job on approx. 10 IT lab PC’s + the PC’s of users who use critical applications. Once the test job and application testing is complete, we would like a way to lock the patch job to prevent additional patches from being added to the Smart Labels. Currently, patches that are downloaded to the K1000 subsequent to our testing and prior to the scheduled company-wide patch deployment can be dynamically added to the Smart…

    16 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. Notifications for Patching

    It would be nice to have the ability to link one or more email addresses to a patch schedule kind of like in the reporting. When all the servers in the schedule are finished (completed, error, or reboot pending) an email is sent to notify someone.

    16 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 →
  8. Snapshot a Hyper-V Machine before Patching

    Before Patching a Hyper-V Machine wouldn't it be awesome if the K1000 could have the perform a snapshot first, so if it fails you could just revert in a matter of a few minutes.

    16 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 →
  9. Update the vendors patch subscription list

    Can the vendors patch list in subscriptions be reviewed and have new vendors added? I am looking to patch more applications. We are working on pushing the Zoom client to all users, and it would be beneficial to be able to subscribe to patches from Zoom.

    The ability to request new vendors from the subscription's page would be beneficial as well. This would allow KACE managers to be able to submit vendors request without having to submit an improvement request.

    15 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. Remotely clean up patch cache on endpoints

    It would be nice to be able to be able to delete the cached patching files from C:\ProgramData\Quest\KACE\patches from the SMA console. Sometimes you need to clear that folder out to fix patching errors or detection issues with stubborn endpoints. Some sort of context command or action available from the inventory screen would be ideal.

    15 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 →
  11. Separate options for Embedded OS

    Right now, selecting and OS automatically includes patches for Embedded OS options. For those not interested in Embedded, it causes extra clutter and work to manage patching.

    Make embedded OS separate options in Subscription. Example: Windows 7, Windows 7 Embedded, Windows 8, Windows 8 Embedded

    12 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 →
  12. End-user ability to minimize the patching box that comes up.

    Currently, the user can drag the box off the screen to get rid of it, but it is still there if there are giving a presentation, for example. It should be fairly easy to make it so the end-user can minimize the box.

    12 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 →
  13. Check all sessions before restarting the machine

    When a patch management deploy schedule has a reboot option enabled with the property "Automatically Reboot When No One Is Logged In" set to true, the Dell KACE agent should check all sessions on the system, not just the console session. If someone logs-in to their desktop via RDP and then disconnects, the agent (as it works now) will automatically restart the PC because it is only checking the console session.

    12 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 →
  14. Patching Status Dashboard Single Pane of Glass

    Please create a patch management dashboard that would allow us to quickly view the patching status of all the machines. Such as so many machines are 100% patched. These machines have errors with patching. Compliance per patch. Patches detected but not downloaded. Machines pending reboot. Even a section for just for logged errors throughout the entire patching process. When we see machines with errors let us select them and try to force the patches at that time. I think we need more single panes of glass throughout the Kace appliance but patching is most crucial.

    12 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 →
  15. Allow the organization administrator to add and remove the patch update source

    Allow the organization administrator to add and remove the patch update source. The admin should be able to change the patch source to internal or other update sources instead of using Lumention or Windows Update.

    12 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. Allow for Maintenance Windows for patch deployments

    With SCCM there is the option to allow a Maintenance window for a group of machines (collection). So i could have a single patch schedule which defines the group of patches to be deployed and assign it to all systems. The machines would ONLY be able to download and install the patches based on the defined maintenance window.

    Example:

    Server Group A - midnight to 2am
    Server Group B - 2am to 4am
    Server Group C - 4am to 6am

    Patch schedule includes all server groups. But based on the respective windows the times these servers will patch will be…

    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 →
  17. Patch Management Compliance

    Under Patch Management > Catalog you can see the compliance of a single patch. It shows you the number of computers that have a patch installed or missing but you can't click on the numbers and get a list of the computers. Being able to click on the numbers would be great. You could get an instant view of computers names that have a patch installed or missing.

    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 →
  18. Ability to list all devices in inventory - device list that are missing patches and remediate with one click

    What I'd like to see is ability to list all devices in inventory-device view that are missing patches and then select the device , under actions goto patch remediate and create a job to immediately push either all OS patches, or all critical patches, or all patches to the device or list of devices.

    Add in a live view of the jobs would also be good.

    Regards
    Nigel

    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 →
  19. 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 →
  20. Differentiate between "applicable" updates versus "available" updates

    KACE shows all 'available' updates but does not differentiate between 'applicable' updates, which makes it almost impossible to know true security vulnerability exposure. For example, if Flash is not installed on a system it KACE still shows Flash as 'missing' - however for security compliance reporting that system is not actually vulnerable because Flash isn't even installed.

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

Feedback and Knowledge Base