Topics created by jithinpsk

Hello Jithinpsk ,
I am making a new Kernel according to your method to be able to integrate NVME drivers for a new laptop that is giving us problems for deployments, but unfortunately I cannot finalize the "bzimage" file, do you have any other information, I have tried with several versions of Linux and always from the .config file.
the latest version (6.6.7) provided by theopenem in LIE is no longer well adapted
Thank you for your answer.

@eruthon Checked multicast functionality after disabling SMB, and set a queue size of 2. However, imaging started without waiting for the second PC and failed, as indicated in the screenshot below.

11-21-23 12:24 Starting Multicast Session With The Following Command: cmd.exe /c ""C:\Program Files\Theopenem\Toec-API\\private\apps\udp-sender.exe" --file "D:\toems_local_storage\images\dev_01_MyApps_Win11_CP941\hd0\part2.winpe.wim" --portbase 9028 --min-receivers 2 --ttl 32 --interface 10.38.40.113 --mcast-rdv-address 224.0.0.1 --log D:\multicast.log & "C:\Program Files\Theopenem\Toec-API\\private\apps\udp-sender.exe" --file "D:\toems_local_storage\images\dev_01_MyApps_Win11_CP941\hd0\part3.winpe.wim" --portbase 9028 --min-receivers 2 --ttl 32 --interface 10.38.40.113 --mcast-rdv-address 224.0.0.1 --log D:\multicast.log & "C:\Program Files\Theopenem\Toec-API\\private\apps\udp-sender.exe" --file "D:\toems_local_storage\images\dev_01_MyApps_Win11_CP941\hd0\part4.winpe.wim" --portbase 9028 --min-receivers 2 --ttl 32 --interface 10.38.40.113 --mcast-rdv-address 224.0.0.1 --log D:\multicast.log"

@theopenem_admin Thank you

@theopenem_admin That worked. Thank you for your help

If somebody is looking at a similar solution, you can use PowerShell to do this. This is not my script, but it works perfectly.

<# .Synopsis This script will create a ramdisk containing the boot.wim which the computer will boot to on restart. This script will work only on Windows Imaging environment. .Prerequisites - From the Windows PE boot USB, copy boot.wim in the Sources folder to C:\Sources on the target - From the Windows PE boot USB, copy the Boot folder to C:\ on the target .Notes Because "bcdedit /bootsequence" is used, the computer should boot back into Windows when restarted if imaging is cancelled. #> # Checks that Disk 0 is the boot disk. $DISKZERO = Get-Disk 0 If ($DISKZERO.IsBoot -ne $true) { Write-Host "Disk 0 is not the boot disk. Exiting..." Exit 999 } else { Write-Host "Disk 0 is the boot disk. Proceeding..." } # Create {ramdiskoptions} and configure bcdedit -create "{ramdiskoptions}" bcdedit /set "{ramdiskoptions}" ramdisksdidevice partition=C: bcdedit /set "{ramdiskoptions}" ramdisksdipath \boot\boot.sdi # Add LiteTouch boot device to OSLOADER $Output = bcdedit -create /d "LiteTouch MDT" /application OSLOADER # Obtain LiteTouch boot device GUID $LTGUID = $Output | %{ $_.split(' ')[2] } # Configure LiteTouch to ramdisk boot bcdedit /set $LTGUID device "ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}" bcdedit /set $LTGUID osdevice "ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}" bcdedit /set $LTGUID systemroot \windows bcdedit /set $LTGUID detecthal yes bcdedit /set $LTGUID winpe yes # Adjust for UEFI vs Legacy BIOS types if ($env:firmware_type -eq 'UEFI'){ Write-Host "UEFI boot confirmed." bcdedit /set $LTGUID path \windows\system32\boot\winload.efi } Else { Write-Host "Legacy boot confirmed." bcdedit /set $LTGUID path \windows\system32\boot\winload.exe } # Force LiteTouch ramdisk on next boot and restart bcdedit /bootsequence $LTGUID shutdown /r /f /t 0

@theopenem_admin Thank you.

Sorry, there is not

@theopenem_admin wow that worked like a charm!!! Thank you very much for your prompt response. You are amazing!!!!

Here is the video.
https://www.youtube.com/watch?v=TU9d6df0HUg