Surface 4 Network boot and Image

[Tom Elliott]

@Psycholiquid Is it okay to solve this thread, now that we CAN network boot and you CAN image this system?

[Psycholiquid]

yeah I would say so.

[Psycholiquid]

OK imaging did image to the device, however, it does need the EFI parttion or it will not boot into the Surface so far as I can tell.

I have tried changing the host EFI Exit type to all different options no change. I will try and see if I can somehow put the partition on there , but I am thinking there will be two different images since the one I made with sysprep and this use two different types of boot partitions.

But to nail the point down the UEFI is on the device not the HDD.

[Wayne Workman]

@Psycholiquid What image type are you using? Please try single disk non resizable and multiple disk non resizable before you give up.

[Psycholiquid]

@Wayne-Workman I am using that now, it isn’t the image it is the device, so when it boot to the drive it needs the EFI partition in order for the device to continue. I am attempting to insert the files into the system partition on the existing image to see if it will pick those up.

[Wayne Workman]

@Psycholiquid Where is the EFI partition and why is FOG not taking a copy of it?

[Psycholiquid]

@Wayne-Workman I think I am not explaining it right, from the surface upload I am getting everything I need. I was able to restore it back to factory orig with eh captured image.

My custom image doesn’t have a EFI partition due to it being loaded form ISO. So in normal Windows install there is the System partition that has stuff in there to allow for the machine to boot. I will be pushing the EFI files to there to see if I can make a hybrid solution.

[Wayne Workman]

@Psycholiquid Oh, ok. I think I might suggest trying to capture your image using different OS types - specifically Linux. See if that works.