@Romain-0 I cannot read the Francais, but I have seen this message before.

Have you disabled Secure Boot? Can you boot with a built-in network card as opposed to a USB one?

@brakcounty According to the installer code, it’s in $sslpath/CA/*. It also appears in your /opt/fog/.fogsettings file, under sslpath=.

By default, the installer drops it all into /opt/fog/snapins/ssl (lib/common/functions.sh L#1879)

OK, I’ll update, then report back. Thank you.

@george1421 My driver injection script (which I believe is the “new” one above) works with 21H2 golden images on both Windows 11 and Windows 10.

@Kureebow USB Booting instructions:

https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media

This feels much better!

Upgraded Fog to 1.4.4, and captured the image, deployed it, and was presented with my AD Login screen! It logged me in, then restarted… Then let me log in properly.

A couple things I need to change on the image, but over all, this is much better than where I was before! Thank you for the advice

@sebastian-roth I’ll help whereever I can.

I’m a jack-of-all-trades SysAdmin, can write tutorials/documentation, and do some simple bash scripting.

@sow20 Are there any error messages that appear when it restarts the capture?

Can you try building your image in a VM so you can take advantage of snapshots? Snapshot before SysPrep, snapshot after SysPrep, reboot the VM and check things work, then revert to the snapshot and try to capture the image.

This worked! Thanks!

I’m disappointed Microsoft’s method doesn’t work anymore, it was super helpful when we were testing Windows 10 at my previous site…

@Scootframer On your server, navigate to the folder you downloaded fog to, and run git checkout dev-branch. Then, re-run the ./bin/installfog.sh script to install the latest version.

If you only have 3.9 GB of free space, I’m going to guess that it’s running out of space before it can set the permissions (but someone else would have to verify that for me). The partitions are supposed to be saved into that dev folder until captured, then it gets moved over and renamed.

@Sebastian-Roth I didn’t know about the 100% option - I like that!

@RogerBrownTDL Try this instead:

lvextend -L +398g ubuntu-vg/ubuntu-lv --resizefs

@RogerBrownTDL Yes.

lvextend - Increase the volume size
-L - Specify the size to increase it by
ubuntu-lv - The name of your logical volume (as reported)
--resizefs - Resize the EXT{2|3|4} file system

@RogerBrownTDL

lvextend -L +398g ubuntu-lv --resizefs

You may need to reboot for it to take effect. This will use all the remaining LVM volume space for your logical volume. You can’t go smaller after the fact, so be sure you want to use it all first.

@Scootframer Hmmm… I’m not sure off the top of my head. I know I’ve seen this issue before, but I do not recall what the fix was.

@Scootframer ls -la /images?

@Scootframer To verify what it is first, run ps aux | grep 2643. Then run kill -9 2643 to forcefully kill it.

@Scootframer Oh good!

Anyways, I would try the latest dev-branch and see if the issue persists. If not, then we would start looking at the logs on the server.

@Scootframer On your server, navigate to the folder you downloaded fog to, and run git checkout dev-branch. Then, re-run the ./bin/installfog.sh script to install the latest version.

If you only have 3.9 GB of free space, I’m going to guess that it’s running out of space before it can set the permissions (but someone else would have to verify that for me). The partitions are supposed to be saved into that dev folder until captured, then it gets moved over and renamed.

@Scootframer Can you confirm you’re using the latest FOG version in the dev-branch branch?

How full is your /images partition/drive? Is it a local drive on your server or an NFS mount? Does /images/a4bb6d84ebf4 exist on your server?