Hi.
I’ve also had problems doing “deploy” image to a Microsoft Surface Pro 4 however I accidentally stumbled upon a workaround of connecting two (2) network interfaces to the Surface Pro 4 as a solution. I connect the Surface Pro 4 to the “Dock” (part # PF3-00005) which is connected to our Ethernet LAN and I also plug a Surface Ethernet Network adapter (part # EJS-00002) into the Surface’s USB3 port. Yes, I know it is silly to connect two Ethernet interfaces to the surface however for whatever reason this allows the “Deploy” to work successfully.
HERE’S DETAILS ABOUT OUR ENVIRONMENT
FOG server version: 1.4.4 (note on 4/3/2018 I see that “Latest stable version is 1.5.0”)
I used the 'Windows 2012 R2" steps at https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy to configure our DHCP option “067 Bootfile Name” to ipxe7156.efi (not ipxe.efi)
After I unbox a new Surface Pro 4 I do the following …
-
Manually add a “hosts” record for the new Surface Pro 4 to FOG
a. Open the box with the “Dock” and write down the Dock’s Ethernet MAC address (which is in very tiny light print)
b. From FOG’s “Hosts” menu click “Create New Host”
c. Fill in the following form options:
i. “Host Name” = “pc_surface03” (or something suitable)
ii. “Primary MAC” = whatever is written on the “Dock” (we assign one dock specifically to each surface because the DOC’s Ethernet MAC address is the key field for FOG host identification)
iii. “Host Image” = select UEFI image form the list
iv. “Host Kernel Arguments” = “has_usb_nic = 1”
v. Scroll down and under the “Active Directory” section check the box for “Join domain after image task”
vi. Scroll down to the bottom and click the “Add” button -
Plug the Dock’s power brick into a wall outlet
-
Connect the Dock’s power brick to the dock
-
Connect an Ethernet cable to the Dock’s Ethernet port
-
Connect the Dock to the Surface Pro 4
-
Plug a Surface Ethernet Network adapter (part # EJS-00002) into the Surface’s USB3 port
-
Connect the Surface Ethernet Network adapter (part # EJS-00002) to our LAN
-
Now we PXE boot the Surface Pro 4 for the first time with the following steps:
a. Hold in [volume-up] and tap the power button
b. When “Surface” appears on the screen release [volume-up]
c. Touch “Security” on the left
d. In the “Secure Boot” touch “Change Configuration” button
e. Touch “None” and then touch the “OK” button
f. Touch “Boot Configuration” on the left
g. Change “Enable IPv6 for PXE Network boot option” option to “Off”
h. Drag the “PXE Network” item to the left
i. When it asks “Boot this device immediately” touch “OK” button
j. When the FOG menu appears you will see the heading “Host is registered as lap_surface03” (or whatever name you manually registered it as) -
Now we deploy our image
a. Choose “Deploy Image”
b. Login to FOG
c. Select the OOBE image you want to deploy
d. Wait 2 minutes for the image to be deployed
e. Even though the image was deployed successfully the deployment “task” remains running forever on the FOG server, so in your web browser (on another PC) navigate to FOG’s “Task Management” page, check the box next to the deployment task that has finished and click the “Cancel selected tasks?” button
I hope the above information is useful to someone else.