KACE Systems Management Appliance (SMA)
Please tell us how you’d like to see the KACE Systems Management Appliance product improved!
161 results found
-
Please add folders to Patch Management Schedules to organize all the different schedules.
I have a lot of patch schedules. Some for servers. Some for computers in different locations. It would be helpful if I could organize these into different folders instead of having them all together.
6 votes -
add a run now module for patching similar to scripting
I would like to see the an option for patch management similar to scripting where you can chose a patch schedule and run it against a device(s) with out having to run the scheduled schedule along with the run now status
6 votes -
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 -
Stage & On-Demand deploy - Show a popup (on interval) that updates are ready for install.
The user doesn’t get any agent-popup that actively notifies him that “patches are staged, and ready for deployment”.
Only the agent-indicator in the system tray turns blue and the option “Deploy staged patches” is shown.But not a single user will keep an eye on the agent-indicator to watch out for the staged patches. Therefore, patches will not be installed in a fast manner, and the user can’t “plan” the deployment himself (within the maximum period of time before the forced indicator kicks in).
I think it would be handy if we can configure a notification-popup to remind the user…
5 votes -
improve agent notifications to include remaining reprompts and countdown time
The agent notifications in patch schedules do not make it clear to the user how many reprompts they have left or how much time they have left before the reboot is triggered. I would like to see something like:
3 of 5 prompt
The computer will reboot in xxx minutes5 votes -
Track and manage Bluebeam Updates.
Track and manage Bluebeam Updates.
4 votes -
Enable patching Autodesk 2019 and higher versions
Enable patching Autodesk 2019 and higher versions
4 votes -
User notification before forcing reboot
I configured the Patch scheduler to show a user prompt if a restart is needed. I also configured a number of prompts which the user can max. snooze the reboot. But if the max snooze count is reached the reboot is forced immediately in the background. It would be nice to pop-up a message box, with a countdown of the last 60 seconds which the user cannot close/minimize. because then the user gets informed that the computer will be restarted soon, but he has time to close and save all his work.
4 votes -
Include Firefox In Patch Subscription/Download/Patch Schedule
Please include FireFox in the applications that can be automatically patched.
4 votes -
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.
4 votes -
Ability to report on newer applicable patches for inactive devices
KACE is a snapshot in time for patch detection. My customer would like the ability to show compliance based on any applicable patches. Example if a device last detected on the 1st tuesday of a month, we need the ability to show those missing patches as well as the patches released on 2nd tuesday of the month.
4 votes -
Patch Labels
Add an additional option or change the smart label searches to include ONLY those patches it detects from the system. When I create a smart label for a specific OS and not to include superseded, it displays hundreds of patches most of which are not installed on my systems. It would increase admin efficiency if we don't have to invalidate each patch that doesn't matter.
4 votes -
Patching Notification Window
Introduce the ability to minimize the "patching in progress" window to notification tray icon, and/or introduce the ability to configure whether the notification window should be "kept on top" or not.
4 votes -
Hide Patch Schedules with devices and labels out of scope for user
The K1000 8.0 permission changes prevent users in a limited sub-admin role from adding out-of-scope devices/labels to a patch schedule. It also prevents them from running these schedules.
The user can however still view these patch schedules and remove/modify them. It would be better if any schedule containing an out-of-scope device/label were simply hidden from the user. This would prevent them from accidentally, or intentionally, deleting or breaking an existing schedule.
Alternatively, allow specific patch schedules to be restricted based on role setting.
3 votes -
Clear Failed Patch Deploy status if already installed
I have a SQL patch that shows as not patched with a deploy status as Failed. Was told since the patch was already installed that the detection can't detect it as needed so it will remain in RED as Failed and this behavior is as expected. Was told I needed to put this in User Voice to get enough votes to get someone in development to fix this. Management sees the patching reports and shake their heads as to why Quest can't fix this so it doesn't show up on reports as a failure. My ticket was open for nearly…
3 votes -
Dell Update Schedule Detail page needs fixing
I don't know if this is a localization issue or what, but in our version of KACE SMA (8.0.320), there are some confusing and/or broken options in the "Schedule" section of the Dell Update Schedule Detail page.
I was directed here by support, but this isn't really a feature request, this is a flat-out bug IMO.
In Normal patch management, there is a checkbox to enable run-on-reconnect if a device is offline at the scheduled time, and input boxes for "delay run" and "end after", where you can enter a number of minutes for each setting.
In Dell Updates, there…
3 votes -
Move patch message window background
Please give us the ability to minimize the initial patching in progress message, or put in the background so it doesn’t disrupt user workflow.
Currently, it sticks to the foreground until the patching process is complete.
3 votes -
When using no reboot option, notification to let the user know they can reboot
We use the no reboot option for servers. We would like the ability to leave a popup notification that updates have been applied and reboot when they can. Also show the patches that are being applied
3 votes -
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 -
Fix Patch superseding in detect only schedules
As per case 4747082:
If a Windows asset has new (non-superseded) patches installed and is scanned using a detect only schedule that uses a label containing superseded updates which have NOT recently been deployed to the asset, these patches are incorrectly detected as required.
Looking in the logs, it is evident that Kace calls dism to only look for the package in question and not packages that Kace knows supersedes it.
The result is that it is impossible to completely rely on detect only labels to generate reporting for accurate compliance.
3 votes
- Don't see your idea?