-
标题
UEFI Image Process using USB key -
说明
Imaging of UEFI enabled systems requires changes to the process for deploying Scripted Installations and System Images. -
原因
Tablet 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. -
解决办法
Creating 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 time
8. 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.
Creating a UEFI Bootable USB Key of the KBE
Once the KBE from the previous section has been successfully created and uploaded to the K2000, we can create a bootable USB flash drive image for it.
1. Login to your K2000 appliance and browse to Deployments > Boot Environments. Find the boot environment that you created and uploaded in the previous section. Click on the name to open the KBE properties.2. There will be a checkbox near the bottom of the properties section that says “Create bootable USB flash drive image for this Boot Environment”. Check that box and wait for the creation to complete.3. Upon completion you will have a new link available. Click “Download bootable USB flash drive image for this Boot Environment”. Choose where to save your download and allow the transfer to complete.4. Unzip this downloaded package and locate the install.exe file at the root of the folder. Double click this file. The K2000 UFD Boot Environment Installer will appear. We are working with UEFI images in this document so choose your destination flash drive, and choose the radio button for FAT32/UEFI. Click format and install to write the bootable image to your flash drive.
Preparing your System for Image Capture
Installing OS and customizing base image
Scripted InstallationIt is highly recommended to install your base OS via a K2000 Scripted Installation, using Volume License Media. Using non-Volume License Media is against Microsoft Licensing. https://support.quest.com/k2000-systems-deployment-appliance/kb/135252This Scripted Installation needs to have the built-in Create UEFI partition task as your pre-installation task to setup and format the correct partitions for a UEFI OS. For more information about a new Scripted Installation, please see the K2000 Administrator Guide.Manual OS Installation
Alternatively, if you wish to manually install the OS on the device, please use the following DISKPART script to properly format the drive prior to OS installation.Select disk 0
Clean
Convert gpt
Create partition efi size=200
Assign letter=s
Format quick fs=FAT32
Create partition msr size=128
Create partition primary
Assign letter=c
Format quick fs=NTFS
ExitAfter the base OS is installed, install applications, updates and other desired configuration changes to the system.
Sysprep ProcessAt this point we have created a USB KBE and are almost ready to capture our image. If you have already configured your system with the desired applications and configuration settings, we can run the Sysprep Creator Wizard to prepare the system for capture.
The link to the latest version of the K2000 Sysprep Creator Wizard can be found under the “Tools” tab of your K2000 Deployment Appliance.
1. Download and install this application, typically on your technician workstation, not the Base OS system. Launch the Sysprep Creator Wizard, choose the desired operating system, and select Create Unattend and Executor then click Next. Fill out the fields in each of the 4 tabs as needed.2. Complete the Sysprep Creator Wizard and click the Create button. You will now be asked where to save the unattend.xml. Copy the unattend.xml and sysprep_executor.exe to the machine you wish to sysprep.3. Run the sysprep_executor.exe file, select the Shutdown checkbox, and specify the location of the unattend.xml file you copied. Select the checkbox to Delete unattend.xml from image. Click Start Sysprep.Issues that may affect Sysprep https://support.quest.com/k2000-systems-deployment-appliance/kb/184427Note: Due to Windows permissions, if the unattend.xml file is located at the root of the “System Drive”, sysprep_executor.exe will not be able to cleanup/delete it.Additionally, the unattend cleanup option will only remove sysprep_executor.exe as well as the unattend.xml file you ran “Sysprep Executor” against. Please note the unattend.xml that is created in Panther will remain.
Capturing your UEFI Image
Your system should be shut down at this point. Configure your system to boot to the KBE USB. Once the device is booted, you will see the KBE boot sequence initiate. Upon successful completion you will be presented with the K2000 Boot Environment menu.Note: If you have followed the instructions above, the selections should be identical. If you did not clear the drive of all partitions before manually installing Windows and configuring it for image capture, please re-install the operating system and ensure that you delete all existing partitions before proceeding with the install.
1. Choose Imaging > Capture Image of This Machine from the KBE menu.2. Enter a Name for your captured image.3. Select Drives C and S.4. Select the radio button for Windows Imaging Format (fast compression).5. Optional: Check the box for Force continue on errors.6. Optional: Check the box for Include debug output in log. (This typically slows down the capture process, so it is only recommended for troubleshooting purposes.)7. Press the Start Capture button and your image will now capture and upload to the K2000 Deployment Appliance.Preparing your image for deployment
1. Navigate to your image under Deployments > System Images.2. Click on the name of the image you captured in the previous step.3. Drag the built-in Create UEFI Partitions task to the left column under Pre-Installation Tasks.4. Drag the built-in Apply UEFI Partitions task to the left column under Mid-Level Tasks.5. Other needed tasks may be added at this stage so long as they do not conflict with the partitioning done by the Create UEFI Partitions and Apply UEFI Partitions task.6. Select "Use Driver Feed(only with Sysprep'd images)".7. Save your ImageNote - when using the Driver Feed Option, verify that your specific model drivers are downloaded into the feed, or for non-Dell systems, manually installed into the driver feed folder structureDeploying your Image
Follow the instructions below to deploy your image.1. Boot to your UEFI USB KBE.2. Choose Imaging > Deploy Image to This Machine from the KBE menu.3. Choose your image from the drop down menu.4. Optional: Check the box for Restart Automatically after deployment.5. Select Deploy Image. Your image will now deployAdditional notes -
If using a UEFI enabled VM for your base image, the ISO of the KBE will not work as expected for booting the VM. Please see this KB article for more details - https://support.quest.com/k2000-systems-deployment-appliance/kb/133519
Windows 10 imaging would follow a similar procedure, but the KBE should use ADK for Windows 10 and KBE Driver Pack 10. The SDA should be on the latest version.