KACE Systems Management Appliance (SMA)
Please tell us how you’d like to see the KACE Systems Management Appliance product improved!
161 results found
-
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 -
Remotely clean up patch cache on endpoints
It would be nice to be able to be able to delete the cached patching files from C:\ProgramData\Quest\KACE\patches from the SMA console. Sometimes you need to clear that folder out to fix patching errors or detection issues with stubborn endpoints. Some sort of context command or action available from the inventory screen would be ideal.
18 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 -
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 -
CVE Rating
Apologies if this has been asked before.
It would be great to be able to see the CVE and CVSS score for a given patch.
This could then be used in a dashboard so you could easily identify where to spend your time most appropriately.I know a lot are often "under analysis" but it's a standard and I think would be beneficial.
11 votes -
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 -
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 -
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 -
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 -
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 -
Requesting foxit phantom pdf patch for updates on windows
Kace k1000 has Foxit reader and Foxit enterprise reader patches available. The same software publisher (Foxit) has another pdf product called "Foxit Phantom PDF reader" and these patches are not available. Our firm utilizes both applications, but as of now we cant centrally manage them both with kace patching. This will force us to have to script and test a MSI deployment to update phantom pdf reader; which is not as efficient as the patch management.
As of right now Foxit version 9.1 is only available via kace for foxit reader and not phantom reader as well.
*Patch Description
Foxit…7 votes -
Rerun patch schedules for only the devices that are offline or have errors
instead of rerunning a patch schedule for all devices, just continue to run the patch schedule on devices that are not completed or have errored out. If you have two schedules one that has no reboots and and one patch schedule with a reboot option. it should reboot the machine instead of bypassing the pending reboot status inorder to patch the missing patch
6 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 -
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 -
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 -
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 -
Allow for reboots before detect and deploy cycles
We have encountered many times when a user leaves for the day without logging out, rebooting, etc and as a result patches fail to install because an application is running. It would be nice to be able to say as part of a patch schedule "reboot prior to detection" or "reboot prior to deployment." In my case, I want the patch cycle to look something like this:
Run detection
IF patches are required, reboot prior to deployment (to ensure all applications are closed)
Deploy patches
reboot if reboot is requiredThere of course would need to be alert mechanisms for…
3 votes -
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 -
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 -
Alerts additional schedule option
With current version of K1000 it's possible to schedule deployments on patching on preselected dates like run on the first Thursday of each month, second Saturday, etc.
I would like to have same option for Distribution/Alerts. Currently there is no way to send alert remaining users to shutdown their programs ( like day before )
before updates will be executed on second Saturday of the month. You can only setup specific day or same day recurrence ( like every 10th day of month )
It will be great if both patching and alerts schedules can be run on same set…3 votes
- Don't see your idea?