Starwind iSCSI initiator problem

ianparcher · Tue Oct 23, 2012 3:36 pm

Hello all, looking for help with an issue.

Windows 2008 R2 box connecting via Starwind iSCSI initiator 5.6
To
Windows server standard 2007 SP2 running Starwind 5.8.2059

When I go through the wizard on the initiator when I select CHAP automount becomes greyed out. Even after the connection is created and I try to edit it the same thing. Automount this device is greyed out. So when I reboot it doesn't remount the drive. Is there something im missing here?
Thanks,
-Ian

Tue Oct 23, 2012 5:00 pm

Stick with MS initiator for production. StarPort is supported as a legacy software only (say "thanks" to Microsoft).

KurianOfBorg · Wed Jun 05, 2013 8:58 am

Why was this done?

Wed Jun 05, 2013 1:11 pm

Why was this done?

Would you please clarify that?
Thank you

KurianOfBorg · Wed Jun 05, 2013 3:24 pm

I meant is there no case where the StarPort Initiator should be used anymore? Is it completely superceded by the Microsoft Initiator for all configurations?

Wed Jun 05, 2013 3:58 pm

Microsoft does not support anything except MS initiator in production so with any issue we'll be the one to blame automagially... We don't want this (neither do you I guess) so please stick with MS initiator for production scenarios.

You can use StarWind initiator for experiments (to see how fast you can go for example) and for protocols Microsoft does not support so far: AoE and FCoE. Pure Test & Development is fine

KurianOfBorg wrote:I meant is there no case where the StarPort Initiator should be used anymore? Is it completely superceded by the Microsoft Initiator for all configurations?