@george1421 said in Which pxe file to use:

There is one other class of iPXE boot loaders, these are ipxe.kpxe and ipxe.efi.

From my memory it is mainly ipxe.pxe. But anyhow, your explanation is wonderful! May we borrow this text to update the docs?

Up until just a few years ago the SNP driver was very immature. […] But now the SNP driver in modern hardware is very good and stable, so the SNP boot loader is now recommended unless you have a UEFI computer older than about 5 years then ipxe.efi should be used.

@george1421 Good point! Should be update the default dhcpd.conf generated by the FOG installer as well?

@Flyer There is some more information on the difference between .pxe, .kpxe and .kkpxe in a dated wiki article (linking to an even more dated reference). We are in the process of updating the docs. Thanks for pointing this out.

@Flyer said in Dual boot (2 disks) unable to boot grub:

Any idea as to the best way to get that where it needs to be

While you figured out why this failed on that particular machine I might still add that the FOS kernel is lacking module load support. All the needed modules are being compiled into the kernel binary.

@pjv The replication service also uses HTTP/HTTPS. So I would add 80/443 to the list.

@brakcounty said in ipxe boot slow after changing to HTTPS:

Even when using the Paravirtualized Network Adapter in VBox?

Learning something new every day! Wow, didn’t know this and never tried it before. Thanks!!!

@AlexPDX said in Windows Keys Management Plugin:

Is there a way to “Link bidirectionally” the information in the Host and Windows Keys Management Plugin ?
Im interested to make a link between :
Windows Key Plugin <->Host

I am not sure this is what this plugin was intended to be used for. From the plugin description: “Windows keys is a plugin that associates product keys for Microsoft Windows to images. Those images should be activated with the associated key.”

But if I understand your post correctly you should not need to use the mentioned Windows Key plugin at all. Each Host object in the database has it’s own field for the Windows Product key (as seen in the web UI host settings page). This is stored in the same DB table and therefore directly connected: host <-> key

…i don’t know if it’s a bug or it’s just me…but sometimes , after i add the “Host Product Key” and click “Update” …then add something in the “Host Description” and click “Update” again …the information in the “Host Product Key” just vanishes

This is definitely not ok! We need to look into why this is happening.

1. Uninstall the Windows Key plugin because I am sure this is not gonna help in your case as stated above. The plugin code is being less well looked at and so chances are higher this has a bug and could even cause trouble.
2. Talk to your folks using the FOG web UI (everyone!) to see if others might be seeing the same issue when saving host information and as well if possibly people edit the same host object and overwrite each others settings.
3. Take a look at the apache error log (see my signature) and post errors found there in this forum topic.
4. Try to replicate the “lost settings” issue so we get some more grip on how to fix this - I have done some testing and it’s not happening for me.

@dashwell said in Problem with INIT.xz @ 74%:

new series of laptops

Beside the excellent hints George already gave I might ask which make and model exactly are we talking about?

@Flyer said in WOL Not Working After Imaging:

I guess they only way to know is to test.

Exactly.

@pep Finally found some time to properly document this issue on github.

Update issue: https://github.com/FOGProject/fogproject/issues/561
Snapin issue: https://github.com/FOGProject/fogproject/issues/562

Both should be fixed in latest dev-banch. The later still needs some good testing. I just did a very basic test to make sure the default schema is being applied.

@sgoodman Reviving this topic as I think this would be good to get done for the next 1.5.x release.

@brian-mainake Need more information.

@dyacishyn We need more information. Please run the following commands and post output here:

lsblk
fdisk -l /dev/sdb
cat /etc/fstab
cat /etc/exports
mount
file -s /dev/sdb*

@Flyer said in WOL Not Working After Imaging:

The only thing that I cannot figure how to get to work automatically (or remotely, like via a snapin) is the enabling of the “Only allow a magic packet to wake the computer” option. This default to OFF in Realtek’s driver, but ON (like it should) in Intel’s.

Looks like there is a registry key for this: https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/power-management-on-network-adapter

Either you add a script to your NIC driver installer snapin to set the registry key or you could even do this via post deploy scripting - find an example of the registry use in the fos code (actuall reged call in line 1054).

@TaTa FOG does not do SSO though you are invited to make it happen. Tell your company to get involved in this open source project, put one developer on this for a few weeks.

@Flyer said in Dual boot (2 disks) unable to boot grub:

Is there a way to set up this script so that it always uses the correct device? For instance, some machines are NVME, some SSD, some rust, etc. So they would have different device names and partition numbers.

Have you looked into using the magic post deploy scripts yet? While I can’t give you a full script example just from memory (don’t have one at hand either) I am pretty sure you have some valuable environment variables at hand when the script is called. So it might be as easy as efibootmgr -c -d $hd -p 1 -L "Debian" -l "\EFI\debian\shimx64.efi"

@Flyer said in WOL Not Working After Imaging:

I was wondering about a Snapin. The Realtek drivers use an InstallShield EXE, which supposedly support command like install (haven’t tried it yet).

Sure you can look into deploying the driver via snapins but it needs to be a setup capable of installing silent - and I mean really silent! Probably not all of the NIC drivers come with this option.

I don’t know much about this but to me it sounds like this would be better handled using sysprep and automatic driver install after the first bootup. This is not a specific FOG topic but you can search this forum for sysprep and find a fair amount of posts. As well search the web and you find lots more.

@gandzioreek said:

I tried, didn’t worked

Please give us some more details on what you’ve tried and what happend - screenshots, error messages, … Otherwise we won’t be able to help you.

@Cyrock Possibly you have more than one topic mixed up in this post. The picture shows the fog-client log from a machine while WOL and PXE booting is not directly connected to the fog-client at all. Let’s try to get this sorted:

But when i WOL my PC, boot pxe works and when the menu appear, they restart indefinitely.
boot hard disk 3, 2, 1… and 3, 2, 1…
I must use CTRL+ALT+SUPPR to reboot.

Do you see this behavior with different hardware or is it just happening/you only have one model of machines? I think I have heard of PCs behaving differently when being started via the WOL magic packet compared to switching it on manually. This is not something caused by FOG I reckon. Please download a WOL tool of you choice (e.g. WakeOnLan Tool 2, WakeMeOnLan, PingTool, …) and see if this causes the same loop. Pretty sure you see the same thing. In this case you can try updating the BIOS/UEFI firmware or talk to your mainboard manufacturer and it’s firmware suppliers.

fog-client log: Middleware::Response Invalid security token

This is caused by an old security token in the database most of the time. In the FOG web UI go the the host object you grabbed the log from and you should see the “Reset Encryption” button there just above the hostname and MAC address(es): https://i.imgur.com/2Egs7O2.png

@JYost FOG does not cache the information other than saving this AD information for each host object. So changing the Active Directory information in the FOG settings page does just do that and would not touch the information in the host objects.

So my suggestion in this case is you create a (temporary) group, add all your 2000+ hosts to it and assign the new AD settings via the group. Note that groups in FOG are more or less a tool to handle hosts in a bulk. So the group itself does not store this information but the hosts will receive it. Therefore you can delete that temporary group after setting the AD information.

@AlexPDX Yes, remove the , as suggested by Tom. I will fix this in dev-branch soon.

@Flyer said in WOL Not Working After Imaging:

So installing the NIC driver manually seems to fix this

You mean the NIC driver on Windows??