Error when creating a KBE
I following the following steps below, and keep getting an error when trying to create this new KBE.
TitleUEFI Image Process
DescriptionImaging of UEFI enabled systems requires changes to the process for deploying Scripted Installations and System Images.
CauseTablet and UEFI imaging is different from standard Laptop and Desktop imaging in a few key ways.
- UEFI enabled BIOS requires the OS to have a specific partition structure, including an EFI partition.
- Tablets are generally UEFI mode only devices. This prevents standard PXE boot initiation of an imaging process from the K2000.
- UEFI can be disabled in some laptop and desktop devices through the BIOS. This will allow you to use a standard legacy image and PXE boot the system. Due to the varied BIOS versions, consulting the hardware manufacturer for these settings is recommended, however, it typically involves disabling UEFI boot and allowing Legacy ROM options or similar.
Tablets, by themselves, often lack the physical NIC needed for network connectivity during the imaging process. Docking stations or USB hubs and Ethernet dongles may be necessary for the imaging process.
More information about UEFI vs Legacy BIOS Imaging can be found in KB Article 190265.This KB article assumes imaging of a Windows 8.1 OS. Adjustments for Windows 10 OS will be noted at the end of the article. This best practice method also does not include recovery partitions or other partitions often included in the base OEM setup your device may have had when shipped. This procedure removes all partitions supplied by the OEM on a device. If the recovery and other partitions are required, adjustments will need to be made in the partition structure for initial setup as well as Pre-Installation and Mid-Level tasks setting up the UEFI partition structure and boot files to accommodate for the extra partitions.
ResolutionCreating UEFI K2000 Boot EnvironmentPre-Requisites
- Windows ADK for 8.1 http://www.microsoft.com/en-US/download/details.aspx?id=39982
- KBE Driver Pack 5 https://support.quest.com/k2000-systems-deployment-appliance/download-new-releases
- K2000 Media Manager
- 1 GB or larger USB thumb drive
Note - In some cases, the specific network and storage drivers for the device will be necessary, as well as drivers for your NIC dongle. These need to be the extracted driver files for Windows 8.1.
Creating the KBE
On your technician computer:1. Download and install the Windows Assessment and Deployment Kit (WADK) for Windows 8.12. Download and install the K2000 Media Manager from your K2000 Deployment Appliance.3. Download and extract the KBE Driver Pack 5.4. (Optional) Download the network, storage and other custom drivers and extract if needed.5. Navigate to \\YOURK2000\drivers in windows explorer. (Replace "YOURK2000" with the IP address or Hostname of our K2000.6. Copy the contents of the PE5 driver pack to the KBE_corresponding_system_ architecture folder in the K2000 drivers share.
7. Copy the Customer extracted drivers to the KBE_corresponding_system_architecture folder in the K2000 drivers share.
Note: The KBE driver folders are labeled kbe_windows_x64/x86. Do not put the drivers in the OS labeled folders. Further instructions for adding the drivers to the KBE can be found at: https://support.quest.com/kb/111719 If you are using a 3rd party USB NIC during this process you will need to acquire the drivers from the manufacturer and load them to the correct folder at this time8. Close the KBE Drivers Share folder.9. Launch the K2000 media manager.10. Enter the IP address of your K2000 Deployment Appliance in the K2000 Hostname field.11. Enter the password for your K2000 Driver Share in the Samba Share Password field.12. Select the “Create K2000 Boot Environment” Tab.13. Provide a name for your Boot Environment.14. Select the correct architecture for the OS you intend to capture or deploy.15. Select your language.16. Confirm that the path to the appropriate Windows Kit is correct.17. Click the Start Upload button.
18. Your KBE will now create and upload to the K2000 Deployment Appliance.
There are no answers at this time