Best posts made by lukebarone

@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.

@kalafina So that’s showing that the DISM command doesn’t like spaces, even when surrounded by quotation marks.

I’d suggest creating a simple .CMD file and running that. For example (untested):

@echo off
copy /y \\server\share\appassoc.xml C:\
dism.exe /online /import-defaultappassociations:C:\appassoc.xml

Obviously, replace \\server\share with a path that is network-reachable from your client.

…

On the other hand, looking at your “Snapin Command read-only”, it looks like you have a syntax error anyways - the appassoc.xml part should NOT have a space before it when including the path.

Another thing to try is instead of running the cmd.exe, run dism.exe for the Snapin Run With, Argument set to /online /import-defaultappassociations:, and see what that produces?

@kalafina I use Samba on a file server. Since you’re running Windows clients, it should work with minimal setup. You need to ensure that wherever the file is stored that the computer account can access it, not necessarily just the user.

But you are right - FOG is defaulting to adding the uploaded snapin file to the end of the command line. There is a walkthrough for adding a Wi-Fi key as a snapin that includes how to upload a ZIP file and run a command from inside - I’d recommend trying that if the above isn’t working.

https://www.youtube.com/watch?v=M-HXtqeukks