SMA (K1000)

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

How can we improve the SMA (K1000)?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Additional end-user options for patch installs

    I would like to be able to give my users the flexibility to schedule installs of patches at a time that suits them ... for example, when the popup appears on the client PC, offer them a range of options such as:
    -- install now
    -- remind me in 1 hour
    -- remind me at 11:00am
    -- install when I next shut down

    751 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    42 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →

    This feature was initially slated to fit within the 9.1 release; however, due to development efforts, it needed to be deferred until a later release (with that most likely being 10.0).

    I believe Ken had inadvertently marked this as Complete by mistake, and we apologize for the confusion.

  2. Allow a user to patch on demand

    It would be great if end users could initiate patching. Right now they can OK or Snooze a patching message, but are not notified again until the snooze interval is up. Right now we have that set at 60 minutes. But if a user is heading to a meeting, it would be great to allow them to begin patching when they leave their desk.

    740 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Optimize patch order to reduce reboots

    I find that patching fully from Microsoft Updates may require 4 reboots on an OS like Vista SP2. Patching that OS with Kbox, might require 10 or 15. End-users don't like reboots. Optimizing patch deployment to a system would be greatly welcomed to reduce the restarts a workstation/server needs.

    607 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

    363 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.…

    191 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Pre-staging of patches

    To increase our patching run rates and to better manage network bandwidth, we’d like the ability to pre-stage required patches on systems and kick off the installation at a designated time; preferably, the appliance tells the agent to start its patching cycle at the designated time (especially for devices off-network like laptops).

    It's my understanding that staging doesn't occur with just a detect; the updates are only copied down during the deploy phase.

    143 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →

    This is under consideration but not planned for the next release, Please continue voting if you’d like to see this feature prioritized for a future release.

  7. Regarding the Patching Schedule, Reboot Options

    Regarding the Patching Schedule Reboot Options, I was hoping to see an option that is between “Force Reboot” and “Prompt User”. What I was looking for was “If there is a user logged on, then prompt user” and “If there is no one logged on Force Reboot”.
    We have a few hundred machines (student and faculty/staff) that get patched every night. I want to make sure that the machines get patched (and may need a reboot) and not wait till someone uses the machine to reboot, so forced reboot is great. But, then again, I don’t want a student working…

    135 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  14 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  8. Patching Notification

    Just spit balling a thought that just ran through my head:

    What if Lumension / Kace issued a patching notice / update to admins who register for it? It could be a weekly email thing. In it Lumension could outline newly released patches (MS, et al.) and the projected release dates from Lumension down to our Kboxes. As admins we would know that certain patches we are looking for are in the pipeline and their ETA dates. Now, as admins, we are no longer in the dark wondering where our patches may be. It would keep emails or support tickets…

    121 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. Would love to see patching for Linux supported in the KBOX!

    Would love to see patching for Linux supported in the KBOX!

    104 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →

    This is under consideration but not planned for the next release. Please continue voting if you’d like to see this feature prioritized for a future release.

  10. Patching needs a Workflow Builder with Scripts, Notifications, Machine Actions.

    KACE needs the ability to build out a patching session as a workflow.

    With a Pacthing Workflow you can add in functions such as separate OS and Application patching schedules, Notifications, Scripts, Machine actions, etc. and have them all run within a set overall time and recieve vaulable notifications as the process is running or if something isn't working.

    Currently I have to run scripts before and after certain servers are patched to manage applications/services so a Detect and Deploy job with multiple reboots doesn't corrupt data. Whenever a schedule time needs adjusted, changes have to be made all over…

    72 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  11. Ability to stop running patches with one click

    It would be nice to be able to click a “stop” button on the KBOX to stop a currently running patch schedule

    69 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. Let remote users download patches from microsoft

    Company with about 500 machines off which > 400 work from remote locations often.

    When a machine is not connected to the company network, it would download it's microsoft updates directly from microsoft. When inside the company network it would download it's updates from the replication shares.

    kr

    57 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  13. Run Patching when idle

    I would like the ability to have a patching schedule based on system idle time. ie have a check box that says run when system is idle for ___ minutes.

    41 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  14. Security - Advertise Patches

    SMS/SCCM have the ability to advertise patches in the form of a pop-up, notifying the user that they have x days to install patches and reboot, at the end of which it will be forced. Also the ability to force the install and give the user x days to reboot or else it will be forced.

    37 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  10 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  15. reboot

    When using the reboot option, although the timer does appear on the desktop, the countdown timer doesn't decrement. If the countdown timer is set to 30 minutes, the timers remains at 30 minutes until reboot. The timer doesn't move. It's doing it in the background but the users don't see the timer decrementing and it confuses the users as they do not know how much time they have left before it'll reboot. I'd like it to show the timer counting down.

    35 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Ken Galvin responded

    Thank you for your input. This is under review and will be prioritized higher as more votes accumulate – so, we encourage you to vote if this interests you.

  16. Add the ability to associate a script to a Patch Schedule

    I would love to have the ability to run a script as part of a patch schedule and have it run before the patching begins.

    The example I have in mind would be for patching BIOS on computers using Bitlocker. I could have a separate patch schedule for BIOS patching only and have a script set to run prior to patching that would suspend bitlocker and enable it after the next reboot. With it being integrated with the patch schedule, I would not have to worry about the bitlocker disable script running needlessly.

    I am doing something similar with scripts,…

    33 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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?

    31 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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??

    31 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  19. Initiate patch installation to local machine from patch detail page

    From the adminui/patch.php page, add a button to force a detect/deploy for the patch on the current machine. This would be useful for trouble-shooting failed patch deployments when only a few machines have trouble.

    30 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add Rocket.Chat and TortoiseGit to the patch feed

    I would like to see more software available. Please add Rocket.Chat for Mac and Windows to the patch feed. What about TortoiseGit for Windows? TortoiseSVN is already included, but not TortoiseGit.

    24 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6 7
  • Don't see your idea?

Feedback and Knowledge Base