KACE Systems Management Appliance (SMA)
Please tell us how you’d like to see the KACE Systems Management Appliance product improved!
70 results found
-
Updating scripts executed in real time
I have to wait for the script to complete to identify the problems in the installation
1 vote -
LDAP labels should reflect what is really in Active Directory. When you test an LDAP label you get an accurate count. Not so in Devices.
If you use a script to access an LDAP label, you don't get the devices listed in your Active Directory, but those in the K1000 instead. These can be wildly different.
1 vote -
Make "Name:" field wider in Task Chain Tasks, and add Notes Field
When adding a "Scripts" Tasks in "Distribution/Task Chains", the field name after creating the task is often too short to see the full name of the task.
For example, I've got numerous scripts named "2018-Mac - Install blah blah blah", and if I chain three or ten of those together, all I can see at a glance is I've got ten scripts named "2018-Mac - Insta....".
Make the field wider so I can see more of the name.
Also, add a Notes field to each task; a year from now I'll have no idea why I'm copying a Mac user's…
1 vote -
Run a script in run now status with the logged in person running the script to find out who does what.
today for check who executed a script we have to do this:
- Settings › History › Object History > view by : Script and check the execution time and compare it with the "run now" status in : Scripting › Run Now Status.then check who is the user who performed the task.
Would it be possible to have the user directly execute the script in the execution status of the script.
1 vote -
Run a script in run now status with the logged in person running the script to find out who does what.
today for check who executed a script we have to do this:
- Settings › History › Object History > view by : Script and check the execution time and compare it with the "run now" status in : Scripting › Run Now Status.then check who is the user who performed the task.
Would it be possible to have the user directly execute the script in the execution status of the script.
1 vote -
Task Chains
It would be nice if on the Scripts, Patch Schedule, and other pages, we could see if those items are already included in a Task Chain by some sort of "flag" in the listing. If multiple people are using your SMA, it's possible they might modify a script or patch job not realising that it is part of an existing Task Chain.
1 vote -
Accurate execution status for Linux Online Shell Scripts
Currently as long as the script is pushed succesfully to the managed device, the server considers this a successful run. It would be very useful if the server was able to determine when a script exited with errors so we can see which particular machines failed to execute correctly so we can perform manual remediation.
1 vote -
Ability to Patch Script without listing label or device.
When saving a Patch Script, you must specify a device label or device name. For testing purposes, there should be a way to save the Patch Script and then later add label or device.
0 votes -
Disable Scripts/not visible to be run
When we disable scripts we need it to not be visible to be ran by our tech's. Also if it is disabled it should not be executable that defeats the purpose of being able to disable a script. We would also like the ability to archive scripts for historical purposes for record of what was previously available.
3 votes -
Script outout in a report/attachment
As an Linux administrator, I find kace as a very useful tool when I want to deploy scripts on multiple servers. However I find very difficult to get the output logs.
Please make a progress to get the script output in a file, that can be well utilized to get the command/script output report.1 vote
- Don't see your idea?