KACE Systems Deployment Appliance (SDA)
Please tell us how you’d like to see the KACE System Deployment Appliance product improved!
22 results found
-
Replication window for RSAs
Some of our sites are on low bandwidth data connections. Trying to sync multiple RSAs takes days as the syncs do not happen concurrently. As these tasks queue up, I am unable to do other K2000 tasks, such as driver feed updates, upload images, or recaching of drivers. If we could have a window for replication similar to the K1000 replication to network shares, this would improve efficiency in our environment and ensure our RSAs are more up-to-date.
275 votes -
Ability to apply K1 labels from the K2 as postinstall tasks
It would be beneficial to be able to leverage the label feature in the K1 at time of system deployment.
160 votes -
Slipstream Patches Into scripted Install
It would be very beneficial to have the K2000 be able to slipstream MS patches similar to nlite/RT7lite with all current patches. Right now a Windows 7 sp1 Scripted install has 170 patches pending from MS.
I see our K1000 as a maintainer of machines not an initial configuratior.123 votesWe’re looking at this after we get more K1000 synchronization built into the K2000.
-
Deploy Windows Updates automatically after postinstallation tasks
It would be nice if the K2000 would also manage Windows Updates (like the K1000) to deploy them automatically as postinstallation Task.
77 votes -
Custom Columns in Deployments area
Allow customers to change the width of existing data columns, add custom columns with pre-existing fields (i.e. date created, last date modified, last date used), and remove columns that customer does not need or want (i.e. hostname) all within the Deployments area of the K2000.
This would great help the organization of images, and the quick viewing of information for image rotation, updating, statistics, etc.
15 votes -
Add a Patch Feed for scripted imaging just like the drivers feed
Add a patch feed that you can subscribe to MS patches, adobe patches firefox ect and then apply patch feeds to scripted images so your images always come off the bench with the latest patching.
15 votesWe’re looking into extending the linking and integration abilities between a K1 and K2 and this would be one of the features we’d implement when that time comes.
-
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.
-
Allow IPV6
Please enable the ability to setup IPV6 networking, along with IPV4.
9 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 -
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 -
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 -
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 -
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 -
Prompt for Post install tasks during image processing
It would be nice to have the ability to get a prompt to come up and ask what other post install tasks need to run during the image process.
Use case: when a machine gets an image deployed, and on certain machines have a prompt come up and have any additional tasks be checked off to run after the OS is installed.
4 votes -
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 -
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. -
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.
-
SDA Multi Org Support for better SMA integration
SDA Multi Org Support for better SMA integration
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 -
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
- Don't see your idea?