Well, I found this:

http://devdocs.magento.com/guides/v2.0/install-gde/prereq/php-centos.html#instgde-prereq-php55-install-centos

Little manipulating and I got it to get me into FOG.

I’ll keep an eye on the server to make sure I’m not getting any failure logs, but it took.

Thanks, Wayne.

@ITSolutions That was it; I’m normally better at catching that, or leaving it set to AHCI (which most of our computers come in as) but it just never crossed my mind.

@Arrowhead-IT

I do not sysprep. (yet - I want to try it out) I have. Did not check that as @ITSolutions idea fixed it when I tried it.

@Omanimous Without knowing the exact details. A 128GB disk (ssd or hdd) from two different manufacturers are usually different sized down to the byte level. So in theory if your source disk is one byte larger than your destination disk a non-resize FOG image will fail.

I can say for my reference image (which I deploy to all hosts), I create on a VM with a 40GB hard drive. That way I’m assured it will deploy to all hardware on my campus. For win10 I use a 60GB reference image.

With FOG 1.2.0 I used non-resizable and then let windows expand the disk. With the 1.2.0 trunk build FOG expands the disk now. I still use a 40GB reference image for Win7. So I always go smaller to larger when the image is deployed.

@Omanimous said:

Changed Option 67 in DHCP to undionly.kkpxe and it seems to be working fine.

lol glad you got it working. I’m sure it will be fine.

In the future, when you have network booting issues, the boot file should always be your first thing to inspect and think about 🙂

Um, what about trying one of my kernels? I try to include as much as possible. I’m guessing you’re running 0.32? Just use the 32bit kernels and name them the normal bzImage. If they don’t work you should be able to switch back relatively easy.