@stealthlegend Ok I will look into this further. But to your point, I do see how this can be beneficial for bulk imaging.

Thank you!

@Xinzo Just a quick note for your understanding. The links you posted in your initial topic post are both about changing the keyboard layout once the Linux kernel (FOS) loads. But entering username/password on a quick deploy is when iPXE is still loaded (before FOS).

I added keyboard layout setting to the latest dev-branch version of FOG just now. So please update to the latest version (1.5.9.174 or later) and make sure you have the set KEYMAP in FOG Configuration -> FOG Settings -> General Settings (e.g. to fr or de).

Be aware that iPXE only comes with simple localized keymap support. For example some special characters (e.g. §) and German Umlauts do not work. It’s not the full set of latin1 keymaps that the Linux kernel actually supports. But most special characters work and YZ are not swapped out like on the US layout. So I hope it’s still helping you when typing username and password on quick deploy.

I can’t properly test this on UEFI machines as I only have a VirtualBox test environment at hand and PXE booting doesn’t work here in UEFI mode. There were rumors about keymap being an issue on UEFI system in the iPXE forums. No idea if that is still the case.

Oops!

Turns out I can delete groups OK. I suspect what was going on is I’d had a long and stressful day and the password it was autofilling that I was mindlessly accepting was wrong. Today I manually typed the password of the FOG user and it worked.

Please excuse my noise!

@anwoke8204 said in Fog taking forever to boot to the network:

tftp 10.4.47.15 ipxe.efi c:\users\kstevens

Hopefully you just missed the action command when you posted the command.

The command should be
tftp 10.4.47.15 get ipxe.efi c:\users\kstevens and it should place the file ipxe.efi in the directory path you provided. It concerns me that the destination file name did not match the source name. The transfer should be very quick like about 2-3 seconds from the time you hit enter on that get command.

What are ping times to this fog server 10.4.47.15 from this same windows test computer?

What are ping time if you use this command ping -4 -l 1300 -n 4 10.4.47.15 This command says use ipv4 set the payload size to 1300 and ping 4 times to the host. I’m specifically using a payload size larger that the default ping size to see if we are hitting a mtu issue that wouldn’t be visible with a 64 byte ping size.

@lcis said in Attempting to check in...... failed:

I’m sorry for the inconvenience…

Not at all an issue. I just thought I let you know. You can’t count on things to be fixed in working-1.6 because no one is maintaining this branch as of now.

Thanks for testing the quick fix and reporting back. I will look into properly fixing this issue in the working-1.6 branch some time this week because I remember we had this issue mentioned in the forums a couple of times and now we know what’s causing it.

@ariederer26 said in How to move DB and images to different server:

Do I have to execute it as Ubuntu root user? Or myself the only user on the system?

In general any Linux/Ubuntu user is able to run mysqldump. But there is a chance you can run mysqldump and not have to provide DB credentials if Run as root.

@george1421 That’s what’s done it, the kernel version I’m using at this subsite is older than the one at the main server.

Main server has been brought up to date but for some reason, I never considered all 37 sites would also need to have bzimage/32 updating as well.

Well, that solves it. Even if it was my own stupidity haha! Thanks mate!

@user419 How did you turn on https protocol in FOG? It almost appears that ipxe did not get recompiled with the same certificate that apache is using for the web server.

@george1421 thank you very much for your help, I’ll try to edit the refind file.

@jshancock1 Is this a new install of FOG? It almost sounds like is not being sent to the target computer causing the unable to boot messages. While they are different messages they are about the same topic.

From the fog server linux comsole prompt what is the output of this command? file /var/www/html/fog/service/ipxe/bzImage

@ggiesen said in FOG Client with CA-issued TLS certificate:

The SnapIn client appears to be trying to talk to the web server using HTTP and on the IP address rather than the FQDN. Any way to fix this?

Unfortunately this is a known issue discussed on github: https://github.com/FOGProject/fogproject/issues/371

I worked around this temporarily by adding the following to /etc/httpd/conf.d/fog.conf:
…

Well done! Overall you’ve made quick progress on making this work!

@george1421 thanks for the answer 😄

@lcis said in Trying to access /images on deploy-debug:

For curiosity, why couldn’t I mount $storage ?

While debugging your post install script, use debugPause to put a break point in your code. Put an echo statement in just before the debugPause to say “Stop me here”. So when you are debug executing your deployment, when you get to “Stop me here” press ctrl-C to exit the fog script. Now run the set command and confirm where $storage is pointing to.

Also side note, I always set $variable using ${variable} so the bash interpeter really knows what I want as a variable.

When you hit the ctrl-c that should be the exact state of the machine. The /images directory on the FOS target computer should already be mapped to the FOG server /images directory at this point (during the execution of the postinstallscript)

Hi,

Same problem as Scoude here with Fog 1.5.9 on Debian 10.
I “defraged” (it’s a ssd), desactivated Fastboot, hibernate off, chkdsk…
Nothing fixed the problem.

Any idea ?

Thanks

@londonfog I can most assuredly tell you that no one using FOG has done this before.

The challenge is getting both iPXE and the FOS Linux kernel to use the serial console port (even at that I don’t know if the SOL redirect will work correctly).

The first step is that you will need to rebuild iPXE using the built in tools in the fog server. https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe I would run through this process the first time as is just to get a base line compile setup.

Then you will want to hack a config file to enable the serial console in iPXE as outlined here: https://ipxe.org/console

As an example here is the fog supplied console.h file https://github.com/FOGProject/fogproject/blob/171d63724131c396029992730660497d48410842/src/ipxe/src/config/console.h#L37 note that you will need to turn on the serial console in the console.h in the build path for iPXE. You will need to do it for both the bios and uefi config files.

You will probably want to add the following lines right under enabling the serial console.

#define COMCONSOLE COM2 #define COMSPEED 9600 #define COMDATA 8 #define COMPARITY 0 #define COMSTOP 1

You will need to make the changes correctly for your SOL configuration.

Then rebuild iPXE a second time. This time move the built files to the /tftpboot directory.

Now for bzImage (fos linux kernel), it looks like you just need to add this to the global kernel args settings console=ttyS2,9600

@ram There are so many questions because your post lacks details.

Is this a new FOG install? What did you configure in your main dhcp server for options 66 and 67? Is your pxe booting client a bios or uefi computer? If you select the boot manager on the target computer (typ F10 or F12) can you select pxe boot? If yes what error message do you get?

@baptistepds Well then we do find that sometimes there is no hope because of a hardware conflict between ipxe and the firmware. We do have one last method to boot bzImage directly fro a usb flash drive. You will lose multicasting and “Deploy image” functions because iPXE isn’t there, but you will still be able to unicast an image onto this computer.

Read through the tutorial completely so you understand the caveats and also look at the forum chat for some additional hints: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image

@george1421
Hey I did a sysprep.
I had to to reboot one time and shutdown one more time. And it works.

Thanks

@rocksoft said in Can fogproject be used to deploy bios/uefi servers like a deployment server ?:

Can fogproject be used to deploy bios/uefi servers like a deployment server ?

The quick answer is yes.

FOG supports both bios and uefi based computers. You need to send a bios based boot loader (undionly.kpxe) to a bios target computer, and snp.efi or ipxe.efi to a uefi based computer.

So if you have your own dhcp server that supports dynamic boot loaders (like a linux dhcp server) you can configure those settings. https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Example_1 or if you have an external dhcp server on a router or L3 switch you can use dnsmasq to provide dynamic dhcp boot loader info https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

And finally if you have no dhcp server, when you install FOG you can tell FOG to install a preconfigured dhcp server to provide dynamic pxe boot info.