Hi
I would like to know how the manual procedure to create a single iso of Windows PE 10.x 32/64 bit using only Windows ADK 10 v1511.
Logically this iso should work properly with the computers with the BIOS or UEFI firmware.
Thanks
Bye
Create a single iso containing Windows PE 32/64 bit
Re: Create a single iso containing Windows PE 32/64 bit
Hi balubeto,
I have updated the description of this procedure in the current documentation , which you find on
http://download.uib.de/opsi4.0/doc/html ... e-packages (pdf version to follow in few days)
> proceed to 'Creating a PE'
It also tells you the manual steps below. Btw, this is not an iso. The file being used to boot is a .wim file, which is kind of an iso, but not exactly.
The PEs being created will be suitable both for BIOS and UEFI. you could have the same files in both dirs 'winpe' and 'winpe_uefi' , but a symlink does the trick, too. just historically we read from winpe_uefi folder. But while copying to the client, we decide whether we need the UEFI files (EFI subfolder ), or the bootmgr file. This way, according to MS, will be decided, whether the PE will boot in UEFI or BIOS mode.
Hint here: you won't be able to deploy UEFI clients with opsi, unless you have a modules file that allows it.
You can obtain a test file by mailing to: info@uib.de , or co-fund the module and have it unlocked for you.
cheers, Andre
I have updated the description of this procedure in the current documentation , which you find on
http://download.uib.de/opsi4.0/doc/html ... e-packages (pdf version to follow in few days)
> proceed to 'Creating a PE'
It also tells you the manual steps below. Btw, this is not an iso. The file being used to boot is a .wim file, which is kind of an iso, but not exactly.
The PEs being created will be suitable both for BIOS and UEFI. you could have the same files in both dirs 'winpe' and 'winpe_uefi' , but a symlink does the trick, too. just historically we read from winpe_uefi folder. But while copying to the client, we decide whether we need the UEFI files (EFI subfolder ), or the bootmgr file. This way, according to MS, will be decided, whether the PE will boot in UEFI or BIOS mode.
Hint here: you won't be able to deploy UEFI clients with opsi, unless you have a modules file that allows it.
You can obtain a test file by mailing to: info@uib.de , or co-fund the module and have it unlocked for you.
cheers, Andre
---
hoping to help
if your problem was solved, pls mark this thread as 'SOLVED'. thank you .
-- no PN support --
Andre
hoping to help

if your problem was solved, pls mark this thread as 'SOLVED'. thank you .
-- no PN support --
Andre
Re: Create a single iso containing Windows PE 32/64 bit
I realized that the boot.wim file is a file containing two volume images:ngbr hat geschrieben:Hi balubeto,
I have updated the description of this procedure in the current documentation , which you find on
http://download.uib.de/opsi4.0/doc/html ... e-packages (pdf version to follow in few days)
> proceed to 'Creating a PE'
It also tells you the manual steps below. Btw, this is not an iso. The file being used to boot is a .wim file, which is kind of an iso, but not exactly.
The PEs being created will be suitable both for BIOS and UEFI. you could have the same files in both dirs 'winpe' and 'winpe_uefi' , but a symlink does the trick, too. just historically we read from winpe_uefi folder. But while copying to the client, we decide whether we need the UEFI files (EFI subfolder ), or the bootmgr file. This way, according to MS, will be decided, whether the PE will boot in UEFI or BIOS mode.
Hint here: you won't be able to deploy UEFI clients with opsi, unless you have a modules file that allows it.
You can obtain a test file by mailing to: info@uib.de , or co-fund the module and have it unlocked for you.
cheers, Andre
The first contains the files that allow to start the Windows PE/RE operating system that is used to prepare a computer for Windows installation mounting and initializing the Microsoft Windows Setup volume image.
The second contains the files that allow to install Windows using the files on the installation media. In addition this volume image has the boot flag.
That is right?
Thanks
Bye
balubeto