Jump to content











Photo
- - - - -

How to check that WinPE is booted from PXE?

pxe winpe network boot

Best Answer memoarfaa , 10 November 2017 - 09:19 PM

See this post
 

Not entirely related to wimboot over different platforms, but since latest wimboot version (2.6.0), you can inject files in the wim file on the fly.
 
You can provide additional files to wimboot. These files will appear within the X:\Windows\System32 directory. For example:[/size]
kernel wimboot
initrd winpeshl.ini winpeshl.ini
initrd startup.bat startup.bat

initrd boot/bcd BCD
initrd boot/boot.sdi boot.sdi
initrd sources/boot.wim boot.wim
boot

You can use this to control the boot process after Windows PE has started. For example, you can use a startup batch file to automatically start the Windows installer from a network share.

Go to the full post


  • Please log in to reply
4 replies to this topic

#1 nguyentu

nguyentu

    Frequent Member

  • Advanced user
  • 102 posts
  •  
    Vietnam

Posted 09 November 2017 - 09:42 PM

Hi,

 

I use Tiny PXE Server and wimboot to boot into WinPE.
Can this be detected by programs? Such as registry keys or files...?
 
Thanks!


#2 netlord

netlord

    Member

  • Members
  • 32 posts
  •  
    Germany

Posted 10 November 2017 - 12:36 PM

Hi there

 

its easy - check the variable firmware_type (echo %firmware_type%)

 

Have fun!



#3 nguyentu

nguyentu

    Frequent Member

  • Advanced user
  • 102 posts
  •  
    Vietnam

Posted 10 November 2017 - 02:48 PM

Hi,

echo %firmware_type%
It has only two values, UEFI and Legacy.


#4 netlord

netlord

    Member

  • Members
  • 32 posts
  •  
    Germany

Posted 10 November 2017 - 03:07 PM

Oh sorry, I misunderstood you.

 

For clarifying - you have an usb device and/or an pxe server and/or pe installed locally and/or an cd/dvd and you would like to know from what device PE has booted?

 

You should know what device you use....



#5 memoarfaa

memoarfaa

    Member

  • Members
  • 81 posts
  •  
    Egypt

Posted 10 November 2017 - 09:19 PM   Best Answer

See this post
 

Not entirely related to wimboot over different platforms, but since latest wimboot version (2.6.0), you can inject files in the wim file on the fly.
 
You can provide additional files to wimboot. These files will appear within the X:\Windows\System32 directory. For example:[/size]
kernel wimboot
initrd winpeshl.ini winpeshl.ini
initrd startup.bat startup.bat

initrd boot/bcd BCD
initrd boot/boot.sdi boot.sdi
initrd sources/boot.wim boot.wim
boot

You can use this to control the boot process after Windows PE has started. For example, you can use a startup batch file to automatically start the Windows installer from a network share.


  • nguyentu likes this





Also tagged with one or more of these keywords: pxe, winpe, network boot

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users