@Dv27842 said in INQUIRY: Network:

I don’t see the file, I have tested it on my desktop and I do see it should I just transfer the file to the VM. Also,

This statement confuses me a bit. We are still talking about usb booting into ipxe right? The file is on the fog server in the /tftpboot directory. Its called ipxe.efi. If the /tftpboot directory is not there you can search for the file with sudo find / -name ipxe.efi But it should be in the /tftpboot directory.

You can get an older version from the github site too. But its best to get it from your fog server. https://github.com/FOGProject/fogproject/tree/master/packages/tftp

@Goneski Great you found a solution for your setup and sharing it here.

Looking through the config posted I am wondering that all the menuentry sections at the bottom of the file are commented (lines starting with #) and so I would expect for those to not be used?!

@george1421 Thanks for the response. I think I might’ve actually figured it out. If you Legacy PXE boot, it errors out on a UEFI based machine. However, if you use the Network Stack PXE boot (UEFI), it will correctly boot. The DVD does work for both UEFI and Legacy. I don’t know why I didn’t think to try that first.

Thanks for the help!

@george1421 Okay, thank you very much for your thourough response, I’m gonna think about it.

If the machine is already set to pxe boot, and wake on lan is operational, then yes.

@mpatel as others have mentioned here - speed is the key; we’re in an identical situation, all sites connect to HQ via VPN but then all sites have Gig Internet so imaging machines at the remote sites has never been an issue, you just talk the end user over the phone to his F12 and that’s that (FOG job must be submitted ahead of time of course).

Well you have a few things in you need to think about.

Moving netboot services to the FOG server. This is pretty easy enough to do. You change the dhcp options 66 and 67 to point to your FOG server from your current netboot server. I do have a tutorial on how to setup FOG as a netboot server here: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images This system uses FOG to create the custom iPXE menu entries to boot into your linix distro’s live installer environment. You may have to tweak the kernel parameters to load your installer seed file. The nfs disk structure and preseed file organization is up to you since netbooting is not a supported feature of FOG, but a hack using the FOG infrastructure for netbooting.

Once you have your netboot installer for linux configured then you can focus on the windows bits.

@Sebastian-Roth Sorted. Many thanks for your help!!

I’m sorry I haven’t answered for so long, but I’ve been busy a lot and haven’t been able to address this issue until now.

First i only got the login of the FOG local users to work with the solution provided by @Tom-Elliott.
I could login with usernames the contain spaces with the following changes:

user.class.php:
Line 214:
Change the relevant regex from:

(?=^.{3,40}$)^[\w][\w0-9]*[._-]?[\w0-9]*[._-]?[\w0-9]+$

to:

(?=^.{3,40}$)^[\w][\w0-9]*[ ._-]?[\w0-9]*[ ._-]?[\w0-9]+$

fog.user.js
Comment out:

//regex: /^[\w][\w0-9]*[._-]?[\w0-9]*[.]?[\w0-9]+$/

When i tried to login with a domain user that contains spaces (users without spaces worked already) i got the same problem, no error but no login.

Then i figured out that the LDAP plugin uses the same check and regex so i had to edit this too:

ldap.class.php
Comment out:

/** * Test the username for funky characters and return * immediately if found. */ // $test = preg_match( // '/(?=^.{3,40}$)^[\w][\w0-9]*[._-]?[\w0-9]*[.]?[\w0-9]+$/i', // $user // ); // if (!$test) { // return false; // }

Now it works like a charm. 😃

Thanks to all people that were involved in this.

This can be marked as solved.

@cammykool I would search for bonding and your linux distro. Bonding or teaming (depends on which method you use) is setup at the OS level. You will also need to get with your infrastructure folks to setup the switch the fog server’s plugged into for bonding. I would suggest LACP also called 802.1ad. Both the switch and the server needs to be configured for the same bonding type. When you setup bonding on the linux side, it will create a new network adapter typically called bond0. That virtual network adapter will then talk to its slave interfaces (the real physical nics). You will apply the IP address to the bonding nic and not the physical nics. The bonding driver will manage the physical interfaces once its setup. When you configure FOG you will tell it to use bond0 (or what ever the bonding interface name that is created). Once you have bonding setup and WORKING at the linux level then you can forget about it and install FOG. Don’t install FOG without or before bonding setup.

@tneuber The unattend.xml thing, is a windows thing and not a fog thing.

For example I don’t use the FOG client in my environment but I use the unattend.xml file to configure the target computer and connect it to AD. Here is an example of a sanitized version of my unattend.xml file: https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/7

@marted said in Remove press F12 for network boot (PXE):

No need to press F12 if I stop all computers and send a signal with the image wake-up on lan

Just be mindful that windows 10 doesn’t play nice all of the time with WOL. Many have reported that wol doesn’t work if the computer was in windows and is either put to sleep or shutdown from inside windows. WOL does work if the computer is unplugged and then pugged in, where windows wouldn’t leave its bits hanging around and breaking the wol process.

@jack_chapman2020 Error is: Logon failure: unknown username or bad password, code = 1326

Try DOMAIN\username and simply username - we have seen one or the other working. Though we have not found the time to figure out in which situation one works or the other.

@lordbob75 Good to hear you got this fixed! Though the error message for me didn’t point to be the IPs to be the issue. But well.

Would you be interested to get in touch with the person who created the Docker image to see if he/she’d be keen to update the FOG version?

Thanks!! I will take a look

@Sebastian-Roth
Yes on proxmox

@wreckignize The rest of the setup should be the same, just how it gets installed is different.

@execcr said in Fog and pxe boot Esxi 6.7u3 installer on HPE Server can't pass k.b00 module:

i just spin up a VM with UEFI bios and E1000E adapater and tried to deploy esxi 6.7u3 to that vm and get past the loading modules stage and i can actually install esxi here.

From what you have told us so far I think this might be some problem with iPXE booting in the other VM. Can you please give us more details on what setting(s) is/are different between the one that works and the one that doesn’t properly load.

@vic60400 Would be interesting to hear if (and how) you were able to exchange the certificates. Other users might find it very helpful.

@george1421
Thank you so much !
It works well !
Have a good day.