Chat now with support
Chat with Support

KACE Systems Deployment Appliance 8.0 Common Documents - Releaseinformationen

Bekannte Probleme

Bekannte Probleme

Im Anschluss finden Sie eine Liste mit Problemen, einschließlich Problemen bei Drittanbieterprodukten, die zum Zeitpunkt der Veröffentlichung bekannt waren:

Bekanntes Problem

ID des Problems

When a task fails in the KACE Boot Environment (KBE), and you click Cancel Deployment, the deployment does not move to the Audit Log.


No error warning is displayed when uploading a KBE to the Remote Site Appliance (RSA).


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


First KBE upload is not being set as the default.


CentOS 8 deployments fail when the repository cache is enabled.


Imported KBE is not set as the default if no other KBE exists on the appliance.


Network media is not properly translated.


The traceroute troubleshooting tool is not working when invoked from the Administrator Console in some environments.


Imported Managed Installation can have wrong size.


VNC fails to show command windows on Microsoft Windows 10 PE (Pre-installation Environment) 2004, in 32- or 64-bit KBEs.


Automated deployment drop-down does not show deployment names when there is no boot environment set as a default.


When a tasks fails, the next tasks shows as being in progress.


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.


Multi-byte locale translation is broken on a KBE.


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


DeployUserStates.vbs fails in a custom deployment.


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.


Incomplete logs are created for deployment of MAC K-Images/ASR Images.


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.


A Mac OS client device is unable to boot in NetBoot from an RSA, when the RSA is on offboard data store.


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.


The NetBoot login screen is displayed on the client machine when deploying a Mac OS X 10.11, ASR (Apple Software Restore)/K-Image, and the boot action is set.

Workaround: It is recommended for users to wait until the NetBoot environment has completed the pre-processing steps for Mac OS X 10.11, which occur when the login screen displays the password box and the KACE SDA IP at the bottom of the screen. Also, the deployment progress can be observed in the KACE SDA Administrator Console.

If a login is attempted before these processes are complete, the KACE SDA imaging utility is not shown on dock and the user will need to reboot into the NetBoot environment.


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


Imported ASR image deployments fail if no ASR images were captured from the KACE SDA.

Workaround: Create the ImageStore folder in the petemp directory.


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 .


In French, the button for "start upload" is truncated in Mac Media Manager.


A Mac client machine is unable to Netboot when SSL, DHCP, Netboot Server is enabled, and the KACE SDA server with expandable storage configured as NAS (network attached storage).


Applying computer name sets a blank computer name when an ASR is deployed which contains no computer name.


Mac OS Join Domain Post-Installation Task script does not check for valid host name assignment, and does not exit with status code of zero '0' if does not find a host name, as expected.


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.


No error message is displayed on Mac Media Manager when NetBoot passwords entered do not match.


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.


Performing a NetBoot into the KACE SDA box assigns two IP addresses to the client.




Die mindestens erforderliche Version für die Installation von Version 8.0 ist 7.2 (7.2.97). Wenn eine frühere Version der Appliance ausgeführt wird, aktualisieren Sie vor der Installation diese wichtige Version auf die angegebene Version und starten die Appliance nach Abschluss des Update neu. Um die Versionsnummer Ihrer Appliance zu überprüfen, melden Sie sich bei der Administratorkonsole der KACE Systembereitstellungs-Appliance an, öffnen Sie den Bereich Benötigen Sie Hilfe? auf der rechten Seite und klicken Sie auf das Symbol „Über die Appliance“.

Vergewissern Sie sich vor der Aktualisierung auf Version 8.0, dass das System die Mindestanforderungen erfüllt. Diese Anforderungen werden in den technischen Daten der KACE Systembereitstellungs-Appliance erläutert:



Falls Sie derzeit eine Produktlizenz für die KACE Systembereitstellungs-Appliance besitzen, ist keine zusätzliche Lizenz erforderlich.

Wenn Sie die KACE Systembereitstellungs-Appliance zum ersten Mal verwenden, finden Sie ausführliche Informationen zur Produktlizenzierung in der Dokumentation zur Appliance-Einrichtung. Das entsprechende Handbuch finden Sie unter Weitere Ressourcen

HINWEIS: Überprüfen Sie vor der Aktualisierung den SDA-Statusübersichtsbericht, und stellen Sie sicher, dass der aktuelle Wartungsstatus gültig und nicht abgelaufen ist. Sie finden den Bericht unter Überwachunsgprotokoll > berichte.



Sie können die Appliance mit einer mitgeteilten Aktualisierung oder durch das manuelle Hochladen einer Aktualisierungsdatei aktualisieren.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating