Chat now with support
Chat with Support

KACE Systems Deployment Appliance 4.1 - Release Notes

Resolved issues

Resolved issues

The following is a list of issues resolved in this release.

Table 2. Resolved Issues

Resolved issue

Issue ID

The automated deployment of a 32-bit OS image failed on a 64-bit processor machine with iPXE.


The RSA upgrade process log showed Updating K2000 instead of Updating RSA.


Some K-Image deployments of Windows 8.1 x64 and x86 were failing with an error in various locations.


MAC Address lists under Selected Devices were cleared when the user switched from the K2000 appliance to the RSA, while creating a boot action from device inventory.


Windows Media Manager was unable to build a KBE and upload it when space is in a Samba share password.


Some computer models hanged at the KBE boot logo (Windows or manufacturer logo) while loading the UEFI KBE.


The Driver Feed page was not displaying a blue arrow when a driver was updated or new.


When a file name of a certain length was added as a pre/post task, it was not easy to replace when using Google® Chrome™ on Windows.


Some UEFI-enabled machines would not boot to the local hard disk after loading the iPXE menu.


The NetBoot Image for Mac OS X 10.11 was too large.


Photos were not being removed from /Applications on Mac OS X 10.11, on NetBoot creation.


Question marks were displayed instead of the application icons for Maps and iBooks on dock in the Mac OS X 10.11 NetBoot environment.


jQuery is removed from the online help (Administrator Guide).


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

The Boot Manager Password feature does not function in the new UEFI-compatible booter.

Boot Manager Password

When running scripted install of Windows 7.x on a system configured with NVMe (non-volatile memory express) that uses the PCIe (Peripheral Component Interconnect Express) bus, the following error occurs:

Windows needs the driver for device [Standard NVM Express Controller]

This issue is unrelated to the K2000 appliance and therefore support is not provided.

Workaround: The following workaround is available as is, without support. For more information, read the following KB article:


On the Driver Feed page, a blue arrow icon is displayed in the wrong location after upgrades.


After changing the time zone, the progress screen is displayed, but the date/time page does not appear, as expected.


Occasionally, a Mac image cannot be captured if the hard drive has a space in the name.


When the Default Boot Action is set to Boot to the Hard drive, the client machine boots into the Boot Menu through iPXE.


Munin stops updating do to large amount of graph.temp files being left behind.


When capturing a WIM image, the progress indicator does not move during the Creating file list for WIM image or Capturing WIM image stages.


When entering command parameters for an application pre-, mid-, or post-installation task, if the parameters are not specified using all lowercase characters, the task engine does not record the parameters correctly.


When creating a new LDAP server, the Test button does not work as expected.


A warning about sysprepped-images appears, even if formatting takes place in a DiskPart script.


Some models freeze during the initializing devices stage, and is not able to get the KBE menu when UEFI PXE booting.


When an RSA is using offboard storage, Mac client machines are unable to boot in NetBoot from the RSA.


The K2000 appliance cannot boot to iPXE (for UEFI) on a virtual machine (VM)created on ESXi 5.x with the network adapter setting NIC set to E1000E.

Workaround: Configure the VM network adapter setting NIC to E1000.


Windows XP scripted installations fail when deploying through WINPE10, a KBE created using ADK (Windows Assessment and Deployment Kit) 10.

Workaround: Use WINPE5, a KBE created using ADK 8.1, to successfully deploy Windows XP Scripted Installs.


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 K2000 IP at the bottom of the screen. Also, the deployment progress can be observed in the K2000 Administrator Console.

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


Scanning Windows XP user states using Windows USMT (User State Migration Tool) 5 or USMT 10 remains in progress intermittently on the K2000 server.

Workaround: Windows XP user states can be scanned with Windows PE, which is the workaround recommended by Microsoft. For more information, visit


Editing a file with Notepad.exe or editing the Registry is not working properly while using Windows PE 10.0 in K2000 Boot Environment (KBE) Recovery Console.


When the PO task join domain successfully associates a machine to a domain, it is incorrectly logged as failed in deployment log.


After successfully deploying a MAC image, the progress status is not updated properly.


Online user states captured from Windows 7x86 are not successfully deployed to Windows 8.1x64.


