iSCSI initiator with VistaPE ? External links Options

[CP1]

Is it possible to get an iSCSI initiator working with VistaPE ?

I am trying to build a disk with Ghost and iSCSI working on it so that we can migrate data from local disks directly onto SAN LUNS.

I thought that it might be possible for several reasons:
1. I think Vista has built in iSCSI support.
2. There was a plugin for BartPE which was for an iSCSI target (not the same I know but...?)
3. PE 2.0 seems a lot more amenable than the old version.

I have tried installing the MS iSCSI initiator (from a USB key) whilst VistaPE was loaded but it complains about a missing setup.inf file.

I have also tried installing the StarPort initiator from RocketDivision software which does seem to install but then complains that it can't load the driver.

Is there any hope that I might be able to get this going or am I just flogging a dead horse ?

Cheers
Chris

[frodo]

Is it possible to get an iSCSI initiator working with VistaPE ?

I am trying to build a disk with Ghost and iSCSI working on it so that we can migrate data from local disks directly onto SAN LUNS.

I thought that it might be possible for several reasons:
1. I think Vista has built in iSCSI support.
2. There was a plugin for BartPE which was for an iSCSI target (not the same I know but...?)
3. PE 2.0 seems a lot more amenable than the old version.

I have tried installing the MS iSCSI initiator (from a USB key) whilst VistaPE was loaded but it complains about a missing setup.inf file.

I have also tried installing the StarPort initiator from RocketDivision software which does seem to install but then complains that it can't load the driver.

Is there any hope that I might be able to get this going or am I just flogging a dead horse ?

Cheers
Chris

I have been doing a little work with a friend based in the US, and between us we have gotten Microsoft iSCSI to work under XP PE, its still being tested, but should see release when he signs off on it, and im currently as we speak trying to do the Vista iSCSI stuff. so good timing on the question.

You cant install the iscsi initiator under Vista, its built in.....

So far despite this being my first Vista PE script (p.s. I like the format Nuno and all who helped create it), and having all the entries correct, after booting the ImagePath line is blank in the CurrentControlSet key in the registry (despite being present and correct in the ControlSet001 key), weird...but even after filling it in again manually, cant get the service to kick in, the device (.sys) is fine and started.

So the troubleshooting is happening now. Pity that Vista has it built in really, otherwise id just run the working XP PE plugin inf through the converter and you'd have it. vista is something i truly hate as an OS, just ask anybody how many times ive said i hate it and that its a downgrade to XP, so its not surprising to me that something that is simple under XP PE as getting a service running is a pain under Vista PE.. they changed the permissions for services under vista so im reading up on the changes to figure out how to get this thing to fire up properly.

Ill keep you updated on the progress of Vista iSCSI and also give you a heads up when the XP PE Microsoft iSCSI initiator plugin is posted as final.

[bilou_gateux]

Ill keep you updated on the progress of Vista iSCSI and also give you a heads up when the XP PE Microsoft iSCSI initiator plugin is posted as final.

Put me in the list of interested people for a working XP PE Microsoft iSCSI initiator plugin.

[I@n]

I'm also interested on a Working BootCD with iSCSI support. I am also attempting to create a boot CD to use as a data migration tool from local disk to SAN LUNs

[C57D]

Ill keep you updated on the progress of Vista iSCSI and also give you a heads up when the XP PE Microsoft iSCSI initiator plugin is posted as final.

I too am interested in this.
Any idea when you will have something to share?

Thank you.

[dinger76]

I have created a working VistaPe Boot CD which works with iSCSI and Ghost for migrating servers from LAS to SAN Booting iSCSI.
We are using QLogic QLA4050 iSCSI cards, they have a hardware initiator and therefore do not require MS iSCSI Initiator.
I simply went and added the iSCSI card drivers to the Drivers folder within the VistaPE build process. When booting into VistaPE the iSCSI LUNS appear as disks in Disk Manager, I then use Ghost 8 (the last proper DOS based ghost) to migrate the servers across to iSCSI.

We've used a similar process within BartPE as well and have migrated around 60 servers using this method.

[MichaelZ]

[...], I then use Ghost 8 (the last proper DOS based ghost) [...]

I think there is a new DOS and Win32 based version Ghost 11.

Many Greetings
MichaelZ

[Chris_M]

So, it is possible to get the MSiSCSI Initiator Service running in both WinPE 2.0 and BartPE???

Can someone enlighten me as to how this is done...

I have used Dependency Walker to verify I have all the needed files and have the MSiSCSI service entries applied in the reg, but when I run iscsicli I just get an error stating that the iSCSI initiator service is not started!

I am extremely grateful for any info as to how to get the MSiSCSI Initiator working in WinPE 2.0 and/or in BartPe.

