Chat now with support
Chat with Support

KACE Systems Deployment Appliance 8.1 Common Documents - Release Notes

Known issues

Known issues

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

Table 3. General known issues

Known issue

Issue ID

Network scan is not populating Network Scan Inventory.


Progress Update messages no longer appear in client log.


Read-only users cannot view Scripted Install XML data.


Upgrading with Hyper-V does not always mount the appropriate disk partition


CentOS 8 deployments fail when the repository cache is enabled.


It is not possible to enable SSL (secure socket layer) using an existing SSL certificate and key on the KACE Systems Deployment Appliance and RSA.


RHEL (Red Hat Enterprise Linux ) and CentOS 7 manual deployment ends in dracut.


The filter tasks box is skewed when browser size is decreased.


UEFI ISO KBE forces the user to press a key to boot from it.


An appliance iPXE error is reported: no configuration methods succeeded.


Custom Deployment does not display User States for deployment.


Remote Site Detail page takes a long time to timeout if RSA is unavailable.


The appliance USMT should use SID (security identifier) instead of the user name to avoid unexpected results while scanstate runs.


Certain task types cause screens to appear in front of the KBE page.


Klonewin stops responding due to network instability issue during file copying phase.


After importing an MI created with All Operating System checkbox selected on the KACE System Management Appliance (SMA), the Runtime Environment is displayed as Windows on the KACE SDA server.


When importing same packages, duplicate entries are created on the appliance.


Online USMT Scan and Offboard Package Transfer fails if SMB v.1 is disabled on the target.

Workaround: Use the USMT Advisor tool, downloadable from the Support Portal or Library Overview page. This tool helps with common issues encountered during this process.


VMware virtual machines with multiple vCPUs (virtual central processing units) cannot PXE-boot to a legacy iPXE.

For more information, read the following KB article:


Building a USB key for a system image does not update status message.


After clicking New boot action for a Mac OS NetBoot on the Boot Environment Detail page, on the Automated Detail page that appears, the Deployment field is not set, as expected.


Some models freeze during the initializing device stage and do not display the KBE menu during an UEFI PXE boot.


The path for drivers in the Driver Feed are not always unique which causes problems for Driver Feed widgets.


Japanese user profile is not listed in Available Profile List.


Imaging to Serial Attached SCSI (SAS) drives is extremely slow, five hours or longer.


The System Image Detail page does not remain locked until the USB creation process is complete.


The Date and Time Settings page should follow the language region date format.


When deploying a dual or multiple partition WIM image through multicast instead of unicast, only the first partition deploys.

Workaround: A workaround is available for this issue. For more information, read the following KB article:


Resizing the columns width functionality does not work for certain columns on some list pages.


The Offboard Storage Error Message in the Initial Configuration Wizard should be moved into the same error message box used in other pages.


Detail View should highlight selected row in data table .


Non-ASCII KACE Systems Management Appliance (SMA) Managed Installation (MI) package name is garbled on the package import list.


Invalid date is allowed for the Run once, on option while creating or updating a scheduled boot action.


Non-English offline user state from Windows 8 is not scanned for K-Image or scripted installation.


lagg0 does not appear in munin.


Intermittently when booting from a USB, the machine freezes while starting Windows.


When switching between linked appliances, the drop-down list in the top-right corner of the Administrator Console should display only the linked appliances instead of all of the appliances to which you logged in to using single sign on (SSO) from the KACE SDA.


When KACE SMA and KACE SDA are linked together, two boot actions are created for client machine with two network interface cards (NICs).


Clicking Remove local files not in image does not remove local files from non-system drive.


System requirements

System requirements

The minimum version required for installing version 8.1 is 8.0 (8.0.194). If your appliance is running an earlier version, update to the listed version before installing this major release and restart the appliance after the update is installed. To check the version number of your appliance, log in to the KACE Systems Deployment Appliance Administrator Console, open the Need Help pane on the right, then click the About Appliance icon.

Before upgrading to or installing version 8.1, make sure that your system meets the minimum requirements. These requirements are available in the KACE Systems Deployment Appliance technical specifications:

Product licensing

Product licensing

If you currently have a KACE Systems Deployment Appliance product license, no additional license is required.

If you are using the KACE Systems Deployment Appliance for the first time, see the appliance setup documentation for product licensing details. Go to More resources to access the appropriate guide.

NOTE: Prior to upgrading, check the SDA Status Overview Report and verify that the current maintenance status is valid and not expired. You can find the report under Audit Log > Reports.

Installation instructions

Installation instructions

You can update the appliance using an advertised update or by manually uploading an update file.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating