KACE Systems Deployment Appliance (SDA)
Please tell us how you’d like to see the KACE System Deployment Appliance product improved!
99 results found
-
upload custom config.xml file for USMT
K2000 - allow upload of a custom config.xml file to better configure USMT.
10 votes -
Delete USMT user state after successful deployment or on timer
Just paint this picture: 300+ Win 7 Clients are to be upgraded (scanstate, wipe+load, loadstate) to Win 10 using the SDA (and build in tasks). The list of possible user states to restore will be to long to click "Start Installation" after three or so upgrades.
Suggestion: Mark USMT user state as to be deleted after a successfull restore. On timer (once per night?) delete marked user states.
Possible plus: Add a checkbox to the USMT user state's details page: "Don't cleanup"10 votes -
Allow IPV6
Please enable the ability to setup IPV6 networking, along with IPV4.
9 votes -
Peer to peer deployment
It could be useful when the network configuration is not multicast compliant to use a peer-to-peer protocol (bitorrent) to deploy images.
9 votesThank you for your suggestion. This has been added to the feature request list. We encourage others to vote as we use this input for prioritizing our release plans.
-
Keep Bootable USB images on file and NOTIFY when completed
When creating images, the option to 'Create Bootable USB flash drive image for this System Image' takes a long time to build, with NO indication of progress and NO NOTIFICATION OF COMPLETION. It expects you to keep refreshing the page until you discover when it has completed. Am I the only person who despises being at the mercy of the refresh button? On top of that programming oversight, once you have download the completed image, it is deleted from the server and will not allow you to download it a second time? What benefit is there in that? Why are…
8 votes -
Allow Friendly Names for RSAs
Keeping track of which RSA is what on the SDA based only on IP is difficult. Allowing to rename RSAs to friendly names would help UX a lot.
8 votes -
PXE Boot supporting 802.1x authentication
It appears PXE 3.0 is capable of supporting 802.1x authentication.
Many networks utilize radius authentication to control users and VLANs. This is an issue with the current K2000 PXE since there is no option to provide credentials. I suggest an option be added to insert a username and password into the undionly.kpxe and ipxe.efi so that PXE Boot can authenticate.8 votes -
Allow RSA's to run network scan and transfer results to K2 appliance
Allow RSA's to run network scan and transfer results to K2 appliance
7 votes -
Multicast an image with multiple partitions
It would be great if it were possible to multicast to a hard drive with multiple partitions. In imaging our dual-boot computer labs we have to unicast the image which takes longer and uses more bandwidth. According to Dell it's a "software defect K2-5393", which In my opinion should be fixed.
7 votes -
Sort filters
I think the K2000 lists should all have configurable sort options. I organize my deployments by name, so I would like to see this breakdown of the images almost every time. I keep having to select to sort by name. I think the system should either have a memory or allow a default to be stored.
The following are example fields that should be sortable:
- Deployments
- Install tasks
- Inventory dropdown menu7 votes -
Dynamic updating of K1000 labels in K2000
The K2000 can pull inventory lists from K1000 labels for automated deployments, but those lists are static. If the label group changes on the K1000, the group does not update on the K2000.
For example, if I had a group of systems I want to re-image on a weekly basis. If one of the computers is replaced, the automated deployment must be rebuilt.
Can the K2000 re-sync label members on the fly or even on a schedule?
7 votes -
Credentials Management
K1000 has a Credentials Vault, could we also add Credentials Management to the SDA k2000, so that scripts or other scripts don't have hard coded username and password in post install task.
Credentials Management or a password vault for Post and PRE task would be great.
Thanks.
7 votes -
Can we include a delayed reboot option?
During post installation tasks processing even after a successful completion we may need delay before Kace engine reboots the computer especially if its the last task.
For instance, I have a .bat file that pulls an installation from the internet the Kace appliance will move onto the next task or reboot before it finishes.
Adding a timeout /t 30 will not delay the reboot.
6 votesThanks for your submission! The team is reviewing your request and will get back shortly.
-
Ubuntu 20.04 Support.
The former Debian Installer (known as 'd-i installer' in some circles) and the use of its "preseed" method of installing has been deprecated as of 20.04.0, and will no longer be used in Ubuntu releases from 20.04.1 and later releases, as it has been replaced by the Subiquity ("Ubiquity for Servers") installer.
This is why the ISO's name was changed from 'server' to 'live-server'. The Ubuntu 18.04 release was released in both formats and they dropped the 'server' version for the Ubuntu 20.04 release. Hence, there is no Debian installer version of the 20.04 ISO and the Quest KACE tool…
6 votes -
Highlight KACE Default-Tasks in Library
Per default, several pre-installation, mid-level and post-installation tasks exist on the SDA. When you start adding more tasks, it quickly becomes confusing which tasks belong to KACE and which are self-created.
I think it would be great if they were visually distinguished. At a glance, you would be able to see your tasks and the ones from KACE.6 votes -
Select post install tasks from KBE UI
It would be great to have all of the post install tasks listed in the KBE UI so that they can be selected at the time of image deployment. This would be easier than having to remember to edit a deployment before hand or being able to deploy the same image with different post install tasks at the same time.
6 votes -
syslog
Provide an option to send syslogs to a server (like a SIEM). I see it is planned for the next major release of the SMA. Is the same feature schedule for SDA?
6 votes -
Have the "SMA Agent" post-install task pull the installer directly from the \kbox\client share.
Have the "SMA Agent" post-install task pull the installer directly from the \kbox\client share. As it is now, the SDA user/manager must manually upload the SMA agent to the SDA's post-install repository, and remember to update it when the SMA's share gets updated with a new client. If the SDA pulled directly from the SMA's share, we wouldn't have to worry about keeping the installers in sync.
6 votes -
Basic SNMP configuration...
Basic configuration, such as system location or system contact, for SNMP is not available to the end user. Many SNMP monitoring tools pull this information and map devices using this information. This information can be provided in the /usr/local/etc/snmpd.conf however the end user can not edit this, so options might be to allow this information to be added in the konfig stage of the install or when going into the Security Settings/General Security Settings and putting a check mark in Enable SNMP Monitoring other fields can open (besides SNMP Community String) for syscontact and syslocation. Once saved this information can…
5 votes -
Allow audit mode when creating an image
When doing a scripted image, it will be helpful to put that image into audit mode automatically so you can more changes to it before syspreping it again.
5 votes
- Don't see your idea?