KACE Systems Deployment Appliance (SDA)
Please tell us how you’d like to see the KACE System Deployment Appliance product improved!
42 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.
278 votes -
Role-based access control (RBAC)
Regulate access to various functionality based on user roles and permissions. This would include granular access to capabilities such as:
- Logon to KBE
- Access to specific production images
- Server/workstation roles
- Samba share access
- Differentiate between access to deploy images, and access to log into connected machines as an admin.
272 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.
163 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.126 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.
81 votes -
Object History tracking for security auditing
The KACE SDA currently has no way to audit changes made to any imaging-related objects, including:
- KBEs
- System images
- Pre/Mid/Post install tasks
- Task Groups
Coupled with the "all or nothing" approach to permissions in the SDA, this creates an information gap that results in a security concern: how do you know what object or setting change was made, when it was made, and who made it?
Consider the worst case scenario: a disgruntled SDA Admin on their final day at the company adds a malicious script or application to a post-install task.
The risks that come with the current model:
…
57 votes -
Improved RSA Administration
With 100's of RSAs deployed, changes to the configuration of a single typically results in hours of work--login to RSA, change configuration, rinse/repeat.
Ideally, I'd like one or more administrative templates that would allow me to control common settings (e.g., proxy, authentication, admin password, NTP, etc.)
I'd also like to script the reboot of a remote site appliance (think quarterly maintenance reboots). Currently, this process is administratively cumbersome even when performing reboots of each RSA (guest) via vCenter.
39 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.
-
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 -
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?
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.
-
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 -
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 -
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 -
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
- Don't see your idea?