OK, well, as an update, It looks like I was banging my head against a bad repo for the php stuff
I walked through the logs of a successful install (by a colleague) and compared them.

All is good now.

Thanks

@george1421
It was worse than i thought.

Ubuntu wouldn’t start so it looks like a complete refresh 😞

They do occasionally have different or old BIOS versions, which I update after Windows is finished loading. But they all have the same settings.

@Wayne-Workman Thanks. This is very helpful

FINALLY!! I figured out the problem. It would always fail the PXE boot in legacy and for some reason I used EFI PXE boot and it now works on this laptop.

@Sebastian-Roth

Yes found this Wiki when I was migrating, thank you

@Sebastian-Roth

Thank you for your help!

@Quazz

You are absolutely right. I always struggle to keep the copying behavior between Linux and robocopy. Sure enough there was a snapin folder inside of the snapin folder. I thought that I had checked that but probably just saw that files were there and did not pay attention to the path. The hashes now exist and I saw that in the logs that it was generated and deploying of those snapins now work as expected.

I appreciate everyone’s help and willingness 🙂

Got it! Thanks.

@David-Raymond said in Cannot find disk on a new Dell Latitude 7400 2-in-1 using FOG:

I have for testing using the dock that came with them.

Just an additional comment. The WD19 docks that come with the 7400 give marginal support for PXE booting. Sometimes they show up and sometimes (most) of the times pxe booting isn’t an option. The older WD15s and the usb-c dongles work 100% of the time.

You may be limited in running FOG inside virtualbox on the 6430. FOG running on bare metal on the 6430 would be just fine for a deployment only system. I would swap out those 6430 delivered hard drives (which are slug speed slow) with an SSD drive. That SSD under windows will make the 6430 fell like a new computer (even at twice the weight of a 7280). Good luck with your deployment. FOG should perform well for you.

We’ll keep track of this on github:
https://github.com/FOGProject/fogproject/issues/328
https://github.com/FOGProject/fos/issues/28

Would you share a screen shot of the error you see on the Dells?
Also what model of Dells do you have issues with and lastly what version of FOG are you using?

Sebastian, thank you. That was it exactly.

@mkeane What do you see in the fog-client log now??

@SBrady I myself have been bitten by web filter issues before on my linux FOG box, so no worries there haha! If you need any additional help or if you run into any other issues, please feel free to open another thread.

nfs addresses have to be written like 192.168.1.2:/nfs (notice the :)

@Sebastian-Roth @george1421 Thank you both. I am most likely eventually going to move to using FOG dhcp so I am not going to go too crazy with this. Was just curious as to if this was a known issue with a workaround. Just using our hq dhcp for the time being for testing.

@Polar-Bear said in Fog 1.5.7 can not capture second image (Debian 10 'Buster'):

For me it is a mystery, on my part I have repeated same steps without any deviation and if earlier it produced described error now it works fine.

We have seen this exact error reported by other users and I am still unable to reproduce the problem and find the real cause of this. Not really sure what to do about it. Seems to be something that does not occur for everyone (obviously) but it’s still around. I even don’t know if it’s something fixed by a reboot or not.

And this time when I was creating new image in web interface I found that now instead of dashes ‘-’ replacing spaces ’ ’ it has removed them!!! Does anybody working on code right now?

I suppose what you are referring to is in management/js/fog/fog.image.js and has not been changed since August 2017 as you see in the github commit history. Which version of FOG did you use before?

@blong10 The fog server really doesn’t do a lot in the imaging process. I would give it at least 4GB of ram to release some of the memory constraints though. The only thing the fog server does is move the image from the network to the disk. It doesn’t process the image at all. Depending on the number of FOG Clients you have a 2 vCPU VM with 4GB of RAM is sufficient.

@doggiebone said in Isolated Network - Operation not supported:

resolv.conf kept being over written but I found an article that sort it out.

This almost sounds like your FOG server’s IP address is being set by dhcp? If that’s the case you need to set it static or you will have problems since the IP address is hard coded into the configuration when the FOG server is installed.

Well done on the rest of getting it setup.

@tbaumann Again: Also make sure SELinux and firewall on the FOG server are disabled and TFTP is running! https://wiki.fogproject.org/wiki/index.php?title=CentOS_7#CentOS_7_pre-config