winpe_uefi Error

[Infotech]

Hello,

I would need help with this:
The folder is not empty, everything is there, media, mount and fwfiles.
Don't know how to make this work..

error.png (628.89 KiB) 2654 mal betrachtet

[Infotech]

```/var/lib/opsi/depot/win11-x64/winpe_uefi# dir
fwfiles media mount```

Everything should be there.

[Rdtrx]

Hast du dir ein WinPE per Windows ADK erstellen lassen und die erzeugeten Dateien dann ins winpe_uefi Verzeichnis gepackt?

[mtb]

‘WinPE directory... UEFI seems to be empty’


The problem occured to me myself, Iwas able to solve the problem, so maybe it will help others too.


Path problem:

When creating the WinPE version for PXE, a temporary folder was created, which seemed to be responsible for the problems.

Code: Alles auswählen

/var/lib/opsi/depot/win11-x64/winpe/media
total 3156
drwxrwsr-x  2 opsiconfd opsifileadmins    4096 Mar  5 15:56 bg-bg
drwxrwsr-x 39 opsiconfd opsifileadmins    4096 Mar  5 15:56 Boot
-rwxrwxr-x  1 opsiconfd opsifileadmins  449800 Jan  8  2025 bootmgr
-rwxrwxr-x  1 opsiconfd opsifileadmins 2622792 Jan  8  2025 bootmgr.efi

I moved all files up one level and deleted the temporary folder. Now the structure looks like this:

Code: Alles auswählen

/var/lib/opsi/depot/win11-x64/winpe
total 3156
drwxrwsr-x  2 opsiconfd opsifileadmins    4096 Mar  5 15:56 bg-bg
drwxrwsr-x 39 opsiconfd opsifileadmins    4096 Mar  5 15:56 Boot
-rwxrwxr-x  1 opsiconfd opsifileadmins  449800 Jan  8  2025 bootmgr
-rwxrwxr-x  1 opsiconfd opsifileadmins 2622792 Jan  8  2025 bootmgr.efi

Permission problem:

It may also be due to permissions. The PXE/Netboot service runs under the user ‘nobody’ (which is the default user in Linux, as I´ve learned today )
I changed that via

Code: Alles auswählen

sudo find /var/lib/opsi/depot/win11-x64/winpe -type d -exec chmod 755 {} \;

sudo find /var/lib/opsi/depot/win11-x64/winpe -type f -exec chmod 644 {} \;

opsi-set-rights

BOOTPSettings: Path must point exactly to EFI file:

Code: Alles auswählen

opsi/loader/opsi-netboot.x64.efi

First, I corrected the permissions and then noticed the path problem, so maybe it works without it.
In this case, the opsi-client-agent hadn´t been installed yet.


regards, Miriam