Jump to content











Photo
- - - - -

RFI - Widnows 10 Iscsi sysprep.

ipxe iscsi windows 10 sysprep target

  • Please log in to reply
No replies to this topic

#1 moriarty

moriarty
  • Members
  • 2 posts
  •  
    United States

Posted 06 May 2020 - 01:22 AM

Short version:

How do you add iscsi boot to sysprep offline image?

 

Longer version:

 

I need assistance on a project. My current system supports installing windows 10 to an iscsi target and works with:

 

lio (targetcli-fb) linux iscis host - block mode. 1 lun per hard disk (works uefi and bios mode)

ipxe, apache, wimboot - booting winpe v1903 (customizations addition of drivers only)

Samba, running Windows 10 1909 setup (customizations: install.wim injected drivers, pagefile disabled)

second state boot is just ipxe with sanboot to iscsi target. It works fine.

 

Becasue my iscsi server supports snapshots and generating a new iqn per client. I wish to optimize this process further. As now it is generating full disk images on the iscsi server. Using sysprep master image with snaps per client should use much less space. It won't be perfect but it will be better than full images per target. And I wish to boot unfamiliar hardware to sysprep.

 

I have the backend working, but I must be missing part of the windows setup process. How it ensures iscsi installation has boot critical, non lwf, network adapter and iscsi initiator.

 

During setup to iscsi, setup does this (rather undocumented) dism function:

dism.exe  /logpath:E:\$WINDOWS.~BT\Sources\Panther\iscsi_boot_net.log /Image:E:\ /Add-NetAdapter /HostAdapter:{76A614E4-1167-4C66-89B9-2A76C663C547} /BootDriver:ms_tcpip /BootDriver:ms_tcpip6

But I am not running setup, so to get the info I need for the first winpe boot instance I need:

wmic nic get guid,name,servicename

which does appear to generate a network adapter in the sysprep image.

After which a regedit of the offline system to promote the network adapter servicename to boot critical and disable the paging file to help the 1909 pagefile bug.

 

But when the sysprep machine is sanbooted (stage 2) I get BSOD IRQL NOT LESS OR EQUAL.

 

Apologies for any mismatching terminology I am not windows guy.


Edited by moriarty, 06 May 2020 - 01:24 AM.






Also tagged with one or more of these keywords: ipxe, iscsi, windows 10, sysprep, target

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users