Encoutered my first UEFI machine recently and it is failing on our standard WIM image deployment via K2000. I have adjusted the bios settings to allow booting into to the KBE environonment however each time the imaging is failing while partitioning and formatting the hard drive. What little documentation from Dell states we should take a UEFI machine and build it out like we want, upload the image, and then use that image for our other UEFI hardware. 

Is this case or would we be able to utilize our standard image somehow? 

Answer Summary:
Cancel
1 Comment   [ + ] Show Comment

Comments

  • Well it appears I have the direction needed - thanks all. Will not utilize any legacy options in the BIOS and go with UEFI - upload a master image and use that for deployment.

    Thanks everyone for your help!
    • I did mine this way after learning I had to rebuild it. It's worked for me, and easier to maintain.

      http://www.itninja.com/blog/view/kace-imaging-capture-uefi-partions-vm-workstation
      • Thanks for the link - I like VM idea!
Please log in to comment

Community Chosen Answer

1

You need to boot with a "UEFI" boot stick for both the capture and deployment.

The wim needs to be also captured from a uefi master.

Answered 04/07/2014 by: SMal.tmcc
Red Belt

  • Can I change boot list option to Legacy which allows me to PXE boot to the KBE or should I keep it UEFI? Also clearly see now that the existing wim image will not work and I will need to upload a uefi master for deployment.
    • has to be 100% uefi. Bios and all
Please log in to comment

Answers

0

Existing images work like a charm for us, as long as they are x64. If they are x64, you can either use them with BIOS or UEFI machines. I made a script we run as a pre-install task that detects whether the machine is running in EFI mode or BIOS mode, then partitions the HDD accordingly. After that, apply the .WIM to C: (like you always do) and at the end, run c:\windows\system32\bcdboot.exe c:\windows and it will automatically create the proper boot files/entries (if it's in BIOS mode, it will create the BCD files on D: [the 100MB system partition], and if it's in EFI mode, it will create the entry in the EFI firmware.

The key is to boot to the proper KBE: if you PXE boot, it will only work in BIOS mode. For EFI, you need to create an EFI boot key using Rufus, then boot to that key in EFI mode.

But as I said, you can use one .WIM for both worlds, even works with Secureboot once imaged.

Answered 04/08/2014 by: SwissJay
Senior White Belt

  • Hey SwissJay, That's great! Why don't you share how you are doing this?
    • Even though we are now using SCCM for imaging, I'll try to get a package put together with the scripts, documentation will be minimal though since I can't throw a whole lot of time at this.
      • That would be awesome, Thank you!
Please log in to comment
0
I have not found how Swiss Jay is able to detect Legacy Boot vs UEFI, however I was able to deploy a  Image to a UEFI system after booting via PXE Boot (Legacy) to the K2000. The BIOS on my OPT9010 allows me to configure for UEFI but enable a legacy boot option as well. By doing an F12 on boot, I am able to choose the Boot to NIC option and do my traditional PXE boot my K2000. Then my Image deployment is configured to create all the UEFI partitions and apply the image. The deployment first uses a DiskPart preinstallation task to create all the UEFI partitions, then after the image is applied, in a MidLevel Bat Script Task I create the EFI Boot Partion. See Below:

Create the Pre-installation Task (Diskpart Type) as follows:

select disk 0
clean
convert GPT
create partition efi size=499
select partition 1
format fs=fat32 quick label=system
assign letter=h
create partition MSR size=128
create partition  primary size=235125
select partition 3
format fs=ntfs quick label=windows
assign letter=c
create partition primary
select partition 4
format fs=ntfs quick label=recovery
Exit

Then Create a Post-Installation Task (BAT Script Type)

Note - When you set this Task to '2000 Boot Environment (Windows)' it becomes a Mid-Level Task. Create the Bat script in the task as follows:

@echo on
bcdboot c:\windows /s h: /f UEFI


This will create the Microsoft EFI partition you need to boot the UEFI image you deployed.

This worked for me I hope it helps you. Booting 200 machines with a USB stick is not practical for me :/

Joe

Answered 03/18/2016 by: jjvillani
Yellow Belt

Please log in to comment
0

Are you using the "Create UEFI Partitions" preinstallation task? This will convert the disk gpt and partition for UEFI systems...

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
Exit

Answered 04/07/2014 by: jegolf
Red Belt

  • I am attempting to use this pre-installation task however when I save system image I receive error message: To deploy the sysprepped image, attach a pre-installation task to format the disk.
    • Select the "Remove local files not in image" checkbox. This will remove the message you are seeing.
      • This is a wim image so I do not see this option - I noticed the option does exist if it is a k-image.
      • if you are using "clean" option in diskpart no files would exist. all tables are destroyed and recreated.
Please log in to comment
Answer this question or Comment on this question for clarity

Share