@george1421 @Avaryan If I am not mistaken, you should try the ipxe7156.efi until we have this figured out right? Newer ones don’t work with the surface.
EDIT: If you have a mixed environment, I’d recommend looking at this page UEFI and BIOS Co-Existence in FOG
@avaryan From what I understand, it will only pxe boot from a microsoft dongle.
From the Website
https://docs.microsoft.com/en-us/surface/ethernet-adapters-and-surface-device-deployment
“Third-party Ethernet adapters are also supported for network deployment, although they do not support PXE boot. To use a third-party Ethernet adapter, you must load the drivers into the deployment boot image and you must launch that boot image from a separate storage device, such as a USB stick”
@Tom-Elliott Please disregard. The association was not stripped on all of them and I think for the affected ones, I may have deleted the associated image and replaced it with a newer version a while back. My bad.
Just wanted to give a heads up that all of my hosts’ default image settings were stripped after the RC1 Working update. Not sure that it is recoverable. They all now say “Select Image”.
@Sebastian-Roth I should have just put “OK” instead. With just the Surface Pro Ethernet adapter, I always get a USB error past the pxe boot, when it is preparing to image. I can use a powered USB hub to get it to work in those situations. You can change those to avoid confusion, but they pxe booted fine up until the commit you specified. If I can get my hands on another in the near future, I’ll get those svn versions as well.
@Avaryan , you can see that my Surfaces keep getting deployed to users before I can finish testing! They are certainly in high demand around where I work. You are right about that
@Tom-Elliott I love the new theme. I have seen the interface through all of the stages of development, from the 0.29 (grey fog as I called it) days to now. I think the new look is clean, sleek, and professional. Plus there are probably a number of things I can’t see directly that are improved on the backend. Well done!
@Tom-Elliott No worries! I was just making sure I didn’t do anything to mess it up. No harm done, just got a mild teasing from my boss! ;D
@Tom-Elliott Re-installed Working FOG 1.5.0 RC1 branch. Seems to have restored the proper host name. Is it something I did? Or is it a bug in the Dev-branch?
Ok, I’m starting to think its MYSQL since any PC I netboot comes up as the same host! All of them, no matter where, show as “BOU33”. Help!
Hi everyone,
I just updated to 1.5 RC1 and I love the way it looks now! However, I noticed a couple of bugs/issues. First off, when I pxe boot , instead of going to a FOG menu, it automatically starts deploying one particular image. I can’t pick the image or go to the menu. It deploys my Optiplex 5040 base image no matter what. It is also ignoring my queue size limit. I’m in a pinch so I’m making this brief, but let me know if you need more info.
@Sebastian-Roth I got my hands on a Pro 4 and tested all 76 of the .efi files you had up in drive. I made notes. Let me know if you need more info. It seems to have worked up until the 5/4/17 commit.
EDIT: They took my surface away for a user before I was able to test the svn folder on the Google Drive folder you shared @Sebastian-Roth 
@fry_p said in Microsoft Surface Pro 4:
@Sebastian-Roth Sorry for the delay, I will hit this on Monday. We’ve been re-wiring Chromebook carts the past few weeks and I’ve been absent from FOG dealings and checking the forums. I will try to find a spare Pro 4 to fiddle with
Hi there, I came back that Monday and had to give away my last Pro 4 to a user. So I guess I’m out for testing this, my apologies. We aren’t planning on purchasing any more in the near future as they are not durable enough for our “rough” users. Sorry everyone
@Sebastian-Roth Sorry for the delay, I will hit this on Monday. We’ve been re-wiring Chromebook carts the past few weeks and I’ve been absent from FOG dealings and checking the forums. I will try to find a spare Pro 4 to fiddle with
@Quazz I just tried both arguments on a surface pro 4. As long as you put
usbcore.old_scheme_first=1
before
has_usb_nic=1
separated by a space like you said, it works with no errors.
“Renaming a Windows computer and then joining a domain is now 2 times faster
Renaming a Windows computer inside a domain is now 3 times faster”
What black magic is this? 
@dylan123 As stated earlier, I got an instant “Failed to get IP via DHCP” error when I had just the dongle plugged directly in. I also am already using the “has_usb_nic=1” argument. Lastly. I have both the dongle MAC and the USB hub MAC listed in the host.
@dylan123 Brilliant suggestion, I didn’t think of that. Unfortunately, with the dock disconnected, we have the same result. I have also tried using the nic on the dock. I have tried a powered usb hub as well. I get the “Failed to get an IP via DHCP” message immediately if I have the usb nic directly connected. In the hub, it waits 35 seconds before the message pops up.
EDIT: I think I figured it out. I failed to realize that my powered USB hub has its own nic. I gather that it is switching the interface to that once it gets to the screen I am having trouble with. My first test, I let it pxe boot and when it got to the “Sleeping for 5 seconds” part, I quickly swapped the ethernet from the microsoft dongle to the USB hub port. It imaged perfectly. My second test is to hook up network to both the USB hub and the dongle going into the USB hub, and I had no trouble. I guess it is “switching” from the microsoft dongle MAC to the USB hub MAC when it hits this stage. I will try to get a powered usb hub (tried non powered to no avail) sans the nic. I am just curious why the stupid dongle by itself can’t pull an ip at that stage.
@Tom-Elliott I followed the exact steps in the highlighted in the solution post on this thread to no avail: https://forums.fogproject.org/topic/9704/surface-3-unable-to-obtain-dhcp/22
It almost appears that it is looking at the wrong interface. Is there a way to specify the interface in fog? It is looking at USB0 but when I unplug the dongle, it states USB2-port1 is the one being pulled.
EDIT: Just noticed i triple posted, sorry. I am just eager to get this working. It is the superintendent’s surface that needs an image, go figure.
@Tom-Elliott Just got to 1.4.0 RC4, still no luck. I tested the USB nic on an already imaged surface for plain connectivity and it worked for that. I tried to image a Pro 3 with the dongle and the same issue. Please let me know what info you need from me.