An Explorer window opens during the Windows PO tasks when deploying Windows 10.


If you attempt to enter konfig for the login and password on the console to make changes to the 3.7 SP2 appliance, an error for incorrect link aggregation IP and details is displayed if link aggregation is enabled.

Workaround: If link aggregation is enabled, go to the Network Settings page to enter the hostname and IP address.


The Appliance Performance page does not display disk usage for external storage.


When you create a Windows or Mac® boot environment from a FreeBSD 10 ISO, the boot environment is not set by default on the General Settings > Default K2000 Boot Environments page.


When you close or cancel an alert or warning message, the message re-appears when you navigate back to the Dashboard page or refresh the Dashboard page.


Imported ASR image deployments fail if no ASR images were captured from the K2000 appliance.

Workaround: Create the ImageStore folder in the petemp directory.


When you click Save after editing a file in a K-Image, the Commit and Revert options disappear, and the edited file no longer appears in the image file browser.

Workaround: Duplicate the image to display the Commit and Revert options, and to display the original file in the image file browser.


An application-type pre-installation task that contains a batch file within a ZIP file fails to execute.


If you boot a 10.9.2 Mac® device in to NetBoot image, and the appliance is set to a locale other than English, the keyboard layout does not display the specified locale.


When a scan user state task fails, and you attempt to retry the task from the Task Error page, the status displays as succeeded. However, the selected user states are not scanned or uploaded to the appliance.

Workaround: Reboot the target device from the Task Error page, then boot the device back in to the KBE and restart the deployment. Rebooting the device creates a new working directory for the USMT profile data so that the profiles can be captured successfully.


Device names are not retained while deploying sysprepped K-Images and scripted installations for x64 and x86 Japanese Windows® operating systems.


When performing manual upgrades, sometimes the upgrade process is not visible in the K2000 Administrator Console.


If the license for the K2000 appliance reaches its maximum limit, and you boot a Mac® device that is not in the K2000 Device Inventory, the error message License exceeded does not display on the target device. Instead, the target device continues trying to boot from the appliance.


The K2000 becomes inaccessible when you attempt to access the Package Management page if an offboard-storage device connection to the K2000 is lost.


Table 4. Hyper-V known issues

Known issue

Issue ID

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


The RSA status does not automatically update when a synch is completed.


The Network Utilization section on the Dashboard page does not display information for Hyper-V® platforms.


When you run the K2000 on the Hyper-V platform, the Hyper-V console continuously displays the error message, runtime went backwards.

Workaround: The K2000 does not require modification. You can ignore the message and continue with the deployment.


Table 5. Multicast deployment known issues

Known issue

Issue ID

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:


Deleting a multicast deployment does not terminate the process. This means that you cannot start a new multicast deployment.

Workaround: Adjust the deployment timeout period. The default multicast deployment timeout is 10 minutes.


Multicast deployments do not continue on errors.

Workaround: Do not set multicast deployments to continue on errors.


Table 6. Remote Site Appliance known issues

Known issue

Issue ID

The RSA becomes inaccessible when you reboot the RSA during reverse migration from offboard to onboard storage.


When attempting to upload media to an RSA, the Media Manager displays the error message: Invalid Response: Please check the hostname provided.

Workaround: Verify that the hostname or the IP address is the hostname or IP address of the K2000, and not the RSA.


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 K2000.


Table 7. Drivers known issue

Known issue

Issue ID

An issue occurs while injecting drivers if a forward slash (/) is present within a manufacturer’s name.


Table 8. Scripted Installations known issue

Known issue

Issue ID

A Windows 10 64-bit scripted installation does not show a that a Boot Environment is available when one actually exists.


Table 9. Media Manager known issue

Known issue

Issue ID

Downloading the Media Manager from the Latin American Spanish K2000 appliance displays the Media Manager product name in Spanish (Spain) on the MSI Installer and on the shortcut icon.


System requirements

System requirements

The minimum version required for installing version 4.1 is 4.0.695 (version 4.0). 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, then click About K2000 at the bottom left of the window.

Before upgrading to or installing version 4.1, make sure that your system meets the minimum requirements. These requirements are available in the K2000 technical specifications.

Product licensing

Product licensing

If you currently have a K2000 product license, no additional license is required.

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

Related Documents