KACE Systems Management Appliance (SMA)
Please tell us how you’d like to see the KACE Systems Management Appliance product improved!
161 results found
-
User-Initiated Detect and Deploy Patching
Have a completely user-initiated form of Detect and Deploy Patching. We currently have an overwhelming majority of users on laptops in a K-12 school environment with a weekly patching schedule. Due to the various different schedules at all the schools and and the district office, there is no single good time to have the patching, nor due to all the different schedules that can change at each school site from week to week. The teachers can't have the updates occur during their lessons so snoozing is enabled, but with the devices being laptops, many teachers then take the devices off…
3 votes -
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 -
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 -
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 -
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 -
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 -
The patch progress window doesn't always close
KACE Patching, "Patching is in progress. This window will close automatically upon completion. Please wait..." Nice feature, but frequently becomes a permanent desktop fixture. After the patch successfully installs, this window never goes away. Every time I've seen it, it's been with Adobe Flash Player updates, but that could be coincidence since they happen so frequently.
2 votes -
Add a patch label to multiple schedules
Hello, it would be very useful to allow a patch label to be added to multiple patch schedules at once, rather than having to open and edit each patch schedule.
I have many many schedules - opening each one to add a label is time consuming.2 votes -
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 -
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 PMIt 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 10pm2 votes -
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 -
1 vote
-
Widget - real time status of a scheduled patch deployment from home screen
Instead of having to go to each individual patch deployment schedule, to check the current status, the information can be pulled from a widget on the home page. When selected, more in depth info on the schedule(s) running will be listed with the percentage of complete/incomplete can be listed.
1 vote -
Central scheduling page
A centralised location/page where you can see all of your tasks and when they are scheduled.
1 vote -
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 -
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 -
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 -
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!
Scott1 vote -
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 -
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
- Don't see your idea?