instead of uploading the drivers to the smb in the appliance, just extract them to a folder locally and point the media manager to it.
this will save time and also avoid samba concurrent connections issues.

We use Rapid7 to scan our network for security vulnerabilities. As of version 7.2.97 on the K2000, the vulnerable and deprecated SMB1 is still present.

Please build the Kace SDA/RSA Virtual Appliances with the 7.1.94 update. As the current 7.0.357 contains a bug that does not allow RSA creation across subnets. Currently, I have to build an RSA with the wrong network settings, then update the RSA to v 7.1. Then change the network settings again. This is very time consuming and cumbersome to do.

Please Provide a 3 TB Hyper-V VHDX for the K2000

Add a Check Box to download and install new updates when checking for drivers under driver feed, or add a function to automatically check and down new drivers Daily, Weekly, Monthly.... etc...

It is a pain having to click on each model and then download the driver manually.

As an admin, I would like to be able to get an email notification when an image or scripted install job completes, as well as what the outcome of the job was (successful/failed/partial).
IN addition to success/failure status, it would be nice to have a link to the log file if it did file to see why a job failed.

Ever since 6.1, when deploying an image we just get a red bar that constantly scrolls. In the older versions it was an actual progress bar that showed which files were being copied and estimated time remaining. This is useless as a progress bar because if a deployment is taking a long time, we don't know if it's just slow, how long is left, or if something is wrong. Terrible design, please go back to the way it was, or give an option.

Popup or where we "alert" license expiry show a popup message when a new driver in the Dell Driver Feed gets updated for "Download and Install" Example, Dell Precision 5510 gets a new video driver update that I am maintaining, when I log into the console a popup at the top tells me it has a new update.

All the most popular switches are handling IGMP instead PGM. Please, KACE, go ahead with IGMP support for K2000.

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.

There are scripts to capture the name for a windows machine you are deploying via an onscreen prompt, but for Mac the only option is to have it grab the existing name of the machine. We join our macs to our domain, and we need to make sure the machines follow our internal naming convention especially for new machines. Add a pre-install task that grabs the existing name and prompts the tech to change it if they want like we do for windows!

Thanks for adding the ability to capture images to RSA's, now please add the ability to transfer/sync those images between RSA's and the main KACE. Otherwise the ability to capture to RSA's is pretty limited/pointless.

It would be great to get Hostnames from a CSV import directly to the K2000 Device Inventory.

If you have an existing WIM image which you want to deploy via the K2000, you need to manually apply it to a device then capture it from the KBE to get it into the appliance.
The ability to upload an existing WIM direct to the K2000 appliance would be very useful. I suspect it would also make it more attractive for organisations to move from other imaging toolsets to KACE if they could deploy their existing WIM images through the K2000.

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.

It would be nice to have the ability to "hide" certain images or scripted installs from within the KBE environment. We have images that only get used once or twice a year and our list of images is almost 100 so if you could "hide" them from the list our technicians wouldn't be able to select the old images.

Rather than having the xml answer file plug in the number of reboots, look for an automated way of calculating the reboots or count them as the system reboots and update status to know how many are still needed. Sometimes, I come up one short or one more than needed. Argh!

It would be nice to be able to run scripts (such as to configure BIOS, etc.) apart from a scripted install or image deployment. As it is we must have several deployments that have different combinations of scripts in the pre-install task area which makes things confusing and cluttered for our technicians when choosing which deployment option is appropriate. We have several image deployment options just for Windows 7 Ent. x64 alone; all of which take up space.