@Tom-Elliott Try with the path starting with %~dp0. For example:
/c dism.exe /online /import-defaultappassociations:%~dp0\appassoc.xml
That variable will map to the current drive and path. If the appassoc.xml file is in the same folder as where FOG is running the command, it should auto-expand and auto-escape the characters (i.e. spaces).
@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?
@kalafina To confirm, you have the feature installed in your image, correct? Even though it’s not turned on until you push the snapin?
@jmcnamee Random question, why do you need to switch to BIOS mode instead of staying in UEFI? The DHCP server should give out a filename based on the architecture during the FOG OS boot. See this link for more details. You will need to disable Secure Boot in your VM though, if enabled.
In my VMs (using Hyper-V or Virtualbox), I would add the drive controllers as SATA as opposed to IDE - have you been able to capture a GPT disk with an IDE controller? I always though that was mutually exclusive.
Another option (albeit very slow) is to try wireless imaging. It can work, but it is VERY slow (i.e. a normal image taking me < 5minutes can take over an hour).
@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.
I assume you disabled Bitlocker on all your visible partitions in Windows before trying to capture?
@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)
@apmt Can you confirm for me that when you say the POST is failing that you are, in fact, talking about the POST process through the motherboard starting up, and not about Windows attempting to start up?
Have you ran a memory test on this system?
@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.
@rizingknight72 said in Windows 10 zero touch deployment:
@george1421 Thanks for the tip. I have a fog server installed and working windows machine. i still am stuck of how to sysprep properly. currently i am using the command:
C:\windows\system32\sysprep\sysprep.exe /oobe /generalize /shutdown /unattend: C\temp\unattend.xml
I got this from a college. I am not sure if this is the right way to use this. they also recommend admiin dosbox. any tips here for?
I would take the space out between /unattend: and the path to the unattend.xml file.
@kibade This is fixed in the latest dev-branch on Github.
@sebastian-roth I believe I am. The pull request I opened works on a fresh Bullseye install (does not include isc-dhcp-server if the user answers N or passes -y to the installer).
Link: https://github.com/FOGProject/fogproject/pull/522
In terms of Debian Bullseye support, I know this is working in dev-branch. I worked on just the DHCP server part that @kibade mentioned, and @george1421 mentioned.
If there is no one starting on this, I’d love to take a crack at it.
@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.
@george1421 Thanks for the input!
I’m not looking to specifically put F2B in; I am putting in code to log to a file login failures and successes, then the SysAdmin can choose to setup a F2B jail based on that. I believe heavily in separation of responsibilities, so I will definitely look into writing a proper tutorial.
Do you think code for simply logging the login attempts would get merged?
WIP - I have FOG now logging to a text file with the remote IP, and an indicator of whether the username supplied was a success or not. I’ll continue testing this next week, and report back if I get it working on new installs too.
If it works, I’ll create a merge request on Github. This has been a fun challenge so far 