@drewski Good job!! Yes the FOSL usb can be removed once the FOS engine starts. The usb is only the delivery system for the FOS engine. FOS runs out of memory once loaded.

@george1421 said in Dell Inspiron mini 1012 ipxe initialising devices problems:

For FOG 1.3.0 and bios based computers you should use undionly.kpxe

undionly.kkpxe actually works more often, with more systems than undionly.kpxe

Further, any system compatible with undionly.kpxe is also compatible with undionly.kkpxe so we have been recommending the .kkpxe version. This is also the file used for BIOS systems in FOG’s ISC-DHCP setup because it is more compatible.

@george1421 said in Fog .032 and HP8000 elite:

you are on 1.3.0-rc1we should not be talking about pxe.krn at all. For bios you should have undionly.kpxe or undionly.kkpxe and for uefi systems ipxe.efi.

+1,000

That’s what I was thinking since it was first mentioned.

@Psycholiquid Understand that I don’t know the Surface Pro, but it was my understanding that you could use MDT to build your reference image with all of the Surface toys built in. https://blogs.technet.microsoft.com/askcore/2014/07/15/deploy-windows-to-surface-pro-3-using-microsoft-deployment-toolkit/ (Yes I know this says surface 3, it was the first one I hit on in my google-fu search)

@Nicolas-Bricet

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@Tim-Trageser

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@nicked

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@SusejNatas Go ahead and update again. RC-4 is out.

Any other scripts I an run or ideas to get some usable info towards troubleshooting?

Thanks Guys got it up and running needed to turn on the boot stack in the bios.

Just so others know/ so you know. There are two different Domain password spots. One for if you have the new client installed and one for legacy clients. It had my password in the new one’s spot where the client on my machines is the old client. Used FOGCrypt to generate the Legacy password again and it worked like a champ.

@Tom-Elliott, thanks. I believe we can close this thread. Things are working now as far as a Capture/Deploy aspect goes. I’m having issues with my images not joining the domain. I have done some reading here and all of my settings appear to be correct. If I can’t get it working, I can start another thread.

Thanks for all of the help. There is no way that I would have got this working without you guys. Thanks.

@Tom-Elliott Tried the ipxe.pxe settings and it’s working, gonna try on some of my other models.
Thank you!

@Boyan-Biandov FWIF if you used the kernels from my link they are 4.6.2. But either way I’m glad you got past this issue. Happy FOGing…

I working!!! Thank you so much.

I’m fairly sure the Surface Pro can only UEFI boot, so you need to make an UEFI image

@Jerry29445 Any news on this?

@jphillip5 Ok the dumb switch resolved (masked) your issue.

Your building switch, is it an advanced switch like the Catalyst series?

Do you have fast STP, port fast, or RSTP enabled on the ports that go to these HP targets?

Do you have green ethernet or 802.1az enabled on these switches? (if so turn it off).

@csurepair You should really start your own thread because the conditions could be different.

Things that we would need to know is the version of FOG you have installed (on or about the cloud on the management home page).

What is your dhcp server?

Is the HP in uefi or bios (legacy) mode?

Since you are getting to the download of bzImage, it probably safe to assume you have the correct iPXE kernel loaded into dhcp option 67.

Are you using dnsmasq in your environment?

you guys can mark this as solved I posted how I resolved this issue above