[Filip Hasa]

hello everyone,

i am opening old case.

I tried create iSCSI plugin. But I have problem with network devices. I cannot start MSiSCSI service. I got a message "error 1083: The executable program that this service is configured to run in does not implement this service "

I added these files:

to windows\system32:
07/08/2009 10:52 PM <DIR> drivers
07/08/2009 10:52 PM <DIR> en-US
11/02/2006 11:45 AM 144,384 iscsicli.exe
11/02/2006 11:46 AM 209,920 iscsicpl.dll
11/02/2006 11:45 AM 120,320 iscsicpl.exe
11/02/2006 11:46 AM 49,152 iscsidsc.dll
01/21/2008 04:21 AM 8,192 iscsied.dll
01/21/2008 04:21 AM 111,616 iscsiexe.dll
01/21/2008 04:21 AM 14,848 iscsilog.dll
01/21/2008 04:21 AM 28,160 iscsium.dll
01/21/2008 04:21 AM 64,000 iscsiwmi.dll

to windows\system32\drivers:
01/21/2008 04:21 AM 181,304 msiscsi.sys
to windows\system32\en-US:
11/02/2006 02:39 PM 23,552 iscsicli.exe.mui
11/02/2006 02:39 PM 45,056 iscsicpl.dll.mui
11/02/2006 02:39 PM 2,560 iscsicpl.exe.mui
11/02/2006 02:39 PM 14,848 iscsidsc.dll.mui
11/02/2006 02:39 PM 7,168 iscsiexe.dll.mui
01/21/2008 04:23 AM 15,360 iscsilog.dll.mui

and whole registry structure from:

HKEY_LOCAL_MACHINE\_WIM\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0000
HKEY_LOCAL_MACHINE\_WIM\ControlSet001\Control\DeviceClasses\{2accfe60-c130-11d2-b082-00a0c91efb8b}\##?#ROOT#ISCSIPRT#0000#{2accfe60-c130-11d2-b082-00a0c91efb8b}
HKEY_LOCAL_MACHINE\_WIM\ControlSet001\Enum\Root\ISCSIPRT
HKEY_LOCAL_MACHINE\_WIM\ControlSet001\Services\Eventlog\System\iScsiPrt
HKEY_LOCAL_MACHINE\_WIM\ControlSet001\Services\iScsiPrt
HKEY_LOCAL_MACHINE\_WIM\ControlSet001\Services\MSiSCSI
HKEY_LOCAL_MACHINE\_WIM\ControlSet001\Control\CriticalDeviceDatabase\Root#iSCSIPrt

I used source Vista SP1 and I implemented this to WAIK image 2.1 (for Vista SP1)

Any tip is welcome

Thank you for a tension

PS: _WIM is SYSTEM in boot.wim image

[jmmdss]

I've gotten iSCSI to work in WinPE 2.1, so hopefully the same process should work on VistaPE, but I'm not an expert on building plugins. Maybe this will help someone anyway.

I'm posting the contents of four files:

1. The file that puts the iSCSI files and registry entries into the WinPE image during the build process. Unfortunately, I don't remember where all the file sources are from. I think I took them from a Vista installation (perhaps after installing the initiator).

CODE

xcopy /S /Y "C:\iscsi\windows\*" c:\Temp\winpe_x86\mount\Windows\*
reg load HKLM\PE_SYSTEM c:\Temp\winpe_x86\mount\Windows\System32\config\SYSTEM
regedit /s "C:\iscsi\iscsi.reg"
reg unload HKLM\PE_SYSTEM

2. The file that lists the dirs/files needed for the xcopy operation.

CODE

[DIRS]
C:\iscsi\windows\iSCSI
C:\iscsi\windows\system32
C:\iscsi\windows\system32\drivers

