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.

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.

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.

The 5.0 reskin is a huge step back from the 4.x color scheme and is too bright for my old eyes.

A way to change the colors for the web interface or just have the ability to swap to a dark theme would be great

Version 6.0 introduced Task Groups. Would be great if it went one step further and allowed us to duplicate task groups. I have many locations that use similar tasks for each deployment but vary slightly (such as time zone). Would be nice to be able to create one task group and then duplicate/modify just the tasks for each location rather than having to build a task group from scratch for each location.

It would be nice to not have to go through the manual process of adding this package for Bitlocker support. If this was one of the KBE Options in the KBE Manipulator, it would help a lot.

Is there any reason why the 'Date Completed' column within 'Progress>Manual Deployments' and 'Audit Log>Manual Deployments' can't be defaulted to sort with the latest deployment date at the top? As I monitor the success of the image deployments, I have to re-sort the column as the default view will always show the oldest deployment at the top. This would be a time saver and seems to make sense (at least to me). Thanks.

Would be great for the K2000 OS to be able to support 10GB. I have noticed that since the the K2000 only supports up to 1GB, this severly limits how many machines I can image at once. I can only image around 8-10 machines at a time before I saturate the 1GB virtual NIC. All of my other VM's run at 10GB and I got the network to support it, would be great if the K2000 could as well. Thanks

It would be great to receive e-mail notifications when the Off-Board Package Transfer Backups are successfully completed and/or have issues.

It would be helpful to have more options with the Sysprep Creator to build a complete unattend file. Things under "Microsoft-Windows-Shell-Setup" including "BluetoothTaskbarIconEnabled" and "DonNotCleanTaskBar" for examples. Encrypting the password would be great. Adding custom firstlogon commands. Among other things that would be helpful.

Currently the limit is 2GB I think for Post Install Task. Even with a work around of exporting, re-zipping and importing, the system does not support large applications such as Adobe CC. The only way around this is to run it from a file share.

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.