As Hp also has started to distribute famy cab driverpacks, it would be nice to be able to symlink the different folders to one folder containing the whole family of drivers. for instance the Elitebook 745 G2 Utilizes the same driverpack as the 725 G2 , but we have to copy the drivers from one folder to another for the drivers to install.

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.

3.6 removed the Boot Action "Boot From Local Hard Drive" and number of boots. With these a default action could be set with number of boots set to 0 per machine. And when another boot action was used, default could be returned by chaining boot actions.

I do not want to default all machines to "K2000 menu" or "hard drive" boot (General Settings > Default Boot Action). While I do like this option and think it is great, there should be the ability to override it per machine (and hopefully be as visible as boot actions tab).

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.

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.

It would be great if we had the option to name a manual deployment. That way when multiple deployments are kicked off we can follow which is which.

Be able to click on a KBE in the K2000 and see what Dell supported workstations they will work on. Having the driver report is nice, but having to search for the actual network driver for the machine I am working on is a pain. Being able to see the model and OS the KBE would speed up this process.

Issue: If MS BitLocker is enabled on the Client Computer, then when the BIOS hands off the boot process to PXE via the NIC and 'times out', then boots to the HDD, after it hits the pxe boot menu, this will trigger bitlocker.

Solution: I need a way for the BIOS to hand control off to PXE and once the PXE option menu is encountered and it defaults to the HDD, but w/o this process triggering MS bitlocker drive encryption.

If I create a new image and I want to sync that out to all my RSAs, it would be nice to have an option to add that item to sync to "selected RSAs" or "All RSAs" instead of having to add the image individually to each RSA, which is painful when you have 10+ RSAs.

Like its possible on K1000

It would be nice to have Scripted Installation support for the XPS13 and other ultrabooks that do not have an ethernet port.

A progressbar will be handy when exporting packages because it can take a long time to complete. Now the K2 only says that he is currently exporting.

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

I would like to see the ability to exclude files from being included in a k-image such as pagefile.sys and hiberfil.sys to allow the images to be smaller

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.

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.