If you read Part 1 and are following along, you should have your cluster running and Virtual Server 200 R2 installed. Part 2 will cover the creation of a virtual machine on the clustered host(s). With the Virtual Server cluster running, let's install the first virtual machine and try out a failover scenario!

To begin, open up the Virtual Server Administration web page on the active node. The first thing we need to do is create a new Virtual Network, let's call it PublicNet. Now before we go any further we need to perform a little trickery. The VNC file, the file containing the configuration of the virtual network we just created, is typically located in C:\Documents and Settings\All Users\Documents\Shared Virtual Networks\VirtualNetworkName.vnc This is not on the shared storage so it won't be available to node 2 in the event of a failover. To fix this we need to copy the VNC file from C:\Documents and Settings\All Users\Documents\Shared Virtual Networks\ and paste it in the shared storage drive. Next delete the PublicNet virtual network from the Virtual Server Administration web page. Finally select Add under Virtual Networks and enter the path to the existing configuration file.

With that complete you should see the virtual network pointing to the VNC file on the shared storage.

The rest of the virtual machine configuration is straight forward. Create the VHD on the shared storage device and choose the PublicNet for the virtual machines network connection. Once done there are a few last steps to configure so that failover will work! Open up the Cluster Administrator and move ResGroup1 to the passive node and then open up the Virtual Server Administration web page on the passive node and add the PublicNet virtual network using the existing PublicNet VNC file we placed on the shared storage device.

All that is left now is to configure the Havm.vbs script. Open up Cluster Administrator and create a new script resource called ResScript1. Configure it as a generic script resource assigned to ResGroup1 with both nodes as possilble owners. Make ResDisk1 a dependancy and enter the path to Havm.vbs. Before bringing ResScript1 online, run the following command

cluster res "ResScript1" /priv VirtualMachineName=GuestMachineName

Bring the script resource online and return ResGroup1 to the active node and put it online. You can now install an OS on the virtual machine. Wanna give it a shot? Open up Cluster Administrator and move ResGroup1 to the other node and watch the Owner change to the other nodes name!