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

@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

@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.

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.

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

Trying a few different options such as single disk not re-sizable to see if that makes a difference

@Tom-Elliott Understood.

When I am uploading no matter how I do it, the image is coming back as uncleanly mounted.

I tried with and without sysrepping it. I did run Disk Scan before on both runs tand rebooted twice before trying to upload the image. Wondering if the partitioning auto fix is causing the issue:

@Psycholiquid said in Surface Pro 4 Image Capture:

@Psycholiquid said in Surface Pro 4 Image Capture:

has_usb_nic=1

ok so added has_usb_nic=1 to the host under kernel arguments and it is uploading now, I still get the usb 2-2-port2 error over and over, but the nic does come up. Ill post a video of here in a sec once the image completes.

I believe what I am seeing is the docking station nic that is throwing that error.

So what are the chances of getting a has USB nic added to the host screen as a check box? Right now I will just make a group and put the kernel arguments there and update the group as hosts are added, but with devices going this way it might not be a bad idea.

Let me know if that is a bit out of scope.

https://youtu.be/QBJLhO1zuJA

Add boom goes the dynamite, the image is hosed due to not cleanly unmounted… I hate windows sometimes.

@Psycholiquid said in Surface Pro 4 Image Capture:

has_usb_nic=1

ok so added has_usb_nic=1 to the host under kernel arguments and it is uploading now, I still get the usb 2-2-port2 error over and over, but the nic does come up. Ill post a video of here in a sec once the image completes.

@george1421 said in Surface Pro 4 Image Capture:

@Psycholiquid So now I’m a bit confused where exactly the issue is.

1. You have a usb network adapter attached to the docking station.
2. You can pxe boot into the FOG iPXE menu no issue
3. You can register the system OK (enter confusion)
4. When you boot to capture the image the FOS engine does not pick up an IP address?

It sounds like iPXE supports that NIC interface, but the FOS engine (linux) does not. There is a kernel parameter for usb booting, is that configured for this host?

No there is not, I have it on the registration which could be why it works there. Do I need to add teh dsame thing to the host itself?
mode=manreg has_usb_nic=1

Also the above errors you are seeing is because I pulled the cable (Dock to Surface) and plugged back in otehr wise I get the usb 2-2port2: Cannot Enable over and over.

It will do that for 5 errors and then post hit Enter to Continue

@george1421 I will give that a try and see what happens

It works on teh same exact machine.

So the scenario is this.

Surface with dock and USB to eth

Registers by booting with Dock and then switching to USB to eth (Does this due to init not seeing dock.

When I set to upload image it never sees the USB to eth nic for some reason. so it works for one but not the other.

Tue Jul 26, 2016 6:21 am
Running Version 1.3.0-RC-2
SVN Revision: 5937

Trying 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 said in Black Screen on Surface Pro 4:

@Wayne-Workman said in Black Screen on Surface Pro 4:

@Tom-Elliott said in Black Screen on Surface Pro 4:

@Psycholiquid I’ll but the 7156 efi files up on rc-3 so this shouldn’t be an issue anymore.

Perhaps even label them differently than just replacing all of them?

Could call the 7156 ipxe.efi file something like surfspro.efi or ipxe7156.efi ?

I want to keep the latest efi files, and these ones that work for the surface too.

If someone ( @Psycholiquid ) could post a complete packet capture of a DHCP conversation with a surface 4, I’ll see what I can do in the way of a vendor class for DHCP.

Man would love to if I knew how…

Unless you are talking about Wiresharking the packets between the surface and the fog server. If so I can give that a try today. I did back up the files before I uploaded the other ones.