Can not install Win11-x64 - opsi:4.3

[ctrazzi]

Hello. I am testing your product with the free license (BASIC up to 30 devices).
I was able to rise the Docker with opsi-server and deploy the agent on 2 clients.
I was also able to create and install opsi-product and build in opsi product like swaudit.
Now I am stuck trying to install Windows 11 on one of the client. The client is not empy, it have already Windows 11 installed and the PK is buid in the PC ROM.
These were my steps until now:
1) Enabled Boot from Netwok
2) Installed opsi-winpe on my opsi-server (inside docker)
3) Installed Windows ADK - 10.1.28000.1 november 2025 on client
4) I have set opsi-winpe to "once" from opsi-configed consolle (when I reboot the pc I see the opsi logo in a sort of loading window)
5) From Netboot products I have configured on setup the Win11-x64 opsi product
6) Than I perform "Save and Execute"
Now I try several times even with some reboot from the client but nothig start...I can see when I reboot it the network boot trying to start(ipv4 and ipv6) but at the end it goes on with the normal boot.
I have try to change the netboot.linux-bootimage parameters but nothing have work(but I can see some effects, like the splash screen), I have also try to deactivare the secure boot option as I read on your guide, but in this case the PC was stuck ad I had to perform a bios recovery to enable again the secure boot. Until than, the pc was stuck on a black screen without anything (I have leave it a night to check if was doing something, but nothing has change).
Now the PC is completely dead, not OPSI fault, but with all the attempt probably the BIOS was corrupted.

Can you please provide me some assistance with this problem? I am stuck and I can not understand how to proceed.
Now I have setup another test pc, but before other attempt I wish to understant what can be the issue.

[j.schneider]

Hello,

you need to configure your DHCP server to provide PXE information to the network device (option 66 and 67).

https://docs.opsi.org/opsi-docs-en/4.3/ ... erver.html

Best regards
Jan Schneider

[ctrazzi]

Hello and thank you for your answer.
I have already try so set these option in our DHCP:
- Option 66 = IP Windows HOST for Docker Container with OPSI-SERVER
- Option 67 = opsi/loader/opsi-netboot.x64.efi

I am not sure about the Option 67, since I had found this settings searching a solution to the problem described in the previous post.
Is it correct?

Another thing that might be a problem, but I am not sure, are the installation files.
Can you please confirm that I have to copy and paste the Windows11 ISO content inside this path /var/lib/opsi/depot/win11-x64/installfiles on OPSI-SERVER?

[n.doerrer]

Hi,

That option 67 looks correct (for x64 hardware)

Yes you have to copy or symlink the iso content to /var/lib/opsi/depot/win11-x64/installfiles on the depot.

[ctrazzi]

Hello and thank you for the support until now.
Since I was not sure about how to procede, I had change my Network setup.

I have create a simple LAN NETWORK (so no internet connection) between OPSI-SERVER and OPSI-CLIENT.
On OPSI-SERVER host I have setup a DHCP Server with Open DHCP Server (https://sourceforge.net/projects/dhcpserver/) and the client takes his IP from the DHCP server (192.168.10.xxx).

I have test the connection between the two PCs with ping command and deploying an OPSI-PRODUCT on the client.

This is the DHCP configuration I had done for OPSI in OpenDHCPServer.ini file:

Code: Alles auswählen

[LISTEN_ON]
;IP WINDOWS WITH DOCKER OPSI-SERVER
192.168.10.5

[RANGE_SET]
DHCPRange=192.168.10.100-192.168.10.120
SubnetMask=255.255.255.0

[GLOBAL_OPTIONS]
AddressTime=3600
;NextServer is TFTP/PXE server to contact
NextServer=192.168.10.5
; BootFileName is the boot file to download;
BootFileName=opsi/loader/opsi-netboot.x64.efi

But nothing has changed about the last behavior, I see during client boot procedure that it takes the correct IP from DHCP, but the installation procedure does not start.

What can be the problem?
There is a specific log I can check?

[j.schneider]

The Client is using the TFTP (UDP) protocol to fetch files from the server.
This is most likely a networking problem between the client and the opsi server running as a docker container on Windows.
Get a TFTP client and manually try to fetch files from the opsi server.
For example:

Code: Alles auswählen

# tftp 192.168.10.5
tftp> get /opsi/loader/grub.x64.efi

[ctrazzi]

Hello, after your answer I had perform some tests and at 99% the problem is what you had point out:
"This is most likely a networking problem between the client and the opsi server running as a docker container on Windows."

I had perform some tests like disable windows firewall on all network type, map ports in the docker-compose file, etc... but nothing end well.
I had also try to get a test.txt file from OPSI-SERVER docker to my windows10 host without any success.
This is the request from windows10 powershell running as administrator:

Code: Alles auswählen

tftp -i 127.0.0.1 GET test.txt

These are command and output from docker shell:

Code: Alles auswählen

/ tcpdump -ni any -vvv -s0 "udp port 69 or portrange 30000-30020" 

tcpdump: data link type LINUX_SLL2 tcpdump: listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes 15:59:31.126730 eth0 In IP (tos 0x0, ttl 64, id 60276, offset 0, flags [DF], proto UDP (17), length 45) 

172.18.0.1.47313 > 172.18.0.5.69: [bad udp cksum 0x5855 -> 0x965f!] TFTP, length 17, RRQ "test.txt" octet 15:59:31.127825 eth0 Out IP (tos 0x0, ttl 64, id 23409, offset 0, flags [none], proto UDP (17), length 44) 

172.18.0.5.30007 > 172.18.0.1.47313: [bad udp cksum 0x5854 -> 0xae79!] UDP, length 16

Asking to ChatGPT/Claude/etc...they point out that TFTP does not work well between windows and docker desktop application since the network port used change randomly. From the output above is also evident that the RRQ goes in, the DATA goes out of 30007, but the ACK never comes back.

The various AI chats have suggest to move the docker on a ubuntu 26 virtual machine (running on VMWare), but if is possible I will prefer stay on my current setup.

There is a way to make this thing work on a windows 10 host?