KACE Systems Deployment Appliance (SDA)
Please tell us how you’d like to see the KACE System Deployment Appliance product improved!
40 results found
-
Using KBE to gather and deploy USMT
It would be nice to be able to use USMT on hardware that is not on the domain of your SDA.
Use case:
Organization acquires another company and we need to gather existing profiles from dissimilar hardware/domain.It'd be nice to be able to boot to KBE on an external drive (SSDs are super cheap these days) and use KBE to gather local profiles using SDA tasks to that external drive, then import them into the SDA for new asset imaging.
Going one step further, we could use the KBE with offline images to gather the USMT, and do an…
3 votes -
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 -
Driver Feed - automate install into appliance of models in inventory
You guys have an inventory of device "model" for network booted devices. It would be great if there was an option where this information could be used to automatically enable/install Dell Driver Feed drivers into the SDA. With options of drivers for which OS (i.e. I only want windows 10 x64 drivers), and some kind of threshold option (like maybe 3 same model in inventory before auto enabled/installed).
Inversely maybe an additional option to delete drivers when there are 0 of the model/s in the SDA inventory (maybe in a specified period).
3 votesThank you for these feature requests!
These sound very interesting. The retention concept for drivers that aren’t needed sounds great.
We will review these further and determine their place within our product backlog. -
SDA Multi Org Support for better SMA integration
SDA Multi Org Support for better SMA integration
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.
-
Having a git like task repository
several of us are working on deployment tasks. It would be convenient to be able to manage these tasks through a git repository (or other cvs, svn...) in order to be able to follow the changes made by colleagues.
3 votes -
Add Support for Xen Hypervisors
We run our KACE appliances in a very open source shop, so the current hypervisor options are less than ideal. We would like to see support for KACE appliances on Xen based hypervisors, especially XCP-ng. (The XCP-ng folks are awesome to work with, KACE engineers!)
3 votes -
Direct editing of USMT XML files
In order to capture and deploy some of the custom data we have we need to modify the miguser and migapp xml files for the USMT tool. It would be nice to be able to edit this directly on the appliance.
3 votes -
SDA data visibility outside of appliance
The SMA (K1) has the ability to query and view all kinds of information using SQL, API, and the KACE GO app. I would like to see this same kind of visibility added to the SDA. When imaging a batch of computers, I'm not always able to sit there and make sure everything works. Using my phone to log into the SDA web interface is very cumbersome. Making this information more readily available and easier to access on the go would be a big benefit.
3 votes -
Sync images captured on RSA to SDA
Version 5 finally allowed users to capture images to the RSAs. We're on version 6.1 now and are still unable to sync/replicate those images back to the SDA. In K-12 education, we use shared images across all our sites. The ability to capture images anywhere is great, but what's the point if you can't share that image with the rest of the sites? We have 23 RSAs. Being expected to export/import these images is absurd.
3 votes -
Enable to "kill" a blocking sync task
We have been facing a lot of situations where the sync queue was hanging and therefore the whole appliance is useless as nothing can be done anymore. This always requires calling the support which causes workload for the support, the customer and wasting time, cause the only thing Support will do is kill the hanging process. If there would be a "button" to kill the "current hanging" task it would be beneficial.
Example: RSA replication hangs because of new version has been installed but no version check, if the "nightly sync" task hits that rsa the whole queue is stuck…
2 votes -
Split task queues for replication
Please make the "nightly sync" queue run multiple RSAs in parallel, or at least adjustable. We are running 200 RSAs and if one of them for whatever reason is blocking delaying the sync the whole queue gets into a backlog. Then it is hard to get it synced without manually interacting and canceling and pushing multiple RSAs at once.
As it is possible to run multiple syncs manually triggered in parallel it should not be a big deal to also make that work for the build in queues.
Same applies at days when we need to inject new drivers intro…
1 vote -
Ability to remove Images captured on an RSA from the main appliance
We can now upload to RSA's but have to get support to remove failed images.
1 vote -
Custom Schedule to Export Packages
Could we have more options for the schedule export of packages? We are looking at schedules such like:
A. on a monthly schedule i.e. the last day of the month or 15th of the month
B. biweeklyI understand that the ability to create a custom schedule is available on the K1000.
Thank you.
1 vote -
Deployment-Wide, Deployer-Defined Variables
Would like the ability to create user-defined variables within a deployment definition (Scripted Installations, or System Images) that are valid for the entire process of deployment. These variables would be held by the K2000, not by the box being imaged.
Example:
As a pre-install task, I could determine the BIOS version of the box being imaged, and store it in the variable FIRMWAREVER, and then at any point subsequent, in a later pre-install task, or a post-install task, I could call %FIRMWAREVER% and have that information. This way I don't have to store it on a temp RAM…1 vote -
Have the possibility to create a bootable usb key for Ubuntu / Linux OS ?
As is the case for Windows pre-boot environments, being able to create bootable USB keys for Ubuntu / Linux OS.
1 vote -
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 -
enable / disable a post install task from executing
if one has the same post install task in 10 scripted images, be able to enable / disable them all at once. for example, a new post install task needs to be created; however, the implementation date is unknown. I can add the task to the 10 scripted images - at my leisure, then when i need to enable the task - it is one click. Be able to enable / disable a task from executing
1 voteThank you for this feature request!
It’s interesting to consider the prospect of viewing the details of a PO task and seeing all the deployments to which it’s linked. With that view available, one could execute an action en masse rather than individually.
We will review this request and determine its place within our product backlog.
-
Detect which "Source Media" and which KBE "Is actually in use"
In a bigger environment it happens that multiple administartors are creating KBEs and injecting Source media. After a while that gets messy and needs a cleanup, but Kace does not offer any option to easily identify which are in use and which are just left overs. There is a marker for "default" but that is all. Would be really helpful to see "used" or "unused" Source Media or KBE.
1 vote -
Ability to import a CSV with MAC addresses to create automatic boot options for devices which were never booted
Right now it is nessesary to boot all devices once to have a network inventory to setup automated boot options.
Better way would be:
Import a CSV with all MAC addresses of the newly delivered devices to create automated boot actions to fully automate the process.0 votes
- Don't see your idea?