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. 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 →
  2. Separate Notification for Reboot under Patching

    Currently when using Patch Management, the user can postpone the reboot. However, it is confusing to the user as they get the same notification when they defer or are out of deferments for rebooting. It would be beneficial to have a separate notification window when they can no longer defer or postpone the reboot.

    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 →
  3. Warning pop-up or other warning creating 'empty' patch schedules

    We had ALL WINDOWS DEVICES (incl servers) mistakenly patched yesterday because there were 2 patch schedules with zero devices in the device box and zero device labels selected. These schedules were there before upgrading to 8.1.108 and no issues. This could be a bug in the code. You should have a warning pop-up or other warning text that you are patching all windows devices in your environment (or similar).
    Luckily we had few calls to IT service desk and no production issues.
    Add a warning please.

    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 →
  4. Ability to add smart label to dell update subscription

    Dell updates needs to be setup like Patch Management. We have 100s of different models and we only update BIOS. Currently, we have to download 40gb and sync to the REPs to support deploying the BIOS. Also need the ability to add drivers/bios for other manufactures similar to uploading drivers on the K2

    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 →
  5. Undocking and Docking Interrupt Patching Timers

    When a user undocks or docks after they had selected No to a restart, it interrupts the timer and prompts them to restart immediately. Support stated this is due to the IP change from wired to wireless. Can it be modified to handle this IP change so the snooze timeout the user selected is not interrupted?

    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 →
  6. Request option to "turn off" Operating System patches for K1000 (Systems Management Appliance)

    I would like the option to DESELECT any OPERATING SYSTEM PATCHES on the K1000 (Systems Management Appliance).

    we only use the K1000 for applications, not for patching the OS

    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 →
  7. 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.

    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 →
  8. Patch Catalog: add field for Date Added to Catalog in Patch Detail

    Need a timestamp added to patch detail of when it was added to the Patch Catalog (feed) of your K1000.

    Released date is based on when patch was released by Vendor. Sometimes patches (esp. 3rd party ones) can take a week or more before showing up in the patch feed. This is problematic for pre-production testing purposes as there is no date to check against for when it became available to use in your environment.

    For example, if testing is 7 days and I check released+7 days in a label to enable production machines (as that is the only date…

    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 →
  9. Allow Patches to apply when the Kace prompt is deferred

    Currently, when the KACE agent prompts the user that a reboot is required to complete the patching process, it will give them the option to reboot now or defer until later.

    it will not apply the patches if the user defers until later, and then manually reboots through windows.

    The agent doesn't seem to know to apply the patches anyway, since a reboot is taking place.

    Spoke to a KACE rep and they told me this feature is not available currently.

    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 →
  10. 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

    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 →
  11. Change Patching push folder

    The K1000 pushes patches to C:/windows/temp -- and our endpoint protection suite is catching all of these with the upgrade to 8.0.318 for some reason, meaning we have to white list each new patch push. There should be a way to change this to an arbitrary folder of our choosing so we can modify permissions adequately on the folder, and white list it on our endpoint protection softwares.

    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 →
  12. Central scheduling page

    A centralised location/page where you can see all of your tasks and when they are scheduled.

    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 →
  13. Hi,

    Security>>PatchListing

    Currently Patch Listing displaying with default view "2014" Patches

    Customer Expectation: Default View should display "All Patches"

    Please provide the solution to make changes in the default view settings

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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 →
  15. allow applications to update without kace deploying the software. for example office 365 chrome updates Adobe.

    allow an exception rule for application to update. At the moment chrome does an update. Kace will redeploy the version it has assigned a label to the software.

    Office 365 updates monthly thus changing the version number which means admin have to re-deploy office 365 instead of letting office update freely.

    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 →
  16. Validation of distribution results

    Recently, I attempted to deploy Windows .NET 4.7.2 to our users.
    I utilized the Distribution platform and Microsoft's executable.
    (This software will be installed via: NDP472-KB4054531-Web.exe /Q /norestart)

    Ultimately the results showed almost all of them "FAILED" after 3 of 3 attempts.
    Further research showed that most of the clients already had .NET 472 installed, but it reported "FAILED" instead of completed.

    It would be excellent if the 'results' of the deployment would report either 'skipped' or 'success'.
    Thank you for your help and assistance!
    Scott

    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. Increase Size or Location of Notification Window

    Most of my users barely notice or ignore my notifications when patching. I would like for the ability to either resize my notification window or to move its location such as the center of the screen so they are forced to see the message.

    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 →
  18. Exclude ip addresses or devices via label or smart label in KACE

    Our servers are managed by WSUS and need KACE to not install an agent or patch the servers.
    We need a way to exclude the servers from KACE.
    Exclude ip addresses or devices via label or smart label in KACE

    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. 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,…

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

Feedback and Knowledge Base