Full UEFI-Deployment Support for Windows 7 x64



  • Hi everyone,
    first of all FOG is a very nice software!

    Here is what i would like to be implemented within the next releases:

    I install Windows 7 x64 on an UEFI-machine, which works fine. Then I image that machine by choosing the image to be a “Multiple Partition Image - Single disk” due to Windows-setup creating 3 partitions during the installation process. Imaging works fine as well. I end up having 4 files on my storage node:

    [CODE]-rwxrwxrwx 1 root root 512 2012-03-26 14:20 d1.mbr
    -rwxrwxrwx 1 root root 9524580 2012-03-26 14:20 d1p1.img
    -rwxrwxrwx 1 root root 81928954 2012-03-26 14:20 d1p2.img
    -rwxrwxrwx 1 root root 13405024509 2012-03-26 14:28 d1p3.img[/CODE]
    Then if I deploy that image so the very same disk, which already has Windows 7 installed (incl. the 3 partitions mentioned above), that works fine as well.
    But if i format the disk and delete all partitions (or just insert an empty disk), i am not able to deploy the image.
    What i can do, is to start Windows-setup unto the point where it creates all the partitions, then abort setup and start deploying the image. The deployment finished correctly but the system won’t boot whatsoever. Unfortunately the Windows repair tool doesn’t fix the problem.
    Maybe you can implement a corrrect deployment of UEFI-partitions including correct partitioning and boot-settings. That would be very nice!
    Or just tell me, if I’m doing something wrong. :)
    Thanks in advance!



  • Seems like I am stuck in a similar place. At this point I can image and deploy from fog, but after that I cannot get the computer to boot from the hard drive without manually going to each computer and changing the boot order in the bios.



  • Same for me, i have trouble with UEFI…
    is there some news with fog 0.33 and UEFI ? (pbs with Lenovo m72e and laptop lenovo x220i, x230i & HP6570b)



  • Any update on this? We’ve got some Win 7 units that have no trouble making images, but will not deploy.



  • Will Fog work at all with UEFI? I have a Gigabyte Z68XP-UD3 with UEFI BIOS and I don’t think I can boot legacy BIOS.

    It starts the pxe boot, downloads something ok, then the screen scrolls too fast for me to see what’s happening and it goes into normal Win 7 x64 boot.

    I have been able to back up other machines so I know it’s working (though I have to type [code]sudo stop/start tftpd-hpa[/code] every time I use the system as that won’t work automatically.

    Any thoughts on how I can backup this UEFI machine or should I just wait?

    Many thanks.



  • Just got hit with this issue on a couple new HP’s for a lab. Hoping I can work through it by disabling [SIZE=12px][FONT=Arial][COLOR=#333333]UEFI[/COLOR][/FONT][/SIZE]

    [SIZE=12px][FONT=Arial][COLOR=#333333]EDIT: I was able to skip all my problems with UEFI by physically moving the sata port the dvd drive was plugged into on the motherboard, then booting to the legacy atapi option. That allowed me to skip the whole GPT issue.[/COLOR][/FONT][/SIZE]


  • Developer

    I know Chuck & Jian are looking at UEFI support. The biggest problem right now is pxelinux. We are looking at moving to iPXE (or gPXE, or whatever the latest incarnation is).



  • Hi,
    i used Dell Optiplex 790 and 990 systems for testing purposes and e.g. a Western Digital WD800JD disk.

    Now with HP 8200 Elite computers:
    If i deactivate (U)EFI in the bios and use the legacy bios mode it mostly works fine (after using sysprep). So i strongly guess that FOG has an issue with the (U)EFI partition and its boot settings.
    As i mentioned above FOG doesn’t even create the needed partitions (3 when installing Windows), so the imaging cannnot succeed.



  • I have UEFI systems. I can take a look at this and see if I can duplicate it. However, can you tell me the make/model of your systems and the make/model of the disk drives you having this issue with?


Log in to reply
 

530
Online

39008
Users

10721
Topics

101837
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.