KACE Systems Deployment Appliance (SDA)
Please tell us how you’d like to see the KACE System Deployment Appliance product improved!
97 results found
-
It would be nice to have something that cross references patch exit codes to a description of what the code means
This could be as simple as a table where a user can enter some patch exit codes and what those codes refer to. This would be a time saver when looking through patch failures to determine the cause instead of having to look up the codes on a regular basis.
3 votes -
Update all RSA Settings
I have several RSAs. Whenever I add a new image I have to go into each of them to check the box (and uncheck the old one). It would be great to be able to update them all at once.
1 vote -
Have RSA's replicate in Parallel.
It is ludicrous that it takes up to 6 days to sync 60 RSA's when there is a driver feed update. The fact that the SDA only syncs the RSA's concurrently slows the process way down.
3 votes -
Windows Server 2022 Deployment
Please add Windows 2022 Deployment support to KACE SDA (K2000)
3 votes -
stop process
can we add a cancel image upload or kill upload process option on the SDA for system images. i recently ran into an issue where kace failed to capture my image and the SDA was stuck on "Finalizing image". the only way i could stop this process was to reboot the SDA. after the reboot the status changed to "interrupted because SDA was rebooted" and then i deleted it.
1 vote -
Driverfeed no longer works with VMs
This used to work on version 8 and prior. It does not work on version 9. Quest has redefined driverfeed to search for the machine ID, which is not available for VMs. They assign a code for the machine ID to a directory name, such as "0a3e". The machine ID is retrieved using "wmic baseboard get product". For a VMware VM "440BX Desktop Reference Platform" is returned. Surely they could key off that to identify that it's a VM. Also, since the PXE platform has VMXNET3 drivers, they can detect whether those are in installed and active. The same is…
2 votes -
When upgrading the SDA from 8 to 9, please copy the driver feed drivers from the old location to the new one?
We upgraded from a late version of 8 to 9.0.144. I found that none of the drivers in the old location (driverspostinstall\dell\windows10x64) were copied to the new location (Z:\driverspostinstall\windows\10\x64\any\dell).
I didn't find that out until yesterday while working with support to discover why driverfeed wasn't working for VMware machines (that's another issue).
2 votes -
Windows 11 Deployment
Please add Windows 11 Deployment support to KACE SDA (K2000) ASAP.
3 votes -
Support for ARM Appliances
It would be amazing for there to be support for ARM architecture, opening up the possibility for appliances on hardware such as Raspberry Pi's and other low cost and easily deployable devices.
3 votesWe'd love to hear more about what types of ARM devices, and OSes the community is deploying.
-
Progress Section
Add the same Progress section that is in the SDA to the RSA which will allow you to monitor progress if imaging off the RSA
3 votes -
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 -
Add Task Start and End Times to Deployment Task Details
It would be nice to go back over a deployment to see how much time elapsed per task to troubleshoot or optimize.
KACE recently added the Add Task Start and End Times to the deployment details page of each deployment. Two additional columns that could be useful are task start and task end time.
3 votesThanks for this feedback - we'll talk to the dev team and see where this addition can be added into the backlog.
-
Update the embedded version of 7-Zip in the Driver Feed Builder Application
The current version of the Driver Feed Builder v3.0.0.0 uses an embedded version of 7-Zip v9.2. The current stable version of 7-Zip v19.00.
The current embedded version v9.2 is flagging in our enterprise anti-virus solution due to vulnerabilities in that version. Suggest replacing with current version v19.00 at a minimum.
Should take a minimum amount of time to provide this update in the next version of the Driver Feed Builder application.
2 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 -
SDA Multi Org Support for better SMA integration
SDA Multi Org Support for better SMA integration
3 votes -
Add a field to the linked appliances list
K2000 Settings - Control Panel - Linked Appliances
Add a singe field to the linked appliance records called "Description". Apart from the hostname (which in many instances is just an IP address) there's no way to identify the various linked appliances.
Thanks!
1 vote -
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 -
Progress > Manual Deployment Progress > Show IP & MAC Address in list as columns
Progress > Manual Deployment Progress >
Show IP & MAC Address in list as columns.0 votes -
Allow IPV6
Please enable the ability to setup IPV6 networking, along with IPV4.
9 votes -
Disable "capture image" option from RSAs
We should have a option to disable or hide the "capture image" from RSAs. For security reasons, we do not need other RSA locations to create their own images. Plus, since Kace already has issues capturing devices from RSAs (if not linking them by IP address), then the image fails and we're unable to delete the failed image from both the RSA or the SDA. We just recently had this issue and had to submit a ticket for Quest support to fix it via tether.
4 votes
- Don't see your idea?