All set - it was the files being sent to a single filename * - that was just a syntax error on my part for using the Windows cli too often.
@Wayne-Workman - i had to change my /opt/fog/.fogsettings file back to pointing the storage at ‘/images’ because the entire imaging process breaks. Also re-added my /etc/fstab line to point /images to the home directory where the 177G volume is. I understand you think my system will fail if I fill up more than the 50G available on the root drive, I’m confident it won’t. Thank you greatly for your assistance, it was the file copy problem.
@EAHarvey You might want to check your /images folder contents, though.
The way image capture works is they get placed in /images/dev first and then at the end they get moved to /images and renamed to the proper destination name.
This moving process uses FTP, failure to move them indicates some sort of issue with that, most likely credentials, but if you’ve recently run the (trunk) FOG installer, this should already be corrected in the mean time.
@Sebastian-Roth I will do that on all the Dell computers we have, and post the output (sorry, working on School Startup, and dealing with the teacher laptops right now). Can I somehow use FOG to boot to a shell and run those commands? Or do I need to boot up Debian and run it from the Live environment?