@Quazz okk im creating a new account and reinstalling fog

@Wayne-Workman I shall do so

Just returning here to let everyone know that, I don’t fail due to it, but the messages will report as Fail/Done depending on the status for the removal bits and pieces.

@mp12 Looks good! I will update the official binaries tomorrow. Thanks for all the testing! Marking as solved.

Man thank you so much, we have our students save their files on SD cards and man does that screw with the mounting process for drives in FOG. Never even thought of that and my employee said today what if we take the card out, problem solved.

@Tom-Elliott @Arrowhead-IT @george1421 Thanks. I might stop make it work with 1.2 then!
I did try to upgrade to 1.2 and it just broke everything so I reverted back to 1.2
I tried setting up a new server running CentOS 7 and fog trunk but it’s not working either, just getting a blank page when trying to access the console towards the end of the install to set up the DB.
Anyway. I’ll try and set up a trunk version again!
Thanks for your help

@Sebastian-Roth You are right that firmware is for the fiber (10G) adapter. While it did fix the error in the log its not adding any real value for the OP or for FOG in general. But too, I’m still not seeing FOG as a good tool for cloning servers because of the other mix of hardware (you won’t find in desktops). I would say remove the firmware and have the OP test again now that its working in his environment (because the other roadblocks have been removed).

@plegrand psexec already has the ability to send commands to remote machines, I’m not sure why you would try to make psexec commands into fog snapins.

This whole thread seems really over-complicated.

Why not just bake-in some run-once functionality into your image? Windows already does this natively via the registry. Doing it for Linux images is trivial because SystemD is amazing.

@george1421 I might just try that, just for troubleshooting purposes.

Re: firmware - There is a BIOS update for the machines, and a firmware update for the NVM Samsung drive. Sadly, trying these was my first troubleshooting step (not listed here, because it was before I suspected components of FOG). I sure was holding my breath that it was the drive firmware though!

@Sebastian-Roth Yeah, it was honestly my fault. Normally I’d capture and deploy immediately after to test, but these past few weeks have been ridiculously insane for me and my machine to image allocations haven’t been as up to date as they normally would’ve been.

I noticed this happened once before with a Windows image, but it was related to the dirty bit and another issue I found here. All in all I wanted to at least report and give this a go, I apologize for taking your time but as always appreciate the help. If this does happen again, I’ll be sure to give those kernels a go and report back here the results.

@rocksteve69 Unfortunately I’m unsure what else to try at the moment.

@Daniel-Miller Thanks Daniel. They use puppet. I’ll shoot them an email.

Thanks again everyone for all the help.

@Wayne-Workman That IS AWESOME! Save me and my team a few minutes in config…very cool.

For others reading and who are suing FOG for the first time. PXe boots up perfectly fine, DHCP will “Spin” and then you’re machine will likely not boot past a black screen perhaps with a flashing cursor. The steps from my previous post (copied inline here) fixed that issue for me:

Steps I have taken to correct:

Boot into BIOS Change the security settings to remove Secure boot change boot type (away from UEFI to BOTH) Set Legacy to first on the boot options.

However as soon as 1.3.0 is out if the issue you had was like mine it likely wouldn’t have been an issue. Also the instructions at the end of the install if using FOG in a Windows DHCP server environment are critical. The Fog team should be given a lot of credit for including those. It made my first install of FOG incredibly fast.

Is the tftp server correct?

Does the file undionly.kpxe exist in /tftpboot/?

Have you copied the contents of /tftpboot/* to /var/lib/tftp/?

Hi Tom,
Thanks for your help,
My setup is working now, i had changed the ports through which machines were booting.
Now it is working.

thanks and regards,
sushant j

I try to summarize what I’ve found in this new thread here.

@Wayne-Workman a bit late in the day but have just setup Fog Imaging server. Could get Realtek Nics to work. Your post solved the issue.

@Daniel-Miller

I am at this specific point with regards to attempting to download the cert.

@fry_p It could be a monitor, keyboard, mouse, patch cable, video cable, or power cable causing the issue too.

We had a computer “Spot” once that was just voodoo’d. It blue screen’d, I said OK. Image it. Fixed. A few weeks later, blue screen. I said, OK it’s a hardware issue. PC Replaced, boom fixed. A few weeks later, another blue screen. I said, OK, this is highly unusual, but I’ll image it. Fixed. And again, another blue screen.

After that last one, I went in with a replacement monitor, replacement VGA cables, replacement power cables for everything, replacement keyboard, mouse, surge protector, and replacement patch cable. The whole 9-yards. Everything but the physical desk and chair was replaced. And that fixed it. All the old crap I pulled from there was marked “bad” and surplussed, I didn’t even bother testing those items as they were old and low-cost.

@JGallo YEs, that is correct. rc-3 has the fix too and so it will remain going forward.