• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All categories
    • L

      Deploying captured Windows 11 golden image using FOG results in Windows only being able to boot into recovery

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Windows Problems
      2
      0 Votes
      2 Posts
      14 Views
      M

      @lucamathuse Hi. I have faced similar situation on HP. I think your computers are going into recovery because the BIOS hasn’t updated its boot entries. So it still thinks it should load the old OS.

      From the steps, I saw you fiddling with the Boot entries. I’m not familiar with that method, but at least on my computers, I don’t need to change anything. Just a sysprep -> Shutdown and capture.

      Have you actually tried investigating whether the data has been copied to your disk? Do you see the boot directory? You should be able to drop into the CMD from that recovery or advanced option and investigate that.

      I have deployed Windows 11 while the image type was Windows 10, and never needed to change anything.

    • K

      Windows 11 | 65x HP Z2 Tower G1i

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      3
      0 Votes
      3 Posts
      421 Views
      M

      @kratkale said in Windows 11 | 65x HP Z2 Tower G1i:

      Can I specify in FOG which hard drive to clone to? For example, using the serial number? That could be stored in the host entry

      Hi, this is a known issue when using NVMe, as you’ve probably already discovered. I’m not sure whether FOG 1.5 supports using serial numbers to target disks, but someone from the team may be able to confirm that. FOG 1.6, however, does support targeting disks by serial number.

      I ran into the same situation. As a workaround, I customized my init.xz to use the PCI path instead, since those appear to be more persistent.

    • J

      EFI Stub Errors on XCP-ng Virtual Machine Attempting 'Perform Full Host Registration and Inventory'

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      16
      0 Votes
      16 Posts
      809 Views
      J

      @rodluz I tried a manual installation of the updated init.xz as outlined in your instructions, and there was no change. I also upgraded my FOG server and reinstalled your experimental XCP bzImage from earlier in this thread but did not see any change in VM behavior after doing so.

      Out of curiosity, @BPSTravis, what hardware are you running XCP-ng on? I know it’s virtualized, but maybe there’s some CPU feature I have disabled in BIOS on my XCP hosts or something like that?

      Also, thanks for your patience. I’m only available to work on this once or twice in the middle of the week as I’m part-time with this organization.

    • L

      Trying to deploy Windows 11 25H2 using FOG always leads to the Windows recovery screen

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Windows Problems
      6
      0 Votes
      6 Posts
      112 Views
      F

      @lucamathuse
      I don’t remember if it’s related to Win11 we have this in our postdownload script :

      if [ -n "$hd" ]; then if [ "$hd" = "/dev/nvme0n1" ] ; then partsys=$hd'p2' partdata=$hd'p3' else partsys=$hd'2' partdata=$hd'3' fi

      We use Virtualbox, install classic WIndows 11, disable Bitlocker, and capture with FOG with image set to “Multiple Partition Image - All Disks”
      My folder capture :

      d1.mbr d1p1.img d1p2.img d1p3.img d1p4.img d1.partitions d1.size

      Maybe try capture debug to see which partition FOG get during your capture

    • 1 / 1