Black Screen on Surface Pro 4

[Wayne Workman]

@fry_p We might have a winner!

Try this class, add it into ISC-DCHP config file and then restart dhcp. Be aware of putting it into the right subnet and not messing up the closing brackets for that subnet.

class "SURFACE-Pro-4" {
    match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00007:UNDI:003016";
    filename "ipxe7156.efi";
}

Notice the filename I specified. This is the file that works with the Microsoft Surface series, and is available in FOG 1.3.0 RC-3 by default.

Also, notice all that stuff in the vendor class identifier… it’s a lot. That exact identifier is probably specific to that EXACT model of surface pro 4. Meaning this probably wouldn’t work for a surface pro made 6 months from now, or 6 months before because the manufacturers change that last part all the time, for every little change they make. I think that’s how they determine what image to put on it at the factory.

If this works, I think we can make a Windows Server 2012+ equivalent as well.

I guess now, I have to ask every surface person on the forums to do a packet capture. They are like Pokemon, gotta catch em all.

That said, can you provide a sub-model number? Anything on the back of the device in tiny print? Not looking for a serial, but a sub-model.

[george1421]

@Wayne-Workman Do you know if wild cards are supported for the class matching? If so then something like “SURFACE*” would match all when the surface 5’s come out.

[Wayne Workman]

@george1421 I set the class name “surface-pro”. The matching string is how the surface 4 identified. You can name classes whatever you want, so long as it makes sense.

In that last packet capture, look at dhcp discover option 60.

[fry_p]

@Wayne-Workman I use Server 2012 as my DHCP server, so how would I incorporate this into that (no idea what or where the ISC-DHCP config file is)? Should I follow the wiki instructions? Pardon my ignorance on the subject. Also, tomorrow I can get you the sub-model, but are we talking the surface, or the dongle?

[Wayne Workman]

@fry_p I’ll give you some steps in a bit, I’m dealing with an issue right now.

[fry_p]

@Wayne-Workman No rush, I’m out of the office today.

[fry_p]

@Wayne-Workman I’m back in the office and the Surface’s are not deployed, so i can test a bit longer. The sub-model is Surface Pro 4 1724 (I think that is the sub model at least. I did some reading up on that ISC-DHCP and realized I don’t utilize this. I currently do not have a test network environment, so I can’t really set one up quickly. At your leisure, can you tell me if I can skip that and go directly to the Server 2012 configuration?

[fry_p]

@Wayne-Workman I figured it out! I’m actually kinda proud of this one. Please see below for all of my Windows Server 2012 configs

Please let me know if you need anything else for this. It did indeed work. Thank you so much!

[Wayne Workman]

@fry_p Excellent job. What you posted is exactly what I would have had you do.

Just keep in mind that this is only likely to work with the exact sub-model, the one you said: Surface Pro 4 1724

For future readers, all that’s needed to make a vendor class for other sub models is a packet capture posted here on the forums, or analyzed by yourself. Simply look at the device’s DHCP Discover packet, inside option 60 you’ll find the vendor class identifier.