@Arjenbulkens I also wonder if its the full name of the base key that is at fault?

HKLM, HKCU, HKCR, HKU, and HKCC is from the MS doc for reg add
ref: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/reg-add

@Arjenbulkens This should work. But to debug what happens if you only run the delete command? Right now its not clear which command is causing it to hang, I might guess the delete key.

I also wonder what the logic is to delete the key and add it back, why not just use the add key to change its value?

@oleg-knysh This is a very strange issue. The only recommendation/question I have at the moment is what version of the FOS Kernel are you using? The latest version is 4.19.64

I also wonder if you update to the latest version of FOG (1.5.7) to see if any of the fixes since 1.5.4 will address this issue. I don’t have a high confidence that it will fix this speed issue. I know it will solve some disk structure problems.

@gpd187 said in Cannot PXE boot target capture device.:

I boot to the network with will not load the undionly.kpxe

Realize that undionly.kpxe will only boot on bios (legacy) based machines. For uefi based machines you will need to send ipxe.efi

e both Virtualbox VM’s

For virtualbox make sure you are using a bridged connection to your network and not natted

And also created a symbolic link undionly.0

FOG doesn’t use undionly.0 files. That symlink is not needed.

So lets start out with what is your dhcp server for this network?

What do you have configured for dhcp options 66 and 67?

Pick a physical computer to test with:
What mode is the firmware in? (bios or uefi).
From a physical computer on the same subnet as the FOG server, can you ping the FOG server?
When you PXE boot the target computer and receive an error, snap a picture of the error on the screen and post the picture here. We need to see the context of the error message.

@Arjenbulkens OK what is the command you are using inside this batch file to delete the key?
The FOG Client runs as the user SYSTEM, so it should have full access to delete from HKLM. I’m still leaning towards an unanswered prompt doing this.

@Arjenbulkens said in Snapin Batch file stays in-progress:

The batchfile deletes a registry key

What is the base path for the key? (HKLM, HKCU,??)

@chunter2 Leaving it won’t hurt anything. One might think, if its working now its good enough.

@brakcounty Ok so it was installed using the tarball method. That way will work too. You will then just download the 1.5.7 tarball and extract it. That will create a directory called "fogproject-1.5.7” change into that directory and then the bin directory. Inside there key in ./installfog.sh The installer will run and ask to confirm a few settings and then it will upgrade the program code. You will/must have internet access for the installer to complete.

@chunter2 Rerunning the FOG installer “should” have fixed any sins from the past (with the exception of custom settings in the fog configurations like your kernel name)

@chunter2 Interesting because the directory /var/www/fog should be linked to /var/www/html/fog The issue was ubuntu had one path and centos/rhel had a different path. So the developers created the link directory to satisfy both camps.

So now does things work or not? For this 3040 are can you run the FOG compatibility test from the iPXE menu?