Jump to content

- - - - -

Diskless booting problem on different machines

  • Please log in to reply
No replies to this topic

#1 Asky

  • Members
  • 2 posts

Posted 30 June 2023 - 12:40 PM



I managed to install windows diskless boot on a single machine with success. The problem arises when i try to boot the same image on a different machine.


On the working machine when windows starts to boot, after few seconds the ISCSI drive/target disconnects, reconnects again after 7-10 seconds and everything boots normally.


When i try to boot with some other machine (older or newer hardware doesn't matter) when windows starts to boot, after few seconds the ISCSI drive/target disconnects but doesn't reconnect again and gives BOOT_DEVICE BSOD


i don't think the problem is network drivers related because if it boots in recovery and i run wpeutil initializenetwork, it connects again to the iscsi target.

It's like windows doesn't initialize the network if i change the machine


Also if i change the boot file to ipxe-snponly-x86-64.efi (latest version from github) it never reconnects the ISCSI drive even if i use wpeutil.

Any help will be grateful


I use ISCSI Console with Tiny PXE server

#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16066 posts
  • Location:The Outside of the Asylum (gate is closed)

Posted 30 June 2023 - 06:09 PM

From what you report it seems like there is something from the "last booted" machine that remains "sticky".


Maybe there is a way to "generalize" the image, but I don't know. 


It could actually be the network drivers as wpeutil initializenetwork


Semi-random idea:


Have you tried adding the command wpeutil initializenetwork in startnet.cmd? 


It should be executed during booting, it has to be seen if it runs "early enough".


It may be needed to add also a wpeutil waitfornetwork command.




#3 misty


    Gold Member

  • Developer
  • 1065 posts
    United Kingdom

Posted 01 July 2023 - 08:59 AM

It's been a while since I did any network booting. You are essentially installing windows and creating a machine specific installation. Expecting a different machine to boot this image is not realistic. It may be possible to modify the registry in the offline image, however I'm not sure which settings would need to be changed.

Consider the issue and workaround for Windows Filtering Platform (WFP) Lightweight Filter (LWF) when cloning an existing installation for iSCSI booting (http://mistyprojects...iles/wfplwf.htm).


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users