Surface Pro 3 PXE:
-
[quote=“MRCUR, post: 40217, member: 25116”]I know this is an older thread, but I just got a few Surface Pro 3’s that I’d like to image through Fog. I installed the latest SVN build of Fog onto Ubuntu 13.10 this morning. I have the DHCP server set to ipxe.efi.
After disabling secure boot on a Surface, I was able to get it to the iPXE menu. Entered the server’s IP when prompted and after about 20 seconds received a timeout message.
Any ideas Tom?[/quote]
I’d like to know if there are any solutions for this as well? I don’t get any sort of connection. We may be implementing this as a standard tablet and it would be a bummer if I can’t create and deploy an image to them. I will add, I am only on version 1.2.1, because of the XP deployment bug (something to do with PartClone?) that a few of us encountered (yes , we still deploy XP to older systems).
-
I get the same result when using ipxe.efi where the tftp boot server is asking for an IP address. I tried the ip address and the full path, e.g. [url]http://192.168.0.1/ipxe.efi[/url] and it just times out When I tried snp.efi and got to the menu, but it just resets back to the menu when I try to inventory.
-
[quote=“Chris Sodey, post: 40510, member: 1418”]I get the same result when using ipxe.efi where the tftp boot server is asking for an IP address. I tried the ip address and the full path, e.g. [url]http://192.168.0.1/ipxe.efi[/url] and it just times out When I tried snp.efi and got to the menu, but it just resets back to the menu when I try to inventory.[/quote]
Good to know you’re having the same issues I am. Sounds like something with ipxe, perhaps someone from the Fog dev team can chime in.
-
I would chime in, but i don’t know all the specifics.
I know things work, but I don’t have any system or test bed to try replicating (which helps me figure out a fix as well) the problem.
-
I am using a stand alone FOG server v. 1.2.0 running on Ubuntu 12.04 server x64. DHCP is handled by ubuntu. I am trying to image a Microsoft Surface Pro 3 with the Microsoft USB3 gigabit network adapter. When I have the boot file set to ipxe.efi tftp asks me to enter in an IP address. Everything else I have used FOG for iPXE just flows to the fog menu, it never stops. When I type in the IP address of the TFTP Server (also DHCP server) it searches for [url]http://192.168.0.1/default.kpxe[/url] and when it doesn’t find it, times out. I tried to enter in the full path of [url]http://192.168.0.1/ipxe.efi[/url] and it also times out like it can’t find ipxe.efi or doesn’t know what to do with it.
Thanks Tom.
-
you shouldn’t be looking for default.kpxe, but default.ipxe.
Beyond that, entering the direct path will make tftp look for ([url]http://192.168.0.1/ipxe.efi/ipxe.efi[/url]) which of course doesn’t exist.
-
I just tested again and Tom you are right about the typo, it is looking for default.ipxe
-
[quote=“Chris Sodey, post: 40515, member: 1418”]I just tested again and Tom you are right about the typo, it is looking for default.ipxe[/quote]
Did you have any success Chris?
-
MRCUR,
I ended up building a MDT and WDS server to get the Surface’s deployed. -
Hey,
If you all are daring and able, i may have a means to get FOG working for these.
It may require a few things, but if you guys have the equipment, I may have a potential solution. I don’t know if it WILL work, but it’s better than anything we have right now right?
-
Tom,
I am willing and able. I have 50 Surface Pro 3’s that still need to be imaged and I am not a fan of the Microsoft solution. What ever it takes to help the FOG team I am here to help.
Thanks! -
Are you aware of proxy dhcp, and how to install it and the ltsp.conf file on your FOG OS?
-
Proxy dhcp I am aware of, but never used. ltsp.conf I have never used.
-
I run Ubuntu 12.04 and the newest FOG patched with the latest SVN to get the work around for the Yogas to work.
-
While the title doesn’t mean much, it’s still useful.
The ltsp is used to “prxy” the dhcp server for boot up requests.
We’ll be making all modifications after this point in that file. Though I need to find out what specifically, so I’ll be testing vicariously through you Chris.
-
I am using FOG in a Windows Environment where I set options 66 and 67 on our DHCP server running on Windows Server 2008 R2.
-
That’s fine.
If you setup dnsmasq, you can leave those values there, or remove them, and all should still work. Albeit with some minor gotchas.
-
Ok, since my FOG is a VM on vmware I can take a snapshot and always roll back in case we break anything
-
Exactly.
-
I have not been able to get the above solution to work on 1.2.0 with the new Surface Pro 3 Dock. I ordered a usb gigabit adapter today, hope to see different results.
