Seite 1 von 1
[resolved] After a pxe boot : obtaining a boot menu instead of automatically launching the Windows ("netboot") install
Verfasst: 27 Sep 2023, 15:46
von bourhis
Hi,
for about a week, on new PCs, the automated installation via a pxe boot no longer works correctly : I obtain a startup menu instead of the automatic launch of the installation of the "netboot" product selected in "opsi-configured".
N.B. : if I choose the 2nd option in the menu (the first is to boot from the local hard drive) and provide it with an "admin" login and password, then select the "netboot" product to install, it works normally.
Did I forget to configure something?
Best regards.
Re: After a pxe boot : obtaining a boot menu instead of automatically launching the Windows ("netboot") installation
Verfasst: 28 Sep 2023, 09:37
von m.radtke
Hi,
it would be good to know what happens on the tftp side on the server when the client tries to netboot
and see what the server deploys and what gets requested. Expecially the requested boot file.
Regards
Mathias
Re: After a pxe boot : obtaining a boot menu instead of automatically launching the Windows ("netboot") installation
Verfasst: 02 Okt 2023, 09:30
von bourhis
Hi,
I don't see any difference between the first one (172.18.61.92) on Windows 11 and the other (172.18.61.106) on Windows 10 which works :
Code: Alles auswählen
Sep 27 15:15:28 bropsi in.tftpd[13475]: RRQ from 172.18.61.92 filename linux/pxelinux.cfg/opsi-netboot.efi
Sep 27 15:15:28 bropsi in.tftpd[13475]: tftp: client does not accept options
Sep 27 15:15:28 bropsi in.tftpd[13476]: RRQ from 172.18.61.92 filename linux/pxelinux.cfg/opsi-netboot.efi
Sep 27 15:15:33 bropsi in.tftpd[13477]: RRQ from 172.18.61.92 filename /grub/grub.cfg-01-bc-0f-f3-c4-90-33
Sep 27 15:15:33 bropsi in.tftpd[13478]: RRQ from 172.18.61.92 filename /grub/grub.cfg-AC123D5C
Sep 27 15:15:33 bropsi in.tftpd[13479]: RRQ from 172.18.61.92 filename /grub/grub.cfg-AC123D5
Sep 27 15:15:33 bropsi in.tftpd[13480]: RRQ from 172.18.61.92 filename /grub/grub.cfg-AC123D
Sep 27 15:15:33 bropsi in.tftpd[13481]: RRQ from 172.18.61.92 filename /grub/grub.cfg-AC123
Sep 27 15:15:33 bropsi in.tftpd[13482]: RRQ from 172.18.61.92 filename /grub/grub.cfg-AC12
Sep 27 15:15:33 bropsi in.tftpd[13483]: RRQ from 172.18.61.92 filename /grub/grub.cfg-AC1
Sep 27 15:15:33 bropsi in.tftpd[13484]: RRQ from 172.18.61.92 filename /grub/grub.cfg-AC
Sep 27 15:15:33 bropsi in.tftpd[13485]: RRQ from 172.18.61.92 filename /grub/grub.cfg-A
Sep 27 15:15:33 bropsi in.tftpd[13486]: RRQ from 172.18.61.92 filename /grub/x86_64-efi/command.lst
Sep 27 15:15:33 bropsi in.tftpd[13487]: RRQ from 172.18.61.92 filename /grub/x86_64-efi/fs.lst
Sep 27 15:15:33 bropsi in.tftpd[13488]: RRQ from 172.18.61.92 filename /grub/x86_64-efi/crypto.lst
Sep 27 15:15:33 bropsi in.tftpd[13489]: RRQ from 172.18.61.92 filename /grub/x86_64-efi/terminal.lst
Sep 27 15:15:33 bropsi in.tftpd[13490]: RRQ from 172.18.61.92 filename /grub/grub.cfg
Sep 27 15:15:33 bropsi in.tftpd[13491]: RRQ from 172.18.61.92 filename /linux/pxelinux.cfg/01-bc-0f-f3-c4-90-33
Sep 27 15:15:35 bropsi in.tftpd[13492]: RRQ from 172.18.61.92 filename /linux/install-x64
Sep 27 15:15:42 bropsi in.tftpd[13493]: RRQ from 172.18.61.92 filename /linux/miniroot-x64
Sep 27 15:22:29 bropsi in.tftpd[13516]: RRQ from 172.18.61.106 filename linux/pxelinux.cfg/opsi-netboot.efi
Sep 27 15:22:29 bropsi in.tftpd[13516]: tftp: client does not accept options
Sep 27 15:22:29 bropsi in.tftpd[13517]: RRQ from 172.18.61.106 filename linux/pxelinux.cfg/opsi-netboot.efi
Sep 27 15:22:30 bropsi in.tftpd[13518]: RRQ from 172.18.61.106 filename /grub/grub.cfg-01-8c-ec-4b-42-c9-58
Sep 27 15:22:30 bropsi in.tftpd[13519]: RRQ from 172.18.61.106 filename /grub/grub.cfg-AC123D6A
Sep 27 15:22:30 bropsi in.tftpd[13520]: RRQ from 172.18.61.106 filename /grub/grub.cfg-AC123D6
Sep 27 15:22:30 bropsi in.tftpd[13521]: RRQ from 172.18.61.106 filename /grub/grub.cfg-AC123D
Sep 27 15:22:30 bropsi in.tftpd[13522]: RRQ from 172.18.61.106 filename /grub/grub.cfg-AC123
Sep 27 15:22:30 bropsi in.tftpd[13523]: RRQ from 172.18.61.106 filename /grub/grub.cfg-AC12
Sep 27 15:22:30 bropsi in.tftpd[13524]: RRQ from 172.18.61.106 filename /grub/grub.cfg-AC1
Sep 27 15:22:30 bropsi in.tftpd[13525]: RRQ from 172.18.61.106 filename /grub/grub.cfg-AC
Sep 27 15:22:30 bropsi in.tftpd[13526]: RRQ from 172.18.61.106 filename /grub/grub.cfg-A
Sep 27 15:22:30 bropsi in.tftpd[13527]: RRQ from 172.18.61.106 filename /grub/x86_64-efi/command.lst
Sep 27 15:22:30 bropsi in.tftpd[13528]: RRQ from 172.18.61.106 filename /grub/x86_64-efi/fs.lst
Sep 27 15:22:30 bropsi in.tftpd[13529]: RRQ from 172.18.61.106 filename /grub/x86_64-efi/crypto.lst
Sep 27 15:22:30 bropsi in.tftpd[13530]: RRQ from 172.18.61.106 filename /grub/x86_64-efi/terminal.lst
Sep 27 15:22:30 bropsi in.tftpd[13531]: RRQ from 172.18.61.106 filename /grub/grub.cfg
Sep 27 15:22:30 bropsi in.tftpd[13532]: RRQ from 172.18.61.106 filename /linux/pxelinux.cfg/01-8c-ec-4b-42-c9-58
Sep 27 15:22:30 bropsi in.tftpd[13533]: RRQ from 172.18.61.106 filename /linux/install-x64
Sep 27 15:22:35 bropsi in.tftpd[13534]: RRQ from 172.18.61.106 filename /linux/miniroot-x64
Best regards
Re: After a pxe boot : obtaining a boot menu instead of automatically launching the Windows ("netboot") installation
Verfasst: 04 Okt 2023, 08:59
von m.radtke
Hi,
does the file
exist?
What is the content of the file?
Whats the MAC Address of the machine in the opsi-configed?
Regards
Re: After a pxe boot : obtaining a boot menu instead of automatically launching the Windows ("netboot") installation
Verfasst: 04 Okt 2023, 09:22
von bourhis
Hi,
No it doesn't exist but neither does the other one (the one whose installation works).
Regards.
Re: After a pxe boot : obtaining a boot menu instead of automatically launching the Windows ("netboot") installation
Verfasst: 04 Okt 2023, 11:53
von m.radtke
Hi
what file is created when you set the netboot package to setup.
You can check this in the opsipxeconfd.log
if the file disappears within seconds without the client booting/requesting it there might be an AV software that checks those files. Those files disappear when an access is registered.
Re: After a pxe boot : obtaining a boot menu instead of automatically launching the Windows ("netboot") installation
Verfasst: 04 Okt 2023, 13:43
von bourhis
Hi,
in the case that's works :
Code: Alles auswählen
[5] [2023-09-27 15:21:19.351] [Opsipxeconfd ] Got connection from client (opsipxeconfd.py:244)
[3] [2023-09-27 15:21:19.352] [ ] Cannot use more than one pxe config template, got: /tftpboot/linux/pxelinux.cfg/install-grub-x64, install-x64 (opsipxeconfd.py:776)
[5] [2023-09-27 15:21:19.352] [ ] Did not find any alternate UEFI pxeConfigTemplate, will use the default UEFI template (opsipxeconfd.py:782)
[5] [2023-09-27 15:21:19.352] [ ] UEFI GRUB configuration detected for iutgestb106.iutb.univ-brest.fr (pxeconfigwriter.py:160)
[5] [2023-09-27 15:21:19.353] [PXEConfigWriter] Creating config '/tftpboot/linux/pxelinux.cfg/01-8c-ec-4b-42-c9-58' and waiting for access (pxeconfigwriter.py:210)
[5] [2023-09-27 15:21:19.353] [ ] PXE boot configuration for host iutgestb106.iutb.univ-brest.fr is now set at '/tftpboot/linux/pxelinux.cfg/01-8c-ec-4b-42-c9-58' (opsipxeconfd.py:644)
[5] [2023-09-27 15:22:30.372] [PXEConfigWriter] Deleting config file '/tftpboot/linux/pxelinux.cfg/01-8c-ec-4b-42-c9-58' (pxeconfigwriter.py:240)
And for my problematic PC :
Code: Alles auswählen
[5] [2023-09-27 14:53:59.570] [Opsipxeconfd ] Got connection from client (opsipxeconfd.py:244)
[3] [2023-09-27 14:53:59.572] [ ] Cannot use more than one pxe config template, got: /tftpboot/linux/pxelinux.cfg/install-grub-x64, install-x64 (opsipxeconfd.py:776)
[5] [2023-09-27 14:53:59.572] [ ] Did not find any alternate UEFI pxeConfigTemplate, will use the default UEFI template (opsipxeconfd.py:782)
[5] [2023-09-27 14:53:59.624] [ ] UEFI GRUB configuration detected for iutgestb92.iutb.univ-brest.fr (pxeconfigwriter.py:160)
[5] [2023-09-27 14:53:59.624] [PXEConfigWriter] Creating config '/tftpboot/linux/pxelinux.cfg/01-a4-bb-6d-ed-66-f6' and waiting for access (pxeconfigwriter.py:210)
[5] [2023-09-27 14:53:59.624] [ ] PXE boot configuration for host iutgestb92.iutb.univ-brest.fr is now set at '/tftpboot/linux/pxelinux.cfg/01-a4-bb-6d-ed-66-f6' (opsipxeconfd.py:644)
It don't use the correct mac adress : that's the problem ! But why ?
Now that I know which log file to look in, I will test further next time.
Thanks
Re: After a pxe boot : obtaining a boot menu instead of automatically launching the Windows ("netboot") installation
Verfasst: 04 Okt 2023, 14:21
von m.radtke
Hi
this is the mac address in the opsi-backend.
to me it seems you have MAC Passthrough enabled. You can change these setting in the UEFI settings
Regards
Mathias