Generate boot.wim

[masterbalby]

Hello,
In the IT department where I work, we use an old MDT server that’s reaching the end of its life cycle.
I’d like to replace it with something more modern.
While searching online, I discovered Opsi.

What will my Opsi server be used for:
- I have a fleet of 2,000 PCs running Windows 11
- When PCs need to be reinstalled, they all go through our repair shop
- So I want to install Windows 11, the drivers for each PC, and a list of software

The Opsi server has two network cards:
- one connected to the internet
- one connected to the Opsi local network (with DHCP for installing the OS)

Where I am now:
- I’ve installed the Opsi server
- I’ve configured the network cards
- I’ve installed the win11-x64 repository and extracted the Windows 11 ISO
- I can boot via PXE and see the Opsi menu
- The PC registers successfully in opsi-configed
- I select “Install win11-x64”
- The PC is partitioned with a WinPE partition
- Files are copied to /mnt/hd
- Additional drivers are found
- The PC reboots

What’s causing the issue?
- I arrive at an interface with a Win11-x64 window featuring a nice Windows icon
- There’s a second window with a terminal showing “Waiting for the network”
- After a while, a window appears with the message: “Failed to mount and no additional network drivers found. Abort program?”

I’m stuck—is this a problem with my boot.wim file?
I’ve generated several using different WinPE network drivers, but I always get the same result.

Any Could someone help me?
Thank you

[ThomasT]

Hi there, basically you seem to be almost there.
It looks like the WinPE does not have the correct drivers for your NIC.

Typically those drivers should be included as described here

In order to find the right driver, i like to try them in WinPE directly. When dealing with a variety of hardware i but a bunch of drivers on an usb-device and stick it in the machine. I then access the Console in WinPE with Shift+F10, navigate to the usb-device and use drvload to load the driver. Once loaded i issue wpeinit and look at the output of ipconfig /all.
Once i have the correct driver i put it in the drivers-directory structure as described above. I would refrain from using a bloated driver-pack as this could lead to different problems.