KACE Systems Deployment Appliance (SDA)
Please tell us how you’d like to see the KACE System Deployment Appliance product improved!
50 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 -
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 -
Detach the image media from the image deployment job
The idea is to have the same process for the Imaging that the scripted installation. Then the image captured will be stored in the media Library and not in the deployment image tab. To create an image deployment job, we will select the image in a dropdown list.
164 votes -
Be able to restore the K2000 database
I just found out that you can not restore the K2000 database even though you can backup the K2000 database. I want to be able to have all my settings if there is a catastrophic failure with my server or just need to refresh the hardware. I have to recreate all my labels, users, Ldap authentication, all my general settings, date time settings, relink all of my RSAs and K1000.
146 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 -
70 votes
We’d like to improve schedulling and automated tasks across the board on the K2000.
I’m not as enthusiastic about supporting user state migration to non-K2000 storage. The advantage of the K2000 is that everything’s centralized. We already have export of user state in 3.3. If the problem is not having enough native storage on the K2000, we’ve heard that loud and clear.
-
Start post install tasks manually on a client for testing purposes
It would be great to have an option to start the post install Task process on a test Client that has already the OS installed, so you don't have to run a full scripted install every time you want to test a postinstallation Task.
63 votesThank you for your suggestion. I have put this in our product feature backlog. Please vote for this feature if you are interested so we can move it up the priority list. If a workaround is discovered, it will be posted here.
-
Capture Full Backup of SDA
Currently, backups are only done if a change to the item being backed up has occurred. This is incremental behavior. We should have the option to specify this behavior (via checkbox, for example).
What I would like is the ability to do a full backup of everything at will - scheduled or otherwise.
An example of a problem arising from the current solution is this: empty the Restore share and then try to back everything up. You cannot. If you offload your backup and then lose it, you cannot make another full backup.
Ideally, everything would be rolled up into…
39 votes -
Join multicast session from KBE
Right now, there doesn't appear to be a way to join a multicast session from the KBE. This would be very helpful if we get a new shipment of PCs in, and set them all up. Then, we just tell the K2 to start the session and wait for 30 clients. This way we don't need to harvest mac addresses before hand... We can just deploy.
37 votes -
Different boot manager password for each RSA
Currently, you can specify a "Boot Manager Password" on the K2000 and it is used on every RSA. I'd like to have different passwords for each RSA. Maybe on the K2000 under Deployments > Remote Sites > (select the RSA) then have a checkbox to override the default "Boot Manager Password" and enter it there.
17 votes -
Dynamic MAC & Host Name querying between K1000 & K2000
Auto-populate Host Name of machines in K2000 System Inventory via K2000 query of MAC address in K1000 Computer Inventory.
17 votesWays to unify the identity of machines on the K1000 and K2000 are on the roadmap, and some have been implemented in 3.3. Unclear if MAC address is reliable enough to assure identity, what with ARP issues and the like, but we’re looking at ways to make integrated appliances work better together.
-
Kace agent automatically install on the K2000 as a post install task when new updates come out
Wouldn't it be great if when a new agent update came out on the K1000 that you wouldn't have to manually update your post install task for the agent on the K2000.
16 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 -
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.
-
upload custom config.xml file for USMT
K2000 - allow upload of a custom config.xml file to better configure USMT.
10 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 IPV6
Please enable the ability to setup IPV6 networking, along with IPV4.
9 votes -
PXE Boot supporting 802.1x authentication
It appears PXE 3.0 is capable of supporting 802.1x authentication.
Many networks utilize radius authentication to control users and VLANs. This is an issue with the current K2000 PXE since there is no option to provide credentials. I suggest an option be added to insert a username and password into the undionly.kpxe and ipxe.efi so that PXE Boot can authenticate.8 votes
- Don't see your idea?