we are using Windows Server 2012 R2 to provide some iSCSI targets for other servers. The server has a storage pool, and there is a virtual disk on top of that, and then an iSCSI target is created on this virtual disk.

However, after server restart, the target is always lost and the initiator cannot connect to this target. If I then restart the Microsoft iSCSI Software Target service (i.e. "WinTarget"), the target is initialized properly and works fine.

Since I believe this is a dependency issue, I tried setting the service startup to "Automatic (Delayed Start)", but it fails with an error ("The delayed start could not be set, parameter is incorrect").

Is this a known issue? I.e. if yes, how do I delay startup of this service?

2 Answers 2


Yes, this is a known issue. Unfortunately native Microsoft iSCSI Target is not something that can be put in production. It is slow, unstable, has limited performance and no caching etc. There are multiple free tools that a capable to provide you with a fast and reliable iSCSI target. We are using Starwind https://www.starwindsoftware.com/starwind-virtual-san-free for this purposes that provides iSCSI targets for ESX and Windows servers. Will solve your issues for sure.

  • 3
    Thanks, StarWind Virtual SAN Free looks interesting, especially if it's really free for commercial use. I am not sure about speed/stability of MS iSCSI, we are using this server for SQL backups over 1Gbps Ethernet and haven't really had anything else to compare it to. Are there some sources/links available regarding its speed/stability issues?
    – vgru
    Commented Oct 13, 2016 at 10:50
  • 3
    Actually I do not have those, but I have tried Microsoft iSCSI Target previously to switching to Starwind and encountered a lot of troubles, especially with ESX hosts. I have also performed some benchmarking of both solutions and realized that MSFT is much slower.
    – Net Runner
    Commented Oct 13, 2016 at 11:13
  • 3
    Ok, found a couple of them myself: StarWind iSCSI vs. Microsoft iSCSI by Jacob Rutski shows a 10x difference. The article also mentions that MS iSCSI does not utilize any RAM read/write caching, meaning improved reliability at the expense of performance (adding more RAM to the box will aid nothing).
    – vgru
    Commented Oct 13, 2016 at 11:39
  • 2
    Yeah, that is what I meant. Moreover, you can use Starwind without RAM caching at all or write-through caching (so only READ operations are cached) and it will still perform better.
    – Net Runner
    Commented Oct 13, 2016 at 11:56

Delayed Startup workaround (will work for any service/app):

Using the idea from this thread, credit to James Roper, I set the service startup type to Manual (this option works, unlike Delayed Start) and added a startup script (with a delay) to start the service, effectively getting a "delayed startup":

  1. Set the Microsoft iSCSI Software Target Service startup type to Manual
  2. Create a file named StartISCSI.CMD somewhere, containing the following commands (WinTarget is the name of the iSCSI Target Service):

    timeout 60
    net start WinTarget
  3. Create a scheduled task to run StartISCSI.CMD on startup (configured to start even if nobody is logged in).

This is not exactly an answer to my question, but at least it's a workaround so it might be helpful to others until someone gives a better idea of why this isn't working properly.

  • 1
    That's not going to help 100%... Commented Oct 14, 2016 at 21:25
  • @BaronSamedi1958: yeah, not the best solution, but it solved (or masked) my problem for now. I am still hoping someone would clarify why it doesn't work if the service starts early.
    – vgru
    Commented Oct 15, 2016 at 17:14

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .