KACE Systems Deployment Appliance (SDA)
Please tell us how you’d like to see the KACE System Deployment Appliance product improved!
40 results found
-
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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.
-
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 -
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.
27 votes -
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 -
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.121 votesWe’re looking at this after we get more K1000 synchronization built into the K2000.
-
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.
14 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.
-
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 -
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
- Don't see your idea?