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

    156 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

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

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

    36 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. 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 →
  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. Email notification upon Patch Schedule Completion

    As many users do, i assume that they have patch schedules set up.. Detect or Deploy only. or even full detect and deploy.. Set up to run at specific times.

    Currently, when you go into that patch schedule, you can see down at the bottom, the machines it will be doing (based on your selection), with Amount needing to be patching, that were patched, etc.. and the STATUS.

    Currently i have created a report, which i now manually run the next morning, to give me this information. I want to see WHAT was done automatically, without having to log into…

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

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

  9. Retry button for failed systems on a patch schedule list

    Lets say you have 20 DC's as an example and you run the patching and then click on the screen that shows your patching process and after a period of time lets say a couple systems fail the handshake or upload files error, you cannot just click on the two machines or failed machines and hit "retry" for just those machines. What we need to have is a retry button that retries all the failed or systems that do not show "Completed" - so that you don't have to run the whole patching process again for all systems when you…

    8 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. 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…)
    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 →
  11. Tray icon color changes if patches are pending

    For the KACE agent tray icon, I would like to see the color be something different, maybe yellow, when there are patches pending that need to be install. That way, when a technician say is working on it, he could go ahead and push patches to the machine to see if a patch resolves an issue.

    3 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. Track and manage Bluebeam Updates.

    Track and manage Bluebeam Updates.

    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. Add Milestone Systems patches and updates repository to Patch Manager Catalog

    Add Milestone Systems patches and updates repository to Patch Manager Catalog to stream line patch management for all security camera systems running with milestone systems since the manual software updates for these systems are very time consuming would be a great sales case for alot of enterprises using milestone software to monitor their sites

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

    63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  15. Custom CRON Schedules

    "In the Administrator's Guide it says that custom schedules can be set to "Run on the first Monday of each month at 09:00" and has the example of 0 9 1-7 * 1. This does not work." Your KB article 125945 - We have always run on a monthly patch schedule following Microsoft patch Tuesdays. It would be really beneficial to have this work. Otherwise, I have to adjust times every month.

    5 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 →
  16. 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 →
  17. Ability to filter patches by Operating System "Begins with" Win 10

    The last 2 weeks we have been very busy getting WIndows 10 build 1709 to patch. The patching stopped since the update of the 24th of July.

    Our patch label had Win 10 as Operating System.
    To fix this, we had to add Win 10 SP0 and Win 10 SP0 x64.

    It would be nice to be able to filter on Operating System "begins with" so we don't have to edit the patch labels every time Microsoft decides to change the current active build version of Windows.

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

    861 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  19. Additional patch schedule parameter: offset schedule by X days/hours

    The existing run on the {first/second/third...} {Monday/Tuesday...} scheduling option isn't useful for us. Yes, Microsoft puts patches out each Tuesday, but we always patch a certain number of days after Patch Tuesday.

    Having an offset value of x number of days after that would allow us to set a patch schedule once, and it would always fit our schedule.

    Example: "Run on the Second Tuesday of Every Month at 21:00, Offset by 2 days" would set our patch schedule to run at 9pm the Thursday after Patch Tuesday.

    This can't be done with the existing options. If I set it…

    3 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. More details on why a machine failed to patch.

    I'd like for there to be a way for you to look at what machines failed to patch, and see what errors occurred, and potentially a knowledge-base article about the error. That way you don't need to dig through logs trying to fish out the particular error.

    5 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