We have a set of Windows images on Dell's ImageDirect site that would be nice to upload over to the K2000, either from the site, or via ISO files.

Have a pre-install task that will allow you to select an existing device from the SMA to apply the KUID as a post install task. When imaging an existing device with a new HDD/SSD the SDA has no KUID to grab so when the agent is installed it thinks the device is a new device. This causes an issue of having multiple assets that should be the same device asset.

When I switch between using a Windows 7 and Windows 8 scripted installation, I have to go and change the default boot environment (between WinPE-3 and WinPE-5) in the settings. It would be nice if the boot environment could be specified as part of the automated deployment.

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

It could be useful when the network configuration is not multicast compliant to use a peer-to-peer protocol (bitorrent) to deploy images.

the download to usb bootable is great. but with a 64gb usb stick it could store a bunch of images. All multiple images to be written to the same usb stick. Then create a very simple menu that prompts the user for which image to deploy.
Could have the install to usb installer create a simple inventory file to record which images on are the usb and in what folder, then simply build the menu from it.

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.

Have the KBE Driver packs available for install right from the appliance. Just click a button and then download and install.

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.

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?

Create a "retire" setting for KBEs, SIs, images, pre/post-install tasks, etc so they are preserved on the KBOX, but they don't appear on boot menu/post install list unless un-retired

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.

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.

With the upcomming of great resolution screens for example the Dell XPS 13 2015.
Which has a resolution of 3200x1800 on a 13 inch screen, the text font is very small, which makes it hard to read.
So the posibility of changing the resolution before the KBE booted up would be a great thing!

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.

Along with the idea of a customizable MOTD, I'd love to see a build in customizable or even basic wiki to add how-tos for new employees being trained to use our KACE system and to reference things and changed we've made.

When scheduling a label of machines (e.g. a classroom of about 50 computers) to automatically install an image adding the ability (ideally via a checkbox) to automatically restart those machines so they can begin imaging. Some machines may not want to be restarted immediately that is why optionally would be great.

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.