• Server
    • FOG Version: 1.3.5
    • OS: Ubuntu 12.04 LTS
    • Service Version: 11.10
    • OS: Windows 10 Pro 1607

    Has anyone successfully imaged a Surface Pro 4? I’ve read through the “Surface Pro” section but everyone is only having issues with getting the image to deploy or upload, I was able to get the image I have built to deploy just fine but I had to turn secure boot off all together to get it to load the ipxe.efi but when it reboots after imaging the screen flickers a bunch and then it just boots into UEFI Wont even get to the “starting windows” icon.

    So two questions
    1.) Is there a specific EFI file that works with the secure boot turned on,
    2.) for those who did get it to work what partition style did you use, MBR or GPT?

  • Just Kidding :))))) I just added the other architectures under the helpful little NOTE: and it works just great! I Skim too much and don’t read enough. You guys are great.

  • @george1421 I already set up the BIOS-UEFI coexistance, but in that article it says there are several other UEFI architectures, I just didn’t know if there was some specific PCEClient:Arch:xxxxxxx architecture That is known to work with VMware

  • Moderator

    @Arsenal101 Right for efi you need to change your dhcp option 67 to an efi kernel (ipxe.efi) and not a bios kernel (undionly.kpxe).

    -OR- if you have a windows 2012 dhcp server (or linux) you can follow this document: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

  • Another Quick question, anyone have any idea what efi file works with Vmware Workstation 12 EFI? do I need to create a seperate policy on the DHCP server for it? It looks like its starts to boot PXE but breaks right after downloading the NBP file

  • Thanks @george1421 Thats exactly what I expected. I am using VMware Workstation on my Local PC just to keep the images an snapshots and whatnot off from the Datastores.
    I was using Workstation10 but it does not support EFI at all so I am upgrading to Workstation 12.5 as I speak 🙂 I will rebuild my image with EFI and GPT Partition tables and we will be good to go for those devices that are EFI only, or even the ones that come EFI but support BIOS, we wont have to downgrade them to BIOS just to image.

  • Moderator

    @Arsenal101 said in Surface Pro 4 Quarrels:

    Okay so I am sure my problem is the fact that my image is built on VMWare Workstation 10 with the Virtual BIOS and MBR Partition Tables and the Surfaces do not have a BIOS or legacy Mode at all, Just UEFI.

    This is problem #1. You can not deploy a bios (legacy) image to a uefi system (period). Reconfigure your virtual machine for uefi mode (just a radio button in the setup under vSphere) and recreate your reference image.

    If you want bitlocker enable it after the system has been imaged. That is the best (and only) route

  • Any specific way I need to upload the image?

  • Okay so I am sure my problem is the fact that my image is built on VMWare Workstation 10 with the Virtual BIOS and MBR Partition Tables and the Surfaces do not have a BIOS or legacy Mode at all, Just UEFI.
    I will swap over to the ipxe7156.efi and see if that is more reliable.
    I don’t believe bitlocker encypted the drive. I was able to reinstall the OS with the Windows 10 OS CD you download right from online.

  • Secure boot MUST be turned off during the imaging process, whether it’s deploy or capture.

    ipxe7156.efi works with the surfaces.

    GPT is fine.

    Make sure Bitlocker has not encrypted your drive.

  • Moderator

    First people seem to have better luck pxe booting with ipxe7156.efi instead of ipxe.efi.

    To your questions.

    1. Secure boot: Not unless the OS you are booting with is Microsoft Certified ($$$). Secure boot needs to be off for imaging.
    2. GPT should work with win10 just fine.

    I can tell you that FOG 1.3.5 stable has an issue with expanding/shrinking hard drives under certain conditions. I’m not saying that this is your issue, just there IS an issue under certain conditions. This issue was resolved in the 1.4.0RCx branch. Barring any unexpected new problem 1.4.0 stable will be released very shortly. You can either upgrade to the 1.4.0RCx branch or wait a little for 1.4.0 stable to be released.