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

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.

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.

The K2000 can pull inventory lists from K1000 labels for automated deployments, but those lists are static. If the label group changes on the K1000, the group does not update on the K2000.

For example, if I had a group of systems I want to re-image on a weekly basis. If one of the computers is replaced, the automated deployment must be rebuilt.

Can the K2000 re-sync label members on the fly or even on a schedule?

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.

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.

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.

Currently, using a Virtual K2000 appliance, it is impossible to expand the offboard storage disk once created - the only way to give yourself more storage is to put the files back onboard, delete the offboard disk, and then re-create, moving the files back over again.

It'd be better if we could just expand the disk in our virtual environment, then ask K2000 to 'rescan' the disk and have the ability to expand into the space.

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 schedule boot actions on Deployments > automated deployments > functional (MAC address and IP address) without the need to create a boot action in the details of an image or a scripted installations.

The ability to export as an XLS format for deployment logs would prove very useful particularly if the date and time fields kept the date/time format, at present we have a long process to convert to date/time to create useful reports.

With the introduction of task groups in 6.0, I would like the ability to mark a task group as a default. So when I capture a new image, that task group is automatically applied to it.

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.

Currently the "Limit average transfer rate to" setting uses Kilobytes per second and this should be set to Kilobits per second instead to be more inline with network throttling standards.

I think the K2000 lists should all have configurable sort options. I organize my deployments by name, so I would like to see this breakdown of the images almost every time. I keep having to select to sort by name. I think the system should either have a memory or allow a default to be stored.

The following are example fields that should be sortable:
- Deployments
- Install tasks
- Inventory dropdown menu

I have a dist for Mappoint (as an example) Id like the ability to add this as a post install script instead of downloading the zip and creating my own application post script installation. Its doubling the workload and disk space.