Please add Windows 11 Deployment support to KACE SDA (K2000) ASAP.

Way to tell USER STATE of same user but different settings.

if some how the template being used or a different name could be given it would help.... we have two setup here.... i copied the user state for one setup previously and just copied the the same users' state for a different setup.... beside date created and note in SDA there is no way to tell the difference

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.

Add the same Progress section that is in the SDA to the RSA which will allow you to monitor progress if imaging off the RSA

Add Progress section in the RSA similar to SDA where you can see the build in progress straight from the RSA.

Add Progress section in the RSA similar to SDA where you can see the build in progress straight from the RSA.

It would be nice to go back over a deployment to see how much time elapsed per task to troubleshoot or optimize.

KACE recently added the Add Task Start and End Times to the deployment details page of each deployment. Two additional columns that could be useful are task start and task end time.

The current version of the Driver Feed Builder v3.0.0.0 uses an embedded version of 7-Zip v9.2. The current stable version of 7-Zip v19.00.

The current embedded version v9.2 is flagging in our enterprise anti-virus solution due to vulnerabilities in that version. Suggest replacing with current version v19.00 at a minimum.

Should take a minimum amount of time to provide this update in the next version of the Driver Feed Builder application.

The current version of the Driver Feed Builder v3.0.0.0 uses an embedded version of 7-Zip v9.2. The current stable version of 7-Zip v19.00.

The current embedded version v9.2 is flagging in our enterprise anti-virus solution due to vulnerabilities in that version. Suggest replacing with current version v19.00 at a minimum.

Should take a minimum amount of time to provide this update in the next version of the Driver Feed Builder application.

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.

SDA Multi Org Support for better SMA integration

K2000 Settings - Control Panel - Linked Appliances

Add a singe field to the linked appliance records called "Description". Apart from the hostname (which in many instances is just an IP address) there's no way to identify the various linked appliances.

Thanks!

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.

Progress > Manual Deployment Progress >
Show IP & MAC Address in list as columns.

Please enable the ability to setup IPV6 networking, along with IPV4.

I would like to be able to configure a deployment from a client computer in an automated way for a new computer:
* with autopilot installation of the Kace agent
* the kace agent :
* install a local kbe
* configure a deployment
* reboot the computer on the local kbe and start the deployment.

Maybe the use of a token like for the SDA could be used to validate the request.

Add support for NAC

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.

Many of my RSAs are in locations that have VERY limited hours I can use max bandwidth. Why can't there be a calendar setup like the SMA where I can specify what hours of what day of the week sync'ing can occur? I have to manually start/stop sync'ing as there's not enough granularity in scheduling the sync. Why can't we have the low/high bandwidth settings just like the SMA? I spend WEEKS, not hours trying to sync my RSAs.