KACE Systems Management Appliance (SMA)
Please tell us how you’d like to see the KACE Systems Management Appliance product improved!
10 results found
-
Add option to disable task skipped task pop up
I opened a ticket and was told that the 11.1 update included an "enhancement" that added a skip task notification. If you're going to add a notification you need to an option to disable it too! My end users don't need to know if a task was skipped and all it did was cause more tickets to my helpdesk. Please add an option to disable this "enhancement". Thanks.
41 votesunder review ·AdminKent Feid (Director of Product Management | Data Protection & KACE Unified Endpoint Management, Quest KACE) responded
We have heard your voices and understand that for many, this message proved to be disruptive. As such, we disabled this notification in our 12.0 release and will look at adding it back as an optional setting as part of a future release.
-
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.
25 votes -
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…
92 votesThank you for your suggestion. We encourage others to “vote this up” to help prioritize it for future releases.
-
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.…
449 votesThis feature request is under review. We encourage others to vote for it to be considered in a future release.
-
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.
70 votesThank 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.
-
Update BIOS that has a password
In an enterprise environment it is common practice to have a BIOS password to stop users accidentally/deliberately accessing the BIOS and making changes that would affect the operation of the computer.
It appears that Distribution/Dell Updates cannot update a BIOS if it has a password set. This means that I have to go to ~1000 computers and upgrade the BIOS manually which is an extreme waste of time when KACE was purchased to do that sort of stuff automatically and it can't update a Dell computer's BIOS.
242 votesunder review ·AdminKent Feid (Director of Product Management | Data Protection & KACE Unified Endpoint Management, Quest KACE) responded
As previously announced, we adopted a new Dell Updates framework starting in the KACE Systems Management Appliance (SMA) release 11.1. This change was triggered by Dell’s plan to end of life the framework previously used by KACE. This new framework developed by Dell is supposed to bring additional capabilities as it matures. We are keeping a close eye on these incremental improvements made by Dell and are hopeful that things like mass passing of passwords will come in time to develop against.
-
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…
141 votes -
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 -
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.
45 votes -
Smart Label patches on type/category
Let it be possible to also create patch lables on the criteria WHICH category it belongs to.
Example: Smart Label which only contains Service Packs for Windows 7.
MS is using this "form" in their WSUS solution. See screenshot.20 votes
- Don't see your idea?