SDA (K2000)
Please tell us how you’d like to see the System Deployment Appliance product improved!
-
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.
272 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.
267 votes -
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.
157 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.109 votesWe’re looking at this after we get more K1000 synchronization built into the K2000.
-
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.
68 votes -
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:
…
57 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 -
Block level imaging of systems
We would like the ability to do block level imaging again. Unfortunately this ability was removed with the removal of the linux kbe in the newest K2000 release. So either implement your own program to do block level imaging or allow the customer to create a section in the WinPE environment where they can use 3rd party imaging programs like Acronis or Ghost. We had this ability when we bought Kace and now it was removed. If Acronis & Ghost can do block level imaging in WinPE, Kace should be able to do the same. This truly limits are ability…
28 votes -
Improved RSA Administration
With 100's of RSAs deployed, changes to the configuration of a single typically results in hours of work--login to RSA, change configuration, rinse/repeat.
Ideally, I'd like one or more administrative templates that would allow me to control common settings (e.g., proxy, authentication, admin password, NTP, etc.)
I'd also like to script the reboot of a remote site appliance (think quarterly maintenance reboots). Currently, this process is administratively cumbersome even when performing reboots of each RSA (guest) via vCenter.
23 votes -
2 Factor authentication
Would be nice to have a 2 factor authentication , as the kace 1000 and 2000 contains important information and detailed inventory
19 votes -
18 votes
Can you flesh out the use case further for me? Give me some examples of what kind of SI’s you’d do, the pre- and post-install tasks, etc.
-
Custom Columns in Deployments area
Allow customers to change the width of existing data columns, add custom columns with pre-existing fields (i.e. date created, last date modified, last date used), and remove columns that customer does not need or want (i.e. hostname) all within the Deployments area of the K2000.
This would great help the organization of images, and the quick viewing of information for image rotation, updating, statistics, etc.
15 votes -
Dualboot Windows/Linux + grub
Hello,
I would like to know when it will be possible to create k-Aother images or image format that will manage the Windows / Linux dual boot + Grub. or at least the possibility of an image Creation repeating the entire hard drive (Whatever the grub partition and above)
Thank you in advance.
RegardsChristophe
Ecole Centrale de Lille - IG2I
France15 votesThis would require expanding our integrated support for Linux platforms, so we’ll keep this in mind.
-
Single Sign On - To match K1000
We are using SSO on the K1000 since it was released. However it broke the linking between the K1000 and the K2000. After several tickets it was decided the problem is the K2000 does not have a SSO option.
Not sure why that is the kace (see what I did there...lol) but it really should support SSO at the console.
14 votes -
13 votes
Thanks!
-
Rename computers via Systems Inventory
Create the ability to rename computers as a post task via the match of the mac address and system name within the system inventory. Right now one needs to maintain a flat file via WSName.
12 votes -
Logical Installation task
Would like to see the k2000 have the ability to do logical installations based on chasis type. Such as desktop or laptops. There are applications that only need to be installed on a laptop and it would be great to automate that based on the type of chasis.
12 votes -
Add a Patch Feed for scripted imaging just like the drivers feed
Add a patch feed that you can subscribe to MS patches, adobe patches firefox ect and then apply patch feeds to scripted images so your images always come off the bench with the latest patching.
11 votesWe’re looking into extending the linking and integration abilities between a K1 and K2 and this would be one of the features we’d implement when that time comes.
-
Get KUID from the SMA for an existing machine
Have a pre-install task that will allow you to select an existing device from the SMA to apply the KUID as a post install task. When imaging an existing device with a new HDD/SSD the SDA has no KUID to grab so when the agent is installed it thinks the device is a new device. This causes an issue of having multiple assets that should be the same device asset.
10 votesThank you for this feature request!
It sounds like some additional review is needed in the product’s capacity after the SMA/SDA are linked. We will review this request and determine its place within our product backlog.
-
Add support for Dell ImageDirect images
We have a set of Windows images on Dell's ImageDirect site that would be nice to upload over to the K2000, either from the site, or via ISO files.
10 votesIn the future, we may have a much tighter integration with Dell factory processes, where you can use your K2000 as a ‘Dell-Factory-in-a-Box’
- Don't see your idea?