KACE Systems Deployment Appliance (SDA)
Please tell us how you’d like to see the KACE System Deployment Appliance product improved!
39 results found
-
Quick view for all Dell models supported by KBE
Be able to click on a KBE in the K2000 and see what Dell supported workstations they will work on. Having the driver report is nice, but having to search for the actual network driver for the machine I am working on is a pain. Being able to see the model and OS the KBE would speed up this process.
4 votes -
USB Image Encypted
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.
3 votes -
Add Option to Pull Serial Number from Ending Characters When Using SetComputerName
Add variable/option to pull serial number from ending (rightmost) Characters When Using SetComputerName. Windows computer name character limits paired with naming conventions and how some manufacturers prefix serial numbers lead to multiple duplicate computer names when trying to use the $Serial variable in setcomputername_x64.exe due to truncation. An option to use the ending characters from the serial and truncate the beginning would be very useful here.
3 votes -
It would be nice to have something that cross references patch exit codes to a description of what the code means
This could be as simple as a table where a user can enter some patch exit codes and what those codes refer to. This would be a time saver when looking through patch failures to determine the cause instead of having to look up the codes on a regular basis.
3 votes -
Windows 11 Deployment
Please add Windows 11 Deployment support to KACE SDA (K2000) ASAP.
3 votes -
Windows Server 2022 Deployment
Please add Windows 2022 Deployment support to KACE SDA (K2000)
3 votes -
Deployment log report date format and XLS export?
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.
3 votes -
name manual deployments
It would be great if we had the option to name a manual deployment. That way when multiple deployments are kicked off we can follow which is which.
3 votes -
modifying task que list
I came across a customer where rsa updates had hung for about a week, after we rebooted the task que had a few hundred tasks to do. For all the rsa's I had to enter each rsa to cancel the update manually, and that did take a lot of time. If we could get access to the task que directly we could have marked all the items we didn't want to do at the moment, and deleted them from the que in one operation.
3 votes -
Better RSA sync scheduling - mimic SMA days/hours
Many of my RSAs are in locations that have VERY limited hours I can use max bandwidth. Why can't there be a calendar setup like the SMA where I can specify what hours of what day of the week sync'ing can occur? I have to manually start/stop sync'ing as there's not enough granularity in scheduling the sync. Why can't we have the low/high bandwidth settings just like the SMA? I spend WEEKS, not hours trying to sync my RSAs.
3 votes -
Add Task Start and End Times to Deployment Task Details
It would be nice to go back over a deployment to see how much time elapsed per task to troubleshoot or optimize.
KACE recently added the Add Task Start and End Times to the deployment details page of each deployment. Two additional columns that could be useful are task start and task end time.
3 votesThanks for this feedback - we'll talk to the dev team and see where this addition can be added into the backlog.
-
Please include an exclusion list for k-images
I would like to see the ability to exclude files from being included in a k-image such as pagefile.sys and hiberfil.sys to allow the images to be smaller
2 votesGreat idea, if we can make it foolproof so that the image is bootable. Need to have a “never exclude” list.
-
Ability to upload MIG files downloaded from the RSA into the SDA
The USMT profile is currently able to be exported from the RSA and could run a custom task to deploy the MIG file. Would be better if there was an option to import MIG file into SDA to be selected during image deployment from SDA. This would be similar to current process of images captured on the RSA that can be exported - then imported into another RSA or SDA.
2 votes -
Update the embedded version of 7-Zip in the Driver Feed Builder Application
The current version of the Driver Feed Builder v3.0.0.0 uses an embedded version of 7-Zip v9.2. The current stable version of 7-Zip v19.00.
The current embedded version v9.2 is flagging in our enterprise anti-virus solution due to vulnerabilities in that version. Suggest replacing with current version v19.00 at a minimum.
Should take a minimum amount of time to provide this update in the next version of the Driver Feed Builder application.
2 votes -
When upgrading the SDA from 8 to 9, please copy the driver feed drivers from the old location to the new one?
We upgraded from a late version of 8 to 9.0.144. I found that none of the drivers in the old location (driverspostinstall\dell\windows10x64) were copied to the new location (Z:\driverspostinstall\windows\10\x64\any\dell).
I didn't find that out until yesterday while working with support to discover why driverfeed wasn't working for VMware machines (that's another issue).
2 votes -
Driverfeed no longer works with VMs
This used to work on version 8 and prior. It does not work on version 9. Quest has redefined driverfeed to search for the machine ID, which is not available for VMs. They assign a code for the machine ID to a directory name, such as "0a3e". The machine ID is retrieved using "wmic baseboard get product". For a VMware VM "440BX Desktop Reference Platform" is returned. Surely they could key off that to identify that it's a VM. Also, since the PXE platform has VMXNET3 drivers, they can detect whether those are in installed and active. The same is…
2 votes -
Add an additional column in the "Deployment progress" view to be able to identify the machines.
Add an additional column in the "Deployment progress" view to be able to identify the machines. Right now its just possible to show the "Name", "Deployment", "Deployment Type" and "Date Started".
In a big envrioenment (we have 14k+ clients and 200 sites) this is completely useless as multiple installations starting at the same day and the list is showing the same "names" just the time is different. By adding the IP and Mac address (both values are available at that point already) would significantly help to identify the correct machine which needs to be monitored.
Easy implementation and a great…
1 vote -
Enhance Scan User States Offline task to work for User Profiles stored on secondary partition
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!1 vote -
Add a field to the linked appliances list
K2000 Settings - Control Panel - Linked Appliances
Add a singe field to the linked appliance records called "Description". Apart from the hostname (which in many instances is just an IP address) there's no way to identify the various linked appliances.
Thanks!
1 vote
- Don't see your idea?