KACE Systems Deployment Appliance (SDA)
Please tell us how you’d like to see the KACE System Deployment Appliance product improved!
125 results found
-
SMTP Authentication
This submission is to vote for the addition of SMTP authentication to the K2000. Currently you can only supply the server name or IP with anonymous authentication. This would be helpful for users with email systems that require authentication - such as Office365 shops.
24 votesThis feature was released for general availability in SDA 8.0.
-
10 GB compatibility with K2000
Would be great for the K2000 OS to be able to support 10GB. I have noticed that since the the K2000 only supports up to 1GB, this severly limits how many machines I can image at once. I can only image around 8-10 machines at a time before I saturate the 1GB virtual NIC. All of my other VM's run at 10GB and I got the network to support it, would be great if the K2000 could as well. Thanks
24 votes -
Ability to put multiple NICs on different networks
We work in a highly secure enviroment with many different vlan's secured from other vlan's it would be nice to be able to put a nic on each vlan so i can image that network w/o having to change ip on switch and kbox(then a reboot of kbox not sure why) . Also I will have issues connecting rsa's due to this inconvienance
22 votesFeature available in version 6.1. For more details on 6.1 check out : https://support.quest.com/kace-systems-deployment-appliance/kb/263374/upcoming-changes-in-sda-version-6-1
-
Add Entire Directories to Images
Ability to not only create a directory as you can now and populate it one file at a time, but actually upload whole directories including their files into system images.
21 votesIn 7.1, this feature request can be accomplished; however, you need to zip up the directory first and then upload the zip file to a WIM image.
-
Decrease delays in adding support for new Mac OS X versions, starting with 10.8 Mountain Lion
Standardizing on a single imaging suite for both Mac OS X and Windows was a big change for us; since we have roughly equal numbers of each that make up our pool of college-owned systems, a fully functional environment is equally critical for each of these platforms.
I am concerned that timely support for Mac OS X seems to be slipping, and this is only becoming more painful as Apple seems to be returning to a near-yearly OS release schedule. 10.7 was not supported in K2000 NetBoot until more than a year after its full release. 10.8 has been out…20 votesOSX 10.9 (Mavericks) is now supported in K2000 3.6, which has just entered RC! If you need it NOW for your own deployment, and want the release candidate, let me know at alex@kace.com!
-
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 votesThis feature was added in SDA v9.1. Downloads for the current versions are available at https://support.quest.com/kace-systems-deployment-appliance/download-new-releases
-
Suggesting further improvements to WIM image handling in 3.5 and above
Hello, there may be a few posts around this idea but they are lacking detail and mostly attack the changes in 3.5 when it comes to WIM's. I can see the merit's in what KACE has done in terms of "cleanliness" however, unfortunately 3.5 has been a step backwards in terms of functionality in regards to WIM's.
Reverting to the old method officially isn't going to happen, although we can all use the old method if we want, with just a few more steps. However rather than that, here's my suggestions on what needs to be changed post-3.5 to bring…
19 votesI split this idea into three separate suggestions for better tracking. I will be managing the three suggestions generated from this one for future planning and notifications, and will now mark this as completed.
Take a moment and place your votes for those suggestions most important to you.
1. Allow multiple imaging tasks to point to a single WIM file – https://kace.uservoice.com/forums/82717/suggestions/20372029
2. Modify WIM Image files (feature started)
https://kace.uservoice.com/forums/82717/suggestions/200405383. Don’t copy the WIM to the local machine before deploying (Image streaming) – https://kace.uservoice.com/forums/82717/suggestions/20371981
-
Add Powershell Script to Post-Installation Tasks
Now that windows comes with Powershell installed. It would be nice to be able to add Powershell scripts as Post-Installation Tasks instead of having to zip them and run them with a batch file.
19 votesCompleted in version 5.0
-
Add Username to eligible Appliance Logs
Currently if a user updates the SDA (K2000) version, the Appliance Upgrade Log only has the date and time of the update. There is no way to see who started the process.
[Mon Jan 7 19:54:22 EST 2019] [notice] XXX Begin K2000 Server Update to 6.1.251 from 6.0.425
[Mon Jan 7 19:54:22 EST 2019] [notice] XXX===========================================================================
[Mon Jan 7 19:54:22 EST 2019] [notice] Removing backup 5.1.84backup.sql.0.gz
[Mon Jan 7 19:54:22 EST 2019] [notice] Removing old database backups
[Mon Jan 7 19:54:22 EST 2019] [notice] kboxupgrade:: NOTICE: Running kboxupgrade.php part 1
[Mon Jan 7 19:54:21 EST 2019] [notice]…15 votesThis feature request has been completed, and you will see user information in the logs after the next most recent appliance upgrade (>7.2).
-
Ability to schedule boot actions
Images get pushed overnight and are pre-staged before IT staff goes home. If the user stays late and reboots his or her computer, the image gets pushed prematurely. Give ability to ignore network boot actions prior to scheduled time.
15 votesThis request has been implemented in the SDA (K2) 3.6 release
-
Ability to Deploy Large Applications as Post Install Tasks
Currently the limit is 2GB I think for Post Install Task. Even with a work around of exporting, re-zipping and importing, the system does not support large applications such as Adobe CC. The only way around this is to run it from a file share.
14 votesThis suggestion was completed in version 6.0.
-
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 votesThis feature was added to SDA in v9.1
-
Ability to schedule a scripted install
I would like to be able to schedule a scripted install for a set of machines on a regular basis (ie. training room pc that needs to be returned to a clean, fresh installed and updated state). Currently, there is no way to schedule a install in this manor.
14 votesScheduling is now in K2000 3.6!
-
Integration with K1000 Database
Direct integration with the K1000 database for machine inventory (and any other useful integration). It seems redundant to have to scan for machines when the K1000 already has all existing systems in the MACHINE table.
14 votes -
Improvement of Sysprep Creator for Windows 10
It would be helpful to have more options with the Sysprep Creator to build a complete unattend file. Things under "Microsoft-Windows-Shell-Setup" including "BluetoothTaskbarIconEnabled" and "DonNotCleanTaskBar" for examples. Encrypting the password would be great. Adding custom firstlogon commands. Among other things that would be helpful.
14 votesSysPrep Creator version 4.0 supports these features and can be downloaded from the Quest Support portal.
-
Windows 8/Server2012/PE 4.0 support
I think I saw this listed on the itninja forums, but nothing was listed here that I could find. So adding it to make sure it is officially on the feature request list.
This would include driver support for Windows 8 and Server 2012 and an upgrade of the KBE to use Win PE 4.0 which I believe is required to install Windows 8 and Server 2012.
Would also like to make sure powershell is added to the KBE. I believe you already get that by adding the scripting package in PE 4.0 which is already added to get vbscript,…
13 votesWe will have preliminary Windows 8/Server 2012 support in the K2000 3.5 release. We’ve run into a few issues with WinPE however, but we’re able to capture and deploy Win8 and S2012.
EDIT: 3.5 SP1 includes full support for Windows PE 4.
-
Make Windows Share imaging hack a standard feature (non-RSA)
RSA deployment is not an option for our environment, so found this with the help of Gerald Mack (and Brian Collins)
http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wim-s
Gerald also provided this DOS command which worked perfectly:
"net use t: /d && net use t: \netshare\share /u:username password"For those offices with small pipes, we load the local KBE via USB key, which we seldom need to update so that is perfect. Ultimately I feel the K2000 should have a function similar to the Replication Shares of the K1000. I believe this would be a major selling point for new customers.
13 votesThis suggestion can be accomplished using the new Custom Deployments feature released in version 6.0.
-
Upload Background Image for PXE Graphical Boot Menu
I would like to be able to change the background of the PXE graphical boot menu to the logo of my organization. I am able to manually do this with FogProject but am not allowed SSH access to the K2000.
13 votesSimplified PXE background changes are included with SDA v9.0. Upgrade today! https://support.quest.com/kace-systems-deployment-appliance/download-new-releases
-
Drive Feed Auto Filter/Remove - Search and Destroy
The Drive feed is an excellant resource when creating scripted installs for Dell Machines, but when you try to image off Dell, like HP for example, we need to add all the drivers manually or in a post installation task. The systems blue screen when there are duplicate drivers, it would be excellent if there was like a search and destroy or remove duplicates option, this would help everyone maintain their own driver database for their enterprises systems.
12 votes -
MTU adjustment
Please add the ability to adjust MTU. It appears Kace appliances use the default 1500 mtu for ip4 connections. It seems most modern networks support well beyond this.
The ability to adjust for our environments would have a huge impact on deployment times.
12 votesFeature available in version 6.1. For more details on 6.1 check out : https://support.quest.com/kace-systems-deployment-appliance/kb/263374/upcoming-changes-in-sda-version-6-1
- Don't see your idea?