I have the same issue on the Realtek 8168. But this is all under hyper-v. On my old pc, with intel NIC, everything worked fine, but now on my new PC with the Realtek 8168 I am running FOG as a virtual machine and a PXE client on. All on hyper-v. It looks like hyper-v inherits the properties of the host system, even with private networks. When using EFI it all works, just not on a legacy NIC.

[quote=“PaganLinuxGeek, post: 42774, member: 2226”]Already considered that. It’s not an option on this device. :-/ I have a raspberry PI running on the home lan that could handle dhcp as it’s always on.[/quote] Install FOG with DHCP anyways, then disconnect from that modem/router thing. Use a cross over cable to connect directly to the target machine.

@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

@FlowLive Hey that’s great to hear that someone can repeat my madness… :sweat: @Wayne-Workman Le me see if I can clean it up a bit. I need to see if I can integrate what @Sebastian-Roth noted in this thread about using a logical to represent the fog server IP. I think I can make it work.

I agree with you that it works wonderfully well with postdownloadscripts, Thanks to the scripts provided by the forum community. Thanks to them. But we must look for a bit before we find the existence of this functionality. Many people will turn to OPSI because it is better indicated in the documentation and it is native in the application. http://www.opsi.org/en I always love Fog because it’s very light. Thanks to the Fog team

@Psycholiquid Oh, ok. I think I might suggest trying to capture your image using different OS types - specifically Linux. See if that works.

Hi everyone Does anyone tried to boot hirens boot cd from network

@vkenny The second element. (Single data store/server, 5 different nodes pointing essentially at the exact same spot.)

@pijltje Hmm I don’t see that directory I am using Ubuntu (I know I know, first time fog when I have time I WILL switch been a pain honestly)

I’m happy to test any of the kernels for the Dell 755/760/780 and provide feedback.

It looks like we have resolved this issue by installing Ubuntu 14.04 on both our FOG server and image server and then installing the GlusterFS as per Tom’s advice. Thank you Tom for all of your help.

@Tom-Elliott Okay, I’ll look into all this. Just happy to be able to get PXE to work! Again, thanks.

@x23piracy Missing since RC10 - see here: https://github.com/FOGProject/fogproject/tree/1.5.0-RC-10/packages/tftp @Tom-Elliott We should definitely put up a big note for the final 1.5 release.

@Wayne-Workman Thank you so much!

@aruhuno said: Following a discussion with @Sebastian-Roth, we finally found it! The problem is the speed negotiation with the switch . I’ll update the firmware of the switches and make feedback. #wiki

George helped me figure out what I was doing wrong. But what you posted Tom is very valuable.

@tom-elliott Oh la la!! works very verry fine :)

@george1421 I didn’t know this was a multi-master setup, if that’s what you meant. I was referring to a video on just configuring a second node into an existing fog setup. With the new access control plugin and site plugin, multi-master setups are just that less a good idea. As it stands now with the access control plugin, location plugin, and site plugin - the only benifit one stands to gain in a multi-master setup is some level of fault tolerance against the upstream box failing - and fault tolerance against the link failing - and for those two things you loose a comprehensive database/control center in a central location - a major drawback.

@themcv said in Image upload & deploy taking a long time: @brad-schumann Try this, I ran into this on Surface’s. Open command prompt as admin. manage-bde -off C: manage-bde -status C: Fingers crossed that it will fix it. In my case, Windows was by default encrypting the free space which caused issues. Tagging this for the #wiki