Surface Pro 4 Image Capture

[george1421]

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

[Psycholiquid]

@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

[Psycholiquid]

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

[Psycholiquid]

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

[Psycholiquid]

https://youtu.be/QBJLhO1zuJA

[Psycholiquid]

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.

[Psycholiquid]

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

[Tom Elliott]

@Psycholiquid My hope is that it will be unneeded in the future, though I don’t know when that will be.

The reason I’m not making it a checkbox is because it’s essentially going to be deprecated the moment 1.3.0 releases. Adding it is not difficult or out of scope but for the few cases where has_usb_nic is actually required I don’t think warrants such a large scale change. Especially considering that not ALL USB PXE Nic’s require the has_usb_nic setting.

[Psycholiquid]

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

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

[Tom Elliott]

@Psycholiquid Did you disable hibernate in the image?

Open CMD:

Run: powercfg -h off

[Psycholiquid]

@Tom-Elliott I did not, I’ll give that a try

[Psycholiquid]

@Tom-Elliott Nope no dice.

[Psycholiquid]

Gonna try turning off quickboot options. I am reading that can cause this issue.

[george1421]

@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

[Psycholiquid]

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.

[Tom Elliott]

@Psycholiquid Upload before hitting OOBE?

[Psycholiquid]

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

[Tom Elliott]

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

[Psycholiquid]

@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