SOLVED Surface Pro 4 Image Capture
-
Tue Jul 26, 2016 6:21 am
Running Version 1.3.0-RC-2
SVN Revision: 5937Trying to capture the image from a Surface pro 4. When I get to the iPXE boot it will boot just fine, once it passes that and gets the init files. It will not see the network anymore.
I have the Surface setup with the doc and a USB to Network Dongle (Approved one that works with registration) I get the following errors once it gets into FOG:
-
@Psycholiquid Understand that I don’t know the Surface Pro, but it was my understanding that you could use MDT to build your reference image with all of the Surface toys built in. https://blogs.technet.microsoft.com/askcore/2014/07/15/deploy-windows-to-surface-pro-3-using-microsoft-deployment-toolkit/ (Yes I know this says surface 3, it was the first one I hit on in my google-fu search)
-
The surface image is a bit different than the normal PC image with the pen and the recovery partition and such., If I just use the LTSB it will not have all the bells and whistles people want from owning a Surface.
-
@Psycholiquid Just as a question, why are you not using something like MDT to build your reference image in a VM, capture and then deploy to your surface systems? This way you don’t have to manage audit mode at all and sysprep will work as it should.
-
Just an update, reinstalled fresh copy of Windows 10 for Surface and it uploads jsut fine it has something to do with the audit mode, as soon as I put it in audit mode it marks that partition as dirty. As to why I am not sure but that is what is happening.
-
@Wayne-Workman Yeah I always run CMD as elevated. It didnt help. It is the EFI boot partition that is giving the error. I am trying a clean install this morning without sysprep to see if it will upload. Then I will work up from there to see where the disconnect is happening. This is kinda weird on partclone’s part. I can see why they check but like George said in another post there should be a way to ignore it since windows 10 will have this alot.
-
@Tom-Elliott said in Surface Pro 4 Image Capture:
@Psycholiquid Did you disable hibernate in the image?
Open CMD:
Run:
powercfg -h offThe command should be run in an elevated command prompt, and is
powercfg.exe /H offso please try that, reboot twice, and then try to upload. -
@george1421 Yeah I would say it is technically working, the issue I am having with with the PC not the capture process.
-
@Psycholiquid as far as this thread is concerned, is the issue of not able to capture the image solved? I know what you are capturing is not working but at this time you can capture.
-
Yeah, but for some reason it is making the partition dirty, cant figure out why though. It did this to me before and I was finally able to get past it after a few reboots and disk checks, but this time it isnt working. Gonna work at it some and report back
-
@Psycholiquid That’s where I was lost. That’s how you’re supposed to do it.
-
@Tom-Elliott Nope, I have it in audit mode, then I run my script (Unattend.xml) and once it goes down and comes back to the “BIOS” I push it into network boot to capture the image
This way when a computer comes up form being imaged it thinks it is the first time it boot. Like all the major OEMs do it
-
@Psycholiquid I don’t know what you mean by “upload before hitting OOBE?”
You’re sysprepping the system, letting it boot a little bit first, THEN uploading the image?
-
@Tom-Elliott yeah I am wondering if it has something to do with audit mode. I have seen it do this before. Not completely sure why.
-
@Psycholiquid Upload before hitting OOBE?
-
ok tried teh powercfg -f off and turning off the quick boot options. Made sure the hibernation file was gone also. No dice, gonna try and upload it before hitting OOBE and see what happens.
-
@Psycholiquid what target OS? If you use the shutdown switch when sysprep it should cleanly close the disk. The other fix would be to sysprep then reboot into a pxe boot. On win10 shutdown is more like enhanced sleep than a power off
-
Gonna try turning off quickboot options. I am reading that can cause this issue.
-
@Tom-Elliott Nope no dice.
-
@Tom-Elliott I did not, I’ll give that a try
