Solved. OMG it’s so good to have another set of eyes on. Talk about not seeing the tree for the forest! I am watching first clone progress. This is far further than I was ever able to get with Symantec ghost - never could build their PXE client. Thank you so much Sebastian.

I have 15 identical systems. All have the same size 120GB SSD drives and only one partition. All have the same W10 build. I have imaged roughly half of them, and the size of the image is always under 20GB. One of the systems is imaging at 119GB. I am doing the same steps each time. Don’t know what’s wrong with this one station!

I have tried to upload a picture and I get “sharp” errors.

Hiyall,

I have 15 machines - same model, SSD brand etc.- which I have started imaging. Drives are all 120GB, and halfway through there is one host that is imaging 119GB - the rest are all 20GB. I can find nothing abnormal with this system, but am unsure what to look for that would explain this. Have retried the capture and same result - just this system.

Solved. OMG it’s so good to have another set of eyes on. Talk about not seeing the tree for the forest! I am watching first clone progress. This is far further than I was ever able to get with Symantec ghost - never could build their PXE client. Thank you so much Sebastian.

Many years have passed since I last attempted a FOG server, and I am not much more experienced on Linux than before. I have made progress, but now I am at an impasse.

I am running FOG 1.5.7 on a Ubuntu 16.04 VM. The IP is accessible to my Lan.

My router is a Unifi USG3 running the latest firmware. DHCP options 66, 67 appear to be working as required:

As I have seen on many forum posts the PXE error “file not found” seems to be the bane of many FOG users, and it certainly has brought my efforts to a halt.

I have also tried going with a bootable USB drive, which doesn’t boot the PXE client.

Unsure what I should next try, but it seems many users resort to dnsmasq as a solution. Any insight or help would be very much appreciated.