I am still new to FOG, but I have my lab environment setup for it and have tested and successfully deployed just base windows 10 to both virtual and physical PCs. I am having issues when trying to deploy a new Windows 10 image to physical PCs. I think this might be a legacy/uefi issue, but I’m not entirely sure.
So, I have a SSD(UEFI) that has windows imaged onto it along with programs that are needed for production, when you boot from it on a PC it just prompts windows installer, etc, and once finished it has all the apps loaded onto it already. I put that into a spare laptop(Dell Latitude 5580) that has both legacy and UEFI, added the host to FOG, and captured the image with no issues. I then took out that SSD and put in the original HDD and tried deploying the image to this. During the install I got two messages(I would upload pics but it says error when trying to upload)

During deployment: Buffer I/O error on dev sda3, logical block <insert numbers here>, lost async page write
At the end of the deployment it said: a warning has been detected! Image failed to restore and exited with exit code 1(writeimage)

After this I try booting legacy and uefi via hdd and windows boot manager, however they both don’t work and ask for a windows installation media. I have not tried another physical PC as we do not have any more spares I can use at the moment.
Any help would be appreciated.

@sebastian-roth
Ping results showed it would drop completely once the PC froze. And by froze I mean it would completely freeze all of the sudden, not gradually. I ended up checked the RAM, and it turns out one of the sticks was bad so instead of a total of 16gb I had 12gb. I had my Fog server with 4gb of ram and the Windows VM 8gb, so no memory left for the actual PC running it all. Just lowered RAM on windows vm to 4gb and it’s all fine. I can now continue with my testing!!
Anyways, thanks for the reply, love seeing how helpful the FOG mods are!

I am running my FOG server off a physical PC and started capturing an image of a virtual windows 10 machine(1909) and after adding the host to the inventory and trying to capture it’s image, my whole PC will just freeze and I have to reboot it to get it back up. It always freezes right around the 50% mark of capturing the image. I’ve left it overnight and it didn’t finish to capture and was still frozen. This didn’t happen when I used a physical PC to capture an image as a test, only virtually.
The only idea I have is that the windows 10 virtual machine I made has been assigned 4 cpus vs the physical machine running it only having 1, so I wasn’t sure if this was an issue. This is on a wiregapped network so no internet access. Does anyone have any ideas?

@george1421 No worries, I was just curious! I think you’ve given me all the information I’ve needed. I appreciate your response time and assistance!:)

@george1421
Awesome thank you so much! I know you could just change the guid and sid after deploying the image but thought sysprep could just eliminate that need. I definitely didn’t think of using a VM for the golden image! I currently have it all setup on it’s own wire gapped network so no internet & not connected to AD.
I think what I will do is use a VM for our base windows10 image, however we have specific programs needed to be deployed on a mass basis that require internet at time of install, so I may just do that with a physical PC but sysprep it before.
Apologies, but can you elaborate on “If windows based use VLK media and keys.” I don’t quite understand that part.
What would happen if you cloned it after it had been connected to AD and what would the process look like to fix any issues arisen from that? What about if the domain changes to something different from what was on the image?

Hello there, I just spun up my first FOG server and am going to be creating some test images before actually using this in our production network. I was wondering If I need to be sysprepping the PC I will capture an image from before creating the image or after? Should I do both so I have either or in case? Thank you!