I am taking this post down because I have found a few articles that detail these steps rather thoroughly. I am going to refocus this series on virtualizing physical machines in order to run them in a Hyper-V Live Migration Cluster. The two specific challenges that I face are virtualizing Exchange and SQL Server. The main issue is that I have their database files stored on a SAN. I connect to the SAN via iSCSI connections. This can be accomplished in the Hyper-V environment, but it fails during a Live Migration. Obviously, this defeats one of the main reasons for virtualization.
The only alternative I see is to convert the data on the LUNs to a vhd, store the VHD in the Clustered Shared Volume (CSV), and connect through Hyper-V. There are obvious performance issues with this solution. This is going to be my focus for the next week or two at work and so I plan to use this series to document my testing and any issues I run into. I would like to reference two blogs that are very helpful in setting up the Hyper-V cluster. Therefore, part 2 and on will require a fully functional Hyper-V Failover Cluster.
The two blogs that I will recommend are Hyper-V R2 Live Migration and Creating a Hyper-V Failover Cluster