Resolved issues
Resolved issues
The following is a list of issues resolved in this release.
|
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. |
|
|
The Driver Feed page was not displaying a blue arrow when a driver was updated or new. |
|
|
Some UEFI-enabled machines would not boot to the local hard disk after loading the iPXE menu. |
|
|
Photos were not being removed from /Applications on Mac OS X 10.11, on NetBoot creation. |
|
|
jQuery is removed from the online help (Administrator Guide). |
Known issues
Known issues
|
The Boot Manager Password feature does not function in the new UEFI-compatible booter. |
|||
|
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: https://support.quest.com/kace-systems-deployment-appliance/kb/185551 |
|||
|
On the Driver Feed page, a blue arrow icon is displayed in the wrong location after upgrades. |
|||
|
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 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. |
|||
|
Workaround: Configure the VM network adapter setting NIC to E1000. |
|||
|
Workaround: Use WINPE5, a KBE created using ADK 8.1, to successfully deploy Windows XP Scripted Installs. |
|||
|
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. |
|||
|
Workaround: Windows XP user states can be scanned with Windows PE, which is the workaround recommended by Microsoft. For more information, visit https://social.technet.microsoft.com/Forums/en-US/83ddb84e-d919-4acc-91ca-78d4f1478df1/scanstateexe-from-usmt-50-from-windows-81-adk-fails-on-windows-xp-with-1-is-not-a-valid-win32. |
|||
|
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. |
|||
|
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. |
|||
|
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. |
|||
|
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. |
|||
|
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. |
|||
|
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. |
|
|
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. |
|
Workaround: A workaround is available for this issue. For more information, read the following KB article: https://support.quest.com/kace-systems-deployment-appliance/kb/212975 |
|
|
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. |
|
|
|||
|
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. |
|||
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.
|
• |
|
• |
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.