Following discussions in the SANBOOT Windows on UEFI system? topic and lots of recent tests, I have updating this post. My original post is included below for continuity purposes (so that the discussion that follows this first post makes sense).

A more detailed comparison of Windows iscsi targets is available here (and also attached to this post in case there are future issues accessing the mistyprojects.co.uk site).

The following is a list of Windows iSCSI Target Software. Some old, some new, most still available. I have also indicated which Targets support installing and booting Windows from Storage Area Network (SAN) - and whether this is supported using Client/Initiators Systems with BIOS or UEFI Firmware.

Kernsafe iSCSI SAN - a free version is available for download (iStorage Server Free) - you will need to register for an account in order to apply for a free license. Registering for an account is relatively straightforward - at the time of writing it's possible to download a 20-day trial version without registering. BIOS Clients - SAN Boot Supported. UEFI Clients - SAN Boot NOT supported..

StarWind Virtual SAN - as of 10th June 2019 the most recent version is StarWind 8. A Free license/version is available. At the time of writing (10th June 2019) the StarWind Management Console (GUI) can only be used for monitoring purposes, and using the GUI for Target management is disabled in the FREE version/license (see here). Powershell scripts can be used for Target management functions in the FREE version. BIOS Clients - SAN Boot Supported. UEFI Clients - SAN Boot NOT supported..

Starwind - legacy versions - including versions 4 / 5.2 / 5.8 / 6.0. As far as I am aware these versions are no longer available commercially. A FREE license appears to have been available for all of these versions at the time of release - with limited functionality. Versions 4.0 and 5.2 both offer a trial period without a licence. Version 5.8 and 6.0 cannot be installed successfully without a license. BIOS Clients - SAN Boot Supported. UEFI Clients - SAN Boot supported.

pyTarget - "...Implement a powerful iSCSI target in python, easily use under most popular systems. ..." - a standalone binary is available for Windows 32-bit (will run without python environment). This project does not have a GUI, however it can be configured from a web interface. Alternatively a .xml configuration file can be used. BIOS Clients - SAN Boot Supported. UEFI Clients - SAN Boot NOT supported..

SANDeploy Server - 30 day trial. Two version are available - SANDeploy Server and SANDeploy Boot Server (which includes DHCP and TFTP server). BIOS Clients - SAN Boot Supported. UEFI Clients - SAN Boot NOT supported..

Kernsafe iSCSI SAN - a free version is available for download (iStorage Server Free) - you will need to register for an account in order to apply for a free license. Registering for an account is relatively straightforward - at the time of writing it's possible to download a 20-day trial version without registering.

StarWind Virtual SAN - a Free license/version is available. Personally I found it very difficult to register and obtain a free license as a corporate email address is required.

pyTarget - "...Implement a powerful iSCSI target in python, easily use under most popular systems. ..." - a standalone binary is available for Windows 32-bit (will run without python environment). This project does not have a GUI, however it can be configured from a web interface. Alternatively a .xml configuration file can be used.

SANDeploy Server - 30 day trial. Two version are available - SANDeploy Server and SANDeploy Boot Server (which includes DHCP and TFTP server). Not tested.

pyTarget looks particularly promising - a Quick and Dirty GUI would be useful

Attached Files

Writing this on a SAN Booted Windows 8.1 - booted from an pyTarget Target.

Client IQN must be specified in the pyTarget configuration file or SANHOOK/SANBOOT will fail.

Use iPXE set initiator-iqn command to set Client IQN to the same name as the IQN specified in the pyTarget config file.

I thought that there might be problems when Windows booted due to the possibility of Windows setting a different IQN and disk access being lost in the handover. Ran iscsicli.exe in Windows and received the following output -

I don't think it likes VHD files. Haven't tested properly, but I'm guessing that the 1 sector header on fixed VHD's is mounted along with the rest of the file - this is purely conjecture at this point.

Misty

P.s. If the disk image is in the same directory as the exe then the path can be omitted - handy for portable operation(s).

My disk is 256MB = 262144KB.Multiply by 2 and I get the right capacity i.e 524288.Or easier ... 256 *2048 ... should have read closer...I must be slow today...

RT(F)M!

....GUI time now.

Misty

P.s. Just tried a fixed VHD as target. Created the VHD on my server using DiskPart - partitioned, formatted, etc. Connected from a Windows 7 PC (not SAN boot - just connected as storage) - it mounted the single partition without any problems.

I don't think it likes VHD files. Haven't tested properly, but I'm guessing that the 1 sector header on fixed VHD's is mounted along with the rest of the file - this is purely conjecture at this point.

Misty

Just for the record, there is NO 1 sector header in fixed VHD, there is a 1 sector footer (the CONECTIX descriptor sector) appended to the RAW image.

@WonkoThanks for the info. I couldn't recall if it was a header, or footer, or both! Due to other commitments and an ability to get easily distracted, I have had to limit my experiments with VHD files. I have a guide to update - a guide I seem to recall you volunteering me for!!!

@Wonko
Thanks for the info. I couldn't recall if it was a header, or footer, or both! Due to other commitments and an ability to get easily distracted, I have had to limit my experiments with VHD files. I have a guide to update - a guide I seem to recall you volunteering me for!!!

Attempted to install Windows 7 (SP1 - 32-bit) directly to a pyTarget Target - it failed to boot during stage 2 (the first reboot after running setup.exe).

A windows 7 disk created with a different Target software (Kernsafe iStorage Server) booted ok when moved to pytarget.

Haven't got a clue what's happening.

Misty

P.s. I haven't tried cloning Windows 7 to a pyTarget Target.

EDIT - I just happened to have an AoE disk cloned from a Windows 2008 R2 SP1 system lying around - mounted this in pyTarget - it took ages to complete the first boot and then prompted to reboot on reaching the desktop - seemed fine on reboot.