It would be very helpful to have the Scan User States Offline task work for environments where user profiles are stored on another partition (D:\Users for example).
The builtin Scan User States Offline task works only if users are stored in C:\Users. Also, the task is somehow hard coded and receives some parameters passed on from Custom, Scripted, Imaging html files respectively and where it's called. The scanuserstates_offline.wsf references scripts under peinst\hta folder which is read only so customizing this task it's almost impossible.
Thank you!

In a bigger environment it happens that multiple administartors are creating KBEs and injecting Source media. After a while that gets messy and needs a cleanup, but Kace does not offer any option to easily identify which are in use and which are just left overs. There is a marker for "default" but that is all. Would be really helpful to see "used" or "unused" Source Media or KBE.

Version 5 finally allowed users to capture images to the RSAs. We're on version 6.1 now and are still unable to sync/replicate those images back to the SDA. In K-12 education, we use shared images across all our sites. The ability to capture images anywhere is great, but what's the point if you can't share that image with the rest of the sites? We have 23 RSAs. Being expected to export/import these images is absurd.

Support for Para Virtual SCSI boot drives for disk performance

When creating a USB Image, have the data encrypted. This will protect sensitive passwords from being exposed. In the event the USB Stick is lost.

When creating a USB Image, have the data encrypted. This will protect sensitive passwords from being exposed. In the event the USB Stick is lost.

We need to be able to create more than one button on the Service Desk User Console (currently quick action button). Would like to be able to create two, direct the button to the appropriate Q and be able to modify the text on the buttons

During post installation tasks processing even after a successful completion we may need delay before Kace engine reboots the computer especially if its the last task.

For instance, I have a .bat file that pulls an installation from the internet the Kace appliance will move onto the next task or reboot before it finishes.

Adding a timeout /t 30 will not delay the reboot.

Regulate access to various functionality based on user roles and permissions. This would include granular access to capabilities such as:

• Logon to KBE
• Access to specific production images
• Server/workstation roles
• Samba share access
• Differentiate between access to deploy images, and access to log into connected machines as an admin.

Instead of picking an image file that has tasks assigned to it, give the ability to create Build Groups where you select the image and applications to be installed. Right now its static, if you want to use the same image but different programs you have to duplicate the image and assign a different set of applications tasks to it. This takes away from usable drive space. It would be easier to build the deployment groups that calls a certain image and application groups.

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?

We can now upload to RSA's but have to get support to remove failed images.

I am speaking from SDA v5.1 perspective. I do not know if SDA v6.0 has already resolved this. The SMA v8.1 resolves this issue.

The issue is described in this knowledge base article:
https://support.quest.com/kace-systems-deployment-appliance/kb/230041/error-net-err_cert_common_name_invalid-certificate-error-on-browser-230041-

The SSL certificate signing request feature needs to support the entry of SAN's.

Allow RSA's to run network scan and transfer results to K2 appliance

Have the "SMA Agent" post-install task pull the installer directly from the \kbox\client share. As it is now, the SDA user/manager must manually upload the SMA agent to the SDA's post-install repository, and remember to update it when the SMA's share gets updated with a new client. If the SDA pulled directly from the SMA's share, we wouldn't have to worry about keeping the installers in sync.

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

It appears PXE 3.0 is capable of supporting 802.1x authentication.
Many networks utilize radius authentication to control users and VLANs. This is an issue with the current K2000 PXE since there is no option to provide credentials. I suggest an option be added to insert a username and password into the undionly.kpxe and ipxe.efi so that PXE Boot can authenticate.