SDA (K2000)
Please tell us how you’d like to see the System Deployment Appliance product improved!
-
UEFI Secure boot
UEFI Secure Boot.
With the release of uefi pxe boots, we can now load images on our dell computers with much less interaction during the unbox. We are still forced to disable secure boot on all new systems before we can boot them.
Secure boot is a prevalent security patch that negates boot malware from infecting systems. this alone should be reason for integrating secure boot loads
all our equipment ships from dell with secure boot enabled under uefi, so I feel our Dell K2000 should be able to image Dell equipment out of the box without needing to modify…
366 votesWe’re moving this request back to a planned state as there are some additional items that need to be worked out before we proceed with development of this potential feature.
Microsoft has provided some additional requirements and processes that need to be completed, and this has added a timeline increase for feature release.
We apologize for any inconvenience this may cause, and we will keep you informed when we have any significant progress updates.
-
Role-based access control (RBAC)
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.
267 votes -
Replication window for RSAs
Some of our sites are on low bandwidth data connections. Trying to sync multiple RSAs takes days as the syncs do not happen concurrently. As these tasks queue up, I am unable to do other K2000 tasks, such as driver feed updates, upload images, or recaching of drivers. If we could have a window for replication similar to the K1000 replication to network shares, this would improve efficiency in our environment and ensure our RSAs are more up-to-date.
260 votes -
Driver Feed for Non-Dell systems
Managing non-Dell systems with the K2000 can be hit or miss. you should be able to feed in drivers for non-dell systems, even without the other manufacturers support.
Kace users could submit model specific driver packages to a temporary Kace FTP site, and Kace or other kace users could test and validate the drivers.
Once validated, the drivers could be included in the driver feed library alongside the existing Dell systems.
I have many great Lenovo notebook Driver Packages (T500, T510, T520, W520 etc...) I would love to share, but could use some working HP Desktop Driver Packages (like the…
168 votesResearching ways to integrate the ITNinja community, and this may be one of the big draws. We’ll look into it.
-
Ability to apply K1 labels from the K2 as postinstall tasks
It would be beneficial to be able to leverage the label feature in the K1 at time of system deployment.
153 votes -
Automatic Naming of Computer from K1000
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.
146 votesThis is part of a long-term vision in the roadmap towards restoring a machine’s identity on the K1000 when rebuilt from the K2000, with incremental progress being made in each release.
-
Be able to restore the K2000 database
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.
139 votes -
Slipstream Patches Into scripted Install
It would be very beneficial to have the K2000 be able to slipstream MS patches similar to nlite/RT7lite with all current patches. Right now a Windows 7 sp1 Scripted install has 170 patches pending from MS.
I see our K1000 as a maintainer of machines not an initial configuratior.107 votesWe’re looking at this after we get more K1000 synchronization built into the K2000.
-
Add SMB v2/v3 support when scanning user states.
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.
97 votes -
Adding Dell Diagnostics or memory testing
Add Dell Diagnostics or memory testing to the KPE recovery options.
91 votesGreat idea. Can folks also provide links to other vendors’ tools?
-
RSA as K1000 Replication Point
If we deploy an RSA to each location, why can't I use it as a K1000 replication point? Doesn't it make sense to use the RSA for this purpose as well as K2000 tasks?
90 votes -
Link tasks to a deployment and not to an image
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.85 votes -
Detach the image media from the image deployment job
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.
73 votes -
69 votes
We’d like to improve schedulling and automated tasks across the board on the K2000.
I’m not as enthusiastic about supporting user state migration to non-K2000 storage. The advantage of the K2000 is that everything’s centralized. We already have export of user state in 3.3. If the problem is not having enough native storage on the K2000, we’ve heard that loud and clear.
-
Deploy Windows Updates automatically after postinstallation tasks
It would be nice if the K2000 would also manage Windows Updates (like the K1000) to deploy them automatically as postinstallation Task.
67 votes -
Start post install tasks manually on a client for testing purposes
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.
56 votesThank you for your suggestion. I have put this in our product feature backlog. Please vote for this feature if you are interested so we can move it up the priority list. If a workaround is discovered, it will be posted here.
-
Object History tracking for security auditing
The KACE SDA currently has no way to audit changes made to any imaging-related objects, including:
- KBEs
- System images
- Pre/Mid/Post install tasks
- Task Groups
Coupled with the "all or nothing" approach to permissions in the SDA, this creates an information gap that results in a security concern: how do you know what object or setting change was made, when it was made, and who made it?
Consider the worst case scenario: a disgruntled SDA Admin on their final day at the company adds a malicious script or application to a post-install task.
The risks that come with the current model:
…
56 votes -
Add Custom Boot Images
Is it possible to:
Create a share on the KBox2000 called kbox_custom for people to add their own .img or .iso files too with the intention of developing a system which allows the booting of custom iso's and img files, ie floppy images for things like running asset tagging utilities.
Suggestions for making it work:
Because the method for booting the current iso’s seems to be through the pxelinux kernel, add a section where they can create their own boot strings and tack them onto the bottom of the boot menu.
Something like what I’ve depicted in the picture attached…56 votes -
Modifying Post Installation Tasks In Each Deployment
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.
46 votes -
K2000 should support VirtIO drivers
With the growing popularity of virtualization hypervisors that require VirtIO drives, Quest should start supporting that. Nutanix with AHV is another example of an environment where VirtIO drivers are required. Everything else we have can handle it, K2000 is the only outlier.
At the moment:
K2000 is not working at all on Nutanix AHV
K1000, even if not officially supported, at least seems working fine43 votes
- Don't see your idea?