I have a pair of Server 2016 VMs in a failover cluster running the File Server and iSCSI Target Server roles. Previously each role was separately defined in the Failover Cluster Manager, but due a need for the iSCSI Target Server to be able to store its virtual disks on the same storage as the File Server cluster volume, the iSCSI Target Server Service/Server Name/Storage was transferred to the File Server role.
After the transfer I am no longer able to add new iSCSI disks via the Server Manager application. The New iSCSI Virtual Disk Wizard says there are no eligible servers available. The iSCSI Target Server itself continues to function and allows initiators to connect, and I am able to add iSCSI virtual disks and targets via PowerShell without issue. The new disks and targets created via PowerShell do show up in Server Manager. And if I transfer the iSCSI Target Server Service/Server Name/Storage back to the iSCSI Target Server role, Server Manager does allow me to add new iSCSI disks.
Does anyone know what (if anything) can be done to allow me to manage the iSCSI Target Server via Server Manager? I've tried moving the role to the other node in the cluster, and relaunching the Server Manager just in case there was cached data but it still doesnt allow me to add new iSCSI virtual disks.
Best Answer
I see similar issue posted on technet. Is there any chance to see what does Event Log show?
For the case, from my experience, Microsoft iSCSI target is too slow. Currently, I use StarWind Virtual SAN Free that delivers really fast iSCSI server with the additional functionality of cache and log-structured file system (snapshots, dedupe, etc.). I suggest you try it since it solves the problem having a single management console: iSCSI server can be installed on whatever host you will to run it and then you can manage the server from any host at all using web GUI. StarWind Virtual SAN allows using PowerShell as well if you want to.