KACE Systems Management Appliance (SMA)
Please tell us how you’d like to see the KACE Systems Management Appliance product improved!
161 results found
-
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 -
Ability to prioritize a patch schedule without having to kill all tasks
We need the ability to reprioritize a task without having to kill 1000s of other tasks to run one task.
0 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 -
Reminders for On-Demand patches before Auto Install
The pop up for On-Demand patches is very subtle. It would be nice to have a reminder pop up every so often and remind/nag the user to install their patches before the automatic timeout.
Also, being able to add custom text to the notification would be very helpful as some of our users are unaware of what Kace is and being able to provide assurance that this is a legit process would be very helpful.
1 vote -
Built-in support for patching linux OS
built-in support for patching linux OSm just like for Windows
1 vote -
Reboot notification counter
We'd like to see a counter in the reboot reminders so users know how many more times they can snooze - in both Software/OS and Dell patching. In addition, if the last message can be set to be different from the other reminders.
12 votes -
Clear progress message in patching
When setting up a patching schedule, you can set a progress message to be displayed when patching is in progress on a computer. Currently, this box has no OK button to close it. I propose adding an OK button to allow users to close the box.
1 vote -
Identify Software Inventory, or Software Catalog, items that have patches in the catalog.
Identify Software Inventory, or Software Catalog, items that have patches in the catalog.
3 votes -
Allow users to patch from the user portal.
I would like to allow users with laptops to patch at their leisure since they might not have their device powered on at a scheduled time.
9 votes -
Retry on Patching Error
When a client losses connection during the patching process which can be long in some cases it tells me "error (agent disconnected)".
Can you please provide a retry or that the client continues and updates the status once the connection is on again.15 votes -
Improvements to Patch Subscriptions
I would love to see additional options for patch subscriptions. For example, we run the KACE agent on Windows Servers for Replication repositories but we manage the patching separately for our servers. I would like the ability to choose only Windows 10 Pro 64bit and not have KACE show patches in the catalog for Windows Server. Additionally, I would like the ability to choose which version of Windows 10 patches to be downloaded. Say my environment is running on 1903, 1909 and 2004 for example. I would like to choose only those versions of patches to be downloaded. This would…
1 vote -
SMA with Proxy in DMZ
We want to patch machines that are not on the network but are connected to their wireless at home. This will help with patching compliance. However, I'm told this can only be done by having our internal SMA public facing. This isn't best practice and we'd to have it point to our proxy in our DMZ. I was told this setup isn't currently supported.
6 votes -
Bring back the view to show ALL patches installed on a device
You used to be able to view ALL patches installed on the device until patching changed to Quest and OS is 2016 or Windows 10. Now the view doesn't show anything more useful then the Installed tab. Wish they wouldn't take features away and require you to enter ideas into user voice.
1 vote -
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 -
Allow more flexibility to patch quarterly. Even custom schedule does not allow...
Today it is not possible to patch or at least easy to patch on a quarterly schedule. For example, "every 3 months, on the 3rd wednesday of the month at 2am." I think its doable if you say "every 3 months, on the 17th of the month at 2am". Patch schedules are based on freebsd cron which does not allow all characters. One cron site allows it this way "0 0 2 ? 1/3 WED#3 *" but Kace does not support the "Wed" or "?" characters. Also It would be nice to be able to view the "task schedule" beyond…
1 vote -
Support patching "Microsoft Windows 10 Enterprise for Virtual Desktops x64" OS
Allow patching "Microsoft Windows 10 Enterprise for Virtual Desktops x64" OS via KACE
9 votes -
Add Patching actions to API
The ability to start and get the status of patch jobs with the KACE API would be incredibly useful to help automate our patching process by being able to invoke and monitor patching with PowerShell rather than having to manage patching from the UI.
12 votes -
Allow additional scripting to be run as part of Windows Feature Updates
The Windows Feature Update installation capability in Kace SMA is a great feature. It would be made even more powerful if additional scripts could be included with the deployment and be run after successful application of the Feature update, such as a powershell script to remove the bloat apps and to reactivate Windows (especially for virtual desktops). This is achievable already by using a separate script job and utilizing smart labels, however if it could be programmed into the Feature update process it would be fantastic.
11 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 -
Provide setting to allow Superseded Patches to be Inactivated after a Delay of 30 Days
Currently we patch all Test/Dev servers following MS Patch Tuesday with all current patches.
We then patch all Production Servers with those same patches 1 month later.
Since Microsoft Supersedes patches every month, causing the patches from 1 month to be superseded before the Production Servers get patched, and we tell SMA to Inactivate Superseded Patches, they never get installed on Production Servers.
If we could have a setting to delay the "Inactivate Superseded Patches" for 1 month or any number of days, we would then be able to patch our Production Servers 1 month behind our Test/Dev servers and…
6 votes
- Don't see your idea?