If i'm rebuilding a computer the Kbox should rename the computer correctly based on the information in the K1000. The old scripts are klunky. Maybe just a simple database/SOAP query to the K1000 for basic naming.

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.

Add Dell Diagnostics or memory testing to the KPE recovery options.

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.

It would be more practical to link tasks (pre-install, mid-install, post-install) to a deployment rather than an image. We are several people to deploy the same image but we use different pre and post-install tasks... If each person changes the tasks for each deployment of the same image we risk to have conflicts...
Actually we duplicate the image to have different tasks but it's not a good solution because the same wim stored many times on the K2000 Appliance.
Another solution would be to just duplicate a link on the wim file and not the entire wim.

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.

To scan user states with USMT from the K2000 web UI, SMB v1 must be enabled on the client pc. Support has confirmed this. There are known vulnerabilities with SMB v1 and most network admins have disabled it in their environments. Please provide support for newer versions of SMB.

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.

Ability to not only create a directory as you can now and populate it one file at a time, but actually upload whole directories including their files into system images.

Having the ability to modify the post install tasks in each deployment separately so that it is not required to create multiple versions of a single script, or to re-script and replace the post install every time you want to change it. Basically, post install tasks able to accept parameters assigned in the deployment detail page.

This submission is to vote for the addition of SMTP authentication to the K2000. Currently you can only supply the server name or IP with anonymous authentication. This would be helpful for users with email systems that require authentication - such as Office365 shops.

I'd like full support for snmp so that the k2000 can be monitored for issues. Also full dell open manage support on the appliance.

Allow user to either choose to sync all driver feed items from the K2000 appliance or instead not sync those files and make the Remote Site Appliance Driver Feed available to choose specific models to download drivers to the RSA.

Having a Xenserver Remote Site Appliance, or an ISO available so customers can install the appliance on their virtual environment.

We currently use our Mac hosted Netboot image as a imaging and Disk First Aid emergency repair netboot. Unfortunately the K2000 will not allow custom netboot images to be uploaded, and the application K-Image cannot be run outside of the K2000 hosted image.