I am confused about the actual syntax of this post download script.
In the sample script on the FOG server, it says:
“# syntax of the post download scripts are”
"#. ${postdownpath}<SCRIPTNAME>

(assuming the script is called (without quotes) “mypostdlscript.sh”, and it is in “/images/postinstall/” directory)
Should I be typing (without quotes) “. ${postdownpath}mypostdlscript.sh”
or should I be typing it as (again without quotes) “. /images/postinstall/mypostdlscript.sh”?
Can you explain what the ${postdownpath} means?

@Sebastian-Roth
I am using FOG 1.5.2.
On the system I a m trying to image from, the system boots to the OS with no problem it is a 960 GB SATA SSD. I have created images in the past on this same FOG server with no problem. A few months ago, I deployed an image to this host without issue. All of the settings listed worked before on other images and on this same host. I have attached a screen capture of the image settings, as well as the host settings.

I keep getting the error shown in the attached graphic whenever I try to capture an image. I can deploy an image from the same FOG server without issue. Everything I have found on the FOG Technical Help as well as through Google either is not fixed or just says something like “Thanks! That works great!” but does not say what the actual fix was. The system I am trying to create the image from boots to the OS (CentOS) without issue as well. I am pulling out what little hair I have left trying to figure this out.

I have several systems with a 4-port network card that I am using to PXE boot these systems. If I put the (PXE network) network cable into the first port on the network card (regardless if there are any other network cables plugged in), it will PXE boot without issue. If I put that same cable into any other port with no other network cables connected, the system will PXE boot without issue, regardless of which port is used. If I connect the first port on the card to a different network and then connect the PXE network to the second port, the PXE boot hangs asking for the TFTP server. Because I don’t control the network, I can’t put the PXE server on the other network, but in order for remote users to connect these systems, the system needs to have the primary network port connected to the network that I have no control over and the PXE server connected to the secondary network. The remote users need to be able to have these systems PXE boot without physical access to the systems, so switching network cables back and forth is not an option either.