KACE Systems Management Appliance (SMA)
Please tell us how you’d like to see the KACE Systems Management Appliance product improved!
77 results found
-
Add option to install at system startup
Right now the only managed install options are execute anytime, execute before logon, execute after logon, execute while user logged on, and execute while user logged off. There should be an option to install when the system boots and before the Ctrl+Alt+Del prompt is shown. Right now the "execute before logon" will install literally right before logon: the agent does nothing until someone presses Ctrl+Alt+Delete and then it starts the install, which causes a delay for the person sitting at the computer.
129 votesThis is under consideration but not planned for the next release, Please continue voting if you’d like to see this feature prioritized for a future release.
-
Single user based deployment
We assign installations to user based groups, to keep software persistent when users change machines. Would love to be able to add an individual user to an MI, much like adding a single machine.
5 votes -
Managed Install Scheduling
I would love to see the ability to set a more specific deployment schedule for the managed installs. Make it like the patch deployment scheduling where you can pick certain day(s) of the week, specific time of day, specific date & time, etc. We have many machines that can only have software deployed to them at specific times and this would help automate that process.
39 votes -
I'd like to have a way to reset the failed status and/or attempt count for an individual computer's Managed Install.
I'd like to have a way to reset the failed status and/or attempt count for an individual computer's Managed Install. Re-saving the MI resets for all failed, but I'm looking for a way to reset the count and/or failed status for individual computers. I'd prefer to not have to allow sub-admins the permission to save/modify MIs.
40 votes -
Limit Deployment To Listed Machines Manual entry
The Limit deployment list should accept a list of IP’s or computer names separated by returns. When I copy a list from outside Kace or inside Kace I should be able to paste it in notepad or excel manipulate it as I want then paste it to the a manual entry filed that will populate the Limit Deployment To Listed Machines filed.
This will be one new multi-line textboxes that will accept inputs. The textbox will be called manual entry above the textbox two bullets one labeled “by IP” the other “by computer name”. When you paste data into this…
37 votes -
Inventory automatically taken when any software or update is installed
It would be extremely beneficial to have any update or software install trigger KACE to take a new inventory.
17 votes -
New Managed Action for Managed Installations: Run Software-Installations before Shutdown like Windows Updates.
It would be great when i can trigger Installations after User has shutdown his Computer like the Installation from Windows Updates.
8 votes -
Installation possibility in User-Portal in "User-Context"
I am looking for a feature, that allows Software to be installed in "User Context". Currently, if a software is published in the software portal, the user itself can initiate the installation. The software is then pushed to the UserAgent and the service installs the software with its system account.
I am looking for the possibility to launch installations within the user context (to access HKCU or %APPDATA% from the current user account running this software). Background is that a distributed package (via software portal) or a software installation job could do things like adjusting the signature of the user…35 votes -
Smart managed installs that know if the installation has been patched
I would love it if I could have a managed installation (say Office 2010) that should automatically be installed on all machines. I also want to be able to patch the software to a newer version without the managed install trying to install the software again.
69 votes -
Create label groups for scripting & deployment purposes, not just organizational purposes
While there is an ability to create group labels in the K1000, these serve little purpose other than organizational purposes because the group label cannot be applied to a script which makes it basically useless. I would like the ability to create a group and then use that group however I want, just like any other label. Example: Deploy Script A to Building Z instead of manually selecting each label for Accounting, HR, Admin, etc.
30 votes -
Managed Install warning is worded incorrectly
When removing all labels/devices from a managed installed, a warning appears with "You have not limited this distribution to any labels or devices. Are you sure you want to deploy to all devices?" with the option to choose Yes or No. Choosing Yes does not push the install to all devices as the warning box seems to indicate it will. The install will not push to any devices.
My thought is no warning or a warning "you have chosen not to install to any machines" or something similar.
See case 3260078 for more details if needed.
3 votes -
Better configurability over Bandwidth Throttling
The K1000 lacks the ability to throttle bandwidth (other than within Replication Shares.) The bandwidth throttling from within Replication Shares is good, but that is the ONLY place that it can be configured. Having the ability to configure this for the whole KBOX would be a great feature. Things like maximum bandwidth utilization, maximum data transferred, etc.
98 votes -
Multiple distribution packages assigned to one software
The problem is that there are a lot of software applications out there that don't differentiate themselves once installed between 32 bit, 64 bit, or any of the OSs (i.e. 2003 vs. 2008) but have different installation packages depending on these items.
173 votes -
Bring back history managed distributions
Bring back the history at the bottom of managed installs.
3 votes -
Show Connected when reviewing status of managed installs
It would be great when you review managed installs to see why a machine did not install if the Connect icon showed. Connect and push now button would be great.
5 votes -
Internal way to preserve the checksum of a managed install
When updating a large .zip for managed installation, the checksum is removed when the file is placed in clientdrop (or when moved to the drop folder). When the installation kicks off, since the checksum of the file does not match the checksum the installation is expecting, the .zip is removed from the target PC. A Kace on-site implementation specialist had a brilliant idea: Use kdeploy -hash <filename> to determine the checksum. Then run a SQL query in the ticketing rules to apply that checksum to your .zip file. Worked perfectly. This could easily be included in the k1000 and would…
5 votes -
3 votes
- Don't see your idea?