[FILES]
C:\iscsi\windows\iSCSI\iscsi.cat
C:\iscsi\windows\iSCSI\iscsi.inf
C:\iscsi\windows\iSCSI\iscsidsc.mof
C:\iscsi\windows\iSCSI\iscsievt.mof
C:\iscsi\windows\iSCSI\iscsihba.mof
C:\iscsi\windows\iSCSI\iscsilog.dll
C:\iscsi\windows\iSCSI\iscsiprf.mof
C:\iscsi\windows\iSCSI\iscsiprt.sys
C:\iscsi\windows\iSCSI\iscsirem.mof
C:\iscsi\windows\iSCSI\mpdev.inf
C:\iscsi\windows\iSCSI\mpdev.sys
C:\iscsi\windows\iSCSI\mpio.cat
C:\iscsi\windows\iSCSI\mpio.inf
C:\iscsi\windows\iSCSI\mpio.sys
C:\iscsi\windows\iSCSI\mpspfltr.sys
C:\iscsi\windows\iSCSI\msiscdsm.inf
C:\iscsi\windows\iSCSI\msiscdsm.sys
C:\iscsi\windows\iSCSI\msiscsi.sys
C:\iscsi\windows\system32\iscsicli.exe
C:\iscsi\windows\system32\iscsicpl.cpl
C:\iscsi\windows\system32\iscsidip.dll
C:\iscsi\windows\system32\iscsidsc.dll
C:\iscsi\windows\system32\iscsiexe.exe
C:\iscsi\windows\system32\iscsilog.dll
C:\iscsi\windows\system32\iscsipp.dll
C:\iscsi\windows\system32\iscsium.dll
C:\iscsi\windows\system32\iscsiwmi.dll
C:\iscsi\windows\system32\iscsixip.dll
C:\iscsi\windows\system32\MFC42D.DLL
C:\iscsi\windows\system32\MSVCRTD.DLL
C:\iscsi\windows\system32\oledlg.dll
C:\iscsi\windows\system32\drivers\iscsiprt.sys
C:\iscsi\windows\system32\drivers\msiscsi.sys

3. The file containing the registry entries to import (named iscsi.reg in my example).

CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Enum\Root\LEGACY_MSISCSI]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Enum\Root\LEGACY_MSISCSI\0000]
"Service"="MSiSCSI"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="Microsoft iSCSI Initiator Service"

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Enum\Root\LEGACY_MSISCSI\0000\Control]
"ActiveService"="MSiSCSI"

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Class"="SCSIAdapter"
"HardwareID"=hex(7):52,00,6f,00,6f,00,74,00,5c,00,69,00,53,00,43,00,53,00,49,\
00,50,00,72,00,74,00,00,00,00,00
"Driver"="{4D36E97B-E325-11CE-BFC1-08002BE10318}\\0001"
"Mfg"="Microsoft "
"Service"="iScsiPrt"
"DeviceDesc"="Microsoft iSCSI Initiator"
"ConfigFlags"=dword:00000000
"Capabilities"=dword:00000000

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\LogConf]

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\Control]
"ActiveService"="iScsiPrt"

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Services\iscsiprt]
"DisplayName"="iScsiPort Driver"
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,6d,00,73,00,69,00,73,00,63,00,73,\
00,69,00,2e,00,73,00,79,00,73,00,00,00
"Start"=dword:00000000
"Type"=dword:00000001
"Group"="iSCSI"

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Services\iscsiprt\Enum]
"0"="Root\\SCSIADAPTER\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Services\iscsiprt\Parameters]
"BusType"=dword:00000009

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0000]
"EnumPropPages32"="iscsipp.dll,iSCSIPropPageProvider"
"InfPath"="iscsi.inf"
"InfSection"="iScsiPort_Install_Control"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,00,0e,ad,e1,6e,c5,01
"DriverDate"="6-12-2005"
"DriverVersion"="5.2.3790.1653"
"MatchingDeviceId"="root\\iscsiprt"
"DriverDesc"="Microsoft iSCSI Initiator"

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Services\MSiSCSI]
"Type"=dword:00000010
"Start"=dword:00000002
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,69,\
00,73,00,63,00,73,00,69,00,65,00,78,00,65,00,2e,00,65,00,78,00,65,00,00,00
"DisplayName"="Microsoft iSCSI Initiator Service"
"Group"="iSCSI"
"ObjectName"="LocalSystem"
"Description"="Manages Internet SCSI (iSCSI) sessions from this computer to remote iSCSI target devices.

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Services\MSiSCSI\Enum]
"0"="Root\\LEGACY_MSISCSI\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Services\NetBT]
"Start"=dword:00000000

[HKEY_LOCAL_MACHINE\PE_SYSTEM\ControlSet001\Services\Afd]
"Start"=dword:00000000

4. The file showing usage in the WinPE environment (uppercase words should be replaced with the appropriate values--setting an IP may not be necessary if using DHCP).

CODE

net start msiscsi

netsh interface ip set address name="Local Area Connection" static MACHINE_IP MACHINE_MASK MACHINE_DEFGATEWAY 1

iscsicli nodename MACHINE_IQN
iscsicli addtargetportal SAN_IP 3260 * * * * * * * * * * * *
iscsicli logintarget SAN_IQN t * * Root\SCSIADAPTER\0000_0 SAN_IP 3260 * * * * * * * * * * 0

The first file is actually just a snippet of a batch file that I use when building the WinPE image. I hope this helps. I can try to figure out where I got the source files from if needed. It was from some post or something, actually all of this process is, but honestly I don't remember for sure where I read it.