Last time I took a look at Hyper-V Server 2008 R2 Beta, I shared the surprise of having Failover Clustering and the possibility to have highly available virtualized workloads on it.

This time I look at an implication of having the Windows Enterprise-like Quick Migration and Live Migration features: increased complexity and configuration burden.

iSCSIcli in Hyper-V Server 2008

In Hyper-V Server 2008 and Server Core Installations of Windows Server 2008 to connect to SAN storage you would use the iscsicli.exe tool. This is the command line equivalent of the iSCSI client configuration tool. This command line tool requires you to utilize your asterisk button a lot. (to accept default values)

Typical commands to connect to your SAN storage look like these:

iscsicli qaddtargetportal iscsihost.domainname.tld UserName Password
iscsicli persistentlogintarget quorum T * * * * * * * * * * * UserName Password 1 * 0
iscsicli persistentlogintarget vms T * * * * * * * * * * * UserName Password 1 * 0
iscsicli qlogintarget quorum UserName Password
iscsicli qlogintarget vms UserName Password

Not really intuitive, but when you’ve read the Microsoft iSCSI Software Initiator User's Guide and have memorized Appendix C of the document you’re basically ready to go.

iSCSIcpl in Hyper-V Server 2008 R2

To make this crucial step in your cluster setup progress a bit easier, Microsoft has included the graphical version of the iSCSI client configuration tool in Hyper-V Server 2008 R2 and Server Core installations of Windows Server 2008 R2. You no longer have to work iscsicli.exe magic to connect to your SAN; you can click your way through now! Of course, for die hard command line freaks and scripters of all sorts the iscsicli.exe command is still available!

Starting the graphical iSCSI client configuration

The graphical version of the iSCSI client configuration tool can be started by typing:

iscsicpl

Below is a screenshot of a Hyper-V server 2008 R2 installation running the graphical version of the iSCSI Client:

Although the name implies otherwise this is not a Control Panel applet like timedate.cpl and intl.cpl. Trying to start the graphical version of the iSCSI Client using control iscsicpl will not result in a running instance.

Managing the Microsoft iSCSI service

For proper operation the Microsoft iSCSI Initiator service should be running. When the service is not running you will be asked whether you want to service to be automatically be started every time the computer starts:

You can also achieve the services starts by typing the following two commands:

sc config MSiSCSI start= auto
net start MSiSCSI

Concluding

Some configuration tasks can be tricky on a GUI-less server. In Hyper-V Server 2008 and Server Core installations of Windows Server 2008 a couple of graphical windows were present. These allowed to configure Regional options and Time and Data options.

In Hyper-V Server 2008 Microsoft included the graphical iSCSI Client. It’s a good thing Microsoft has included some more graphical tools to achieve tasks in the 2008 R2 Wave of products more easily.

Related posts

The Hyper-V Server 2008 R2 Surprise

Further reading

Server Core Cluster - how it’s done
TechEd Barcelona - the end
Clustering Videos on the Web
Microsoft iSCSI Software Initiator User's Guide 2.x
iSCSI Configuration UI included in Hyper-V 2008 R2
iSCSI Configuration UI included in Hyper-V 2008 R2
Building a Failover Cluster with Server Core Part 2
Step-by-step: Using the Microsoft iSCSI Software Target with Hyper-V
Microsoft TechNet Forums - Configuring iSCSI initiator using iscsicli.exe
Microsoft TechNet Forums - Configuring iSCSI using iscsicli.exe
Microsoft TechNet Forums - How to identify source NICs to be passed via iSCSIcli?
Microsoft TechNet Forums - Building a Host Cluster with Hyper-V in core mode
Microsoft TechNet Forums - ISCSI help. I need white papers
Microsoft TechNet Forums - Server Core and iSCSI initiator

-------------------------------------------------------------------------------------------------------------------

Connect NAS iSCSI to Hyper-V server

John's blogs are more related to using Hyper-V management tool on another computer to manage Hyper-V.

You can try the following steps:

1. Join both the Server Core machine and the machine on which you run the Disk Management console into Active Directory domain.

2. Make sure the user account which you are using to log on to the remote management machine has been added to the local Administrators group on the Server Core.

3. On the Server Core, run the following command:

Netsh advfirewall firewall set rule group="remote volume management" new enable=yes

4. On the Server Core, check if the Virtual Disk service has been started. If not, run the following command to start it:

Net start vds

5. On the remote management machine, open the MMC snap-in. Add a new snap-in of the Disk Management and point it to the Server Core.

For more details, please refer to the following blog article:

http://blogs.technet.com/server_core/archive/2008/01/14/configuring-the-firewall-for-remote-management-of-a-workgroup-server-core-installation.aspx