Skip to content

KACE Systems Deployment Appliance (SDA)

Please tell us how you’d like to see the KACE System Deployment Appliance product improved!

99 results found

  1. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Detect which "Source Media" and which KBE "Is actually in use"

    In a bigger environment it happens that multiple administartors are creating KBEs and injecting Source media. After a while that gets messy and needs a cleanup, but Kace does not offer any option to easily identify which are in use and which are just left overs. There is a marker for "default" but that is all. Would be really helpful to see "used" or "unused" Source Media or KBE.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Enable to "kill" a blocking sync task

    We have been facing a lot of situations where the sync queue was hanging and therefore the whole appliance is useless as nothing can be done anymore. This always requires calling the support which causes workload for the support, the customer and wasting time, cause the only thing Support will do is kill the hanging process. If there would be a "button" to kill the "current hanging" task it would be beneficial.

    Example: RSA replication hangs because of new version has been installed but no version check, if the "nightly sync" task hits that rsa the whole queue is stuck…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Sync images captured on RSA to SDA

    Version 5 finally allowed users to capture images to the RSAs. We're on version 6.1 now and are still unable to sync/replicate those images back to the SDA. In K-12 education, we use shared images across all our sites. The ability to capture images anywhere is great, but what's the point if you can't share that image with the rest of the sites? We have 23 RSAs. Being expected to export/import these images is absurd.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  New Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Split task queues for replication

    Please make the "nightly sync" queue run multiple RSAs in parallel, or at least adjustable. We are running 200 RSAs and if one of them for whatever reason is blocking delaying the sync the whole queue gets into a backlog. Then it is hard to get it synced without manually interacting and canceling and pushing multiple RSAs at once.

    As it is possible to run multiple syncs manually triggered in parallel it should not be a big deal to also make that work for the build in queues.

    Same applies at days when we need to inject new drivers intro…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  New Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Can we include a delayed reboot option?

    During post installation tasks processing even after a successful completion we may need delay before Kace engine reboots the computer especially if its the last task.

    For instance, I have a .bat file that pulls an installation from the internet the Kace appliance will move onto the next task or reboot before it finishes.

    Adding a timeout /t 30 will not delay the reboot.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  30 comments  ·  New Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. syslog

    Provide an option to send syslogs to a server (like a SIEM). I see it is planned for the next major release of the SMA. Is the same feature schedule for SDA?

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. The CSR generator needs to support SAN's as it does in the SMA v8.1

    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.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Ability to remove Images captured on an RSA from the main appliance

    We can now upload to RSA's but have to get support to remove failed images.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  New Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Allow RSA's to run network scan and transfer results to K2 appliance

    Allow RSA's to run network scan and transfer results to K2 appliance

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Have the "SMA Agent" post-install task pull the installer directly from the \kbox\client share.

    Have the "SMA Agent" post-install task pull the installer directly from the \kbox\client share. As it is now, the SDA user/manager must manually upload the SMA agent to the SDA's post-install repository, and remember to update it when the SMA's share gets updated with a new client. If the SDA pulled directly from the SMA's share, we wouldn't have to worry about keeping the installers in sync.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. PXE Boot supporting 802.1x authentication

    It appears PXE 3.0 is capable of supporting 802.1x authentication.
    Many networks utilize radius authentication to control users and VLANs. This is an issue with the current K2000 PXE since there is no option to provide credentials. I suggest an option be added to insert a username and password into the undionly.kpxe and ipxe.efi so that PXE Boot can authenticate.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Add a widget on Dashboard to show whether scheduled sync to RSA(s) failed or was successful.

    Add a widget on Dashboard to show whether scheduled sync to RSA(s) failed or was successful, maybe have a widget to show the status of all scheduled operations. Would be nice to know if something failed without having to wade through logs or submenus.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Delete USMT user state after successful deployment or on timer

    Just paint this picture: 300+ Win 7 Clients are to be upgraded (scanstate, wipe+load, loadstate) to Win 10 using the SDA (and build in tasks). The list of possible user states to restore will be to long to click "Start Installation" after three or so upgrades.

    Suggestion: Mark USMT user state as to be deleted after a successfull restore. On timer (once per night?) delete marked user states.
    Possible plus: Add a checkbox to the USMT user state's details page: "Don't cleanup"

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  New Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Allow option to choose which driver feed models to sync to RSA instead of all drivers downloaded on K2

    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.

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Credentials Management

    K1000 has a Credentials Vault, could we also add Credentials Management to the SDA k2000, so that scripts or other scripts don't have hard coded username and password in post install task.

    Credentials Management or a password vault for Post and PRE task would be great.

    Thanks.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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.

    275 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Allow audit mode when creating an image

    When doing a scripted image, it will be helpful to put that image into audit mode automatically so you can more changes to it before syspreping it again.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  New Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

KACE Systems Deployment Appliance (SDA)

Categories

Feedback and Knowledge Base