KACE Systems Management Appliance (SMA)
Please tell us how you’d like to see the KACE Systems Management Appliance product improved!
79 results found
-
Customizable LM.Detection resource consumption
The KACE agent patch detection engine, under certain workflows, can be highly disruptive: pegging disk I/O, pegging CPU, RAM usage >1GB, and causing USB HID (keyboard) events to be dropped.
Currently the engine runs full bore, as fast as possible.
A beneficial feature would be customizable resource consumption for the detection engine to facilitate enhanced end-user experience for use cases when detection/deployment must occur during business hours.9 votes -
Ignore Client IP using REGEX or Mask for a range.
Ignore Client IP using REGEX or Mask for a range, to avoid insert many lines.
3 votes -
Ability to view archive from inventory-devices in the view by section
Able to look at archived devices from the devices inventory view
8 votes -
macOS Device Actions
With the introduction of the updated agent in version 9.0 that uses the agent to run device actions instead of the browser, it should now be possible to create device actions for macOS clients. Ideally this would be implemented in a way that would show device actions for macOS computers only on macOS devices, and Windows actions for those devices.
11 votes -
AHV
Display Nutanix AHV VMs as Virtual
9 votesWe are excited to announce that version 12.0 of the KACE Systems Management Appliance (SMA) is almost ready for the Beta/Release Candidate program. This release will contain initial Nutanix support for the SMA. Although this is not the specific UserVoice feature you requested, you have made a request related to Nutanix in the past; so we want to invite you to check it out. If you are interested in participating in the Beta/Release Candidate program, simply send an email with “Nutanix Beta” in the subject header to: kace_beta@quest.com and you will be contacted shortly with details. Thank you in advance for your kind consideration!
-
View Application & Windows Patch State on the Client
It would be a great idea to show the enduser the current state of the Patching Process.
The Enduser should be able to see which Application and which patch is currently beeing installed.
I have found some other ideas about this already but they all have been closed as "completed" but there is nothing like this in the current Version of K1000 8.1.
27 votes -
Fix Amp.conf File So It Doesn't Reconfigure
Our K1000 is not available when you are not connected to our network. So when laptops leave our network to do work at home the agent continues to try to check in. Over time, because the agent can't connect to the server, the amp.conf deletes out all the configuration data, and the machines stop checking in. We have over 200 machines that have this problem. We then have to track these all down and reinstall the agent. But since this continues to happen we are never able to really make much progress.
15 votes -
Detect per user installs
Some software installs only for the current user to avoid needing admin rights. It would be great if the agent could detect that and list it with the rest of the software, maybe by adding (username) at the end of the description to indicate it is only for one user.
2 votes -
Software inventory disks esclusion
We have many workstation with fiber connected storages.
This volumes are mounted in Windows as disks, but the storage hardware is shared among many clients.
When the inventory starts the multiple disk access made are killing the storage performance making user experience with software using these volumes extremely bad.On this disks we don't have any applications, just video files, so there is no need for the Agent to do a software inventory on them.
I would like to propose a disk esclution flag\rule to esclude specific disks from inventory scan.
Thanks.
Attilio6 votes -
Able to quickly see what computers are currently have a pending reboot for any OS or third party software
And to be able to use this information as a smart label.
I have an issue where I want to update Windows 10 and new servers to the latest Kace agent, but some of them are in a pending reboot state. If you push the new agent to them it will automatically reboot the system without warning because the msi reboot flag is tripped. If I could quickly tell if the device has a pending reboot and be able to use a label to limit it, I could avoid this problem.6 votes -
Possibility to manual upload agent bundle also under Appliance Update
Many customers have a hard time with manual updates.
The usage of the server upgrade kbin works fine but when they try to upload the agent kbin this fails.
So many SR are updated where support needs to point the customer to right location.
Even this is described in KB articles and the release notes this gives customers hard times.It would be great if the upload would also work over the manual update field or lead the customer to the right page if an upload has been tried.
9 votes -
Agent for AIX
The agent covers a good number of OS options, but AIX is not included outside of the SSH/agentless option.
4 votes -
Agent app on Chromebooks
Can we get a app in Chromebook that works like the amp agent?
7 votes -
configure Kace not to use the root of the C drive as a working area
Is it possible to configure Kace not to use the root of the C drive as a working area? It keeps adding and removing cab files there when it’s working, which is a pain when you have Explorer configured to expand the directory tree. It keeps appearing and disappearing from the tree. The name of the cab file causes it to appear at the top of the entries under the C drive, causing the entire tree to flicker and shuffle. This is both distracting and causes directories I’m trying to click to move around underneath the mouse. The path to…
11 votes -
Allow access to agent share after SMB Signature Required is enabled in AD
Once SMB Signature Required is enabled in Active Directory then the agent share is unable to be access. It would nice to be able to download the new agent without having to block smb signature and then have to enable smb signature again.
51 votes -
Bypass UAC while running scripts
This is a follow up ticket to continue tracking an add on thread to a ticket which is now completed:
http://kace.uservoice.com/forums/82699-k1000/suggestions/1637531-uac-compatibilityBypass UAC while running scripts:
Running scripts as System does not involve UAC. If running scripts as a User, UAC applies. That case is still under consideration for a future release.79 votesYou are encouraged to vote on this ticket that was split out for a previous (closed ticket) that contained two different suggestions.
-
Have agent update K1000 when IP changes
I have a problem where employees with laptops cannot get software from the User Console Library because the IP address from their last inventory (up to 4 hours ago) does not match the IP the K1000 web interface is seeing.
For example I have about 50 scripts in the library to automate the installation of printers in Boston, New York, LA, and Dallas. I have smart labels configured so that if you check in on the Boston, NY, LA, or Dallas subnets you get that site label. I then limit all the scripts for the printers in each site to…
205 votesThank you for your very thorough desciption of the issue. We will consider this as a feature request in the future. We prioritize based on feedback like yours – so we encourage others to vote for this feature request.
-
Better Mac OS X documentation for Kace Agent
I've found sadly very little documentation about using the Kace Agent on a Mac. I did find a list of all the runkbot commands for Windows and for a while presumed that this would be the same on a Mac. But I started to realize that this is not the case. Now, I've finally located support articles that show that runkbot 2 0 on a Mac runs inventory where the same command in windows is runkbot 4 0. But then what does 4 0 do on a Mac? And what about the rest of the commands such as 6 0?…
12 votes -
Agent Provisioning uses NTLMv2 to support Level 5 (NTLMv2 only Refuse LM & NTLM)
Presently the Agent Provisioning requires NTLM Level 0-4, if your environment uses Level-5 you cannot deploy the Agent via Agent Provisioning.
9 votes -
add ipv6 detection
add ipv6 detection at Network Interfaces in agent inventory
9 votesThank you for your input. We are investigating this and encourage others to vote for this feature/functionality if they think it would be useful
- Don't see your idea?