Clustering Is getting to easy more and more is clustering needed and yes sometimes it is hard. Like the SQL 2014 installation build a cluster in less than 5 minutes 
Let me describe the easy steps and get a full blown classic SQL server 2014 on windows server 2012R2
I use always the advance option this is much easier than you think and if something goes wrong you have to do just one step to renew not the whole setup.
This will do only Step 1 Advanced Cluster Preparation ( this will take about 3 minutes to install )
d:setup.exe /qs /CONFIGURATIONFILE="SQL2014-cluster-step1.ini" /AGTSVCPASSWORD="Password01" /ASSVCPASSWORD="Password01" /SQLSVCPASSWORD="Password01" /ISSVCPASSWORD="Password01" /RSSVCPASSWORD="Password01" /IACCEPTSQLSERVERLICENSETERMS /INDICATEPROGRESS
next step Advanced Cluster Completion ( this will take about 3 minutes to install )
d:setup.exe /qs /CONFIGURATIONFILE="SQL2014-cluster-step2.ini" /IACCEPTSQLSERVERLICENSETERMS /INDICATEPROGRESS
I See you thinking how to get the INI files, easy just do once the Setup and follow the wizard and just before starting the installation “ready to install” there is the ini line
If you installed it in the default path on the C drive and the number can be different !
C:Program FilesMicrosoft SQL Server110Setup BootstrapLog
If you use my line then quote out the ;UIMODE="Normal" can’t use silent and Gui in normal mode
; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block.
;UIMODE="Normal"
Adding the Cluster
d:setup.exe /qs /CONFIGURATIONFILE="SQL2014-addcluster-step3.ini" /AGTSVCPASSWORD="Password01" /ASSVCPASSWORD="Password01" /SQLSVCPASSWORD="Password01" /IACCEPTSQLSERVERLICENSETERMS /INDICATEPROGRESS
Pause
But the best part is here SQL now support CVS
SQL Server 2014 is that you can now use a Cluster Shared Volume (CSV) in addition to the other methods you already could use for database and backup storage (drive letter, mount point, SMB share, local tempdb – the last two were introduced in SQL Server 2012). The big benefit here is that if one node of the SQL Server cluster loses connectivity to the storage, it can still read and write data over the network to a different node’s SAN connection.
just replacing the value in the ini file with the cluster storage volume or storage pool
; The Database Engine root data directory.
INSTALLSQLDATADIR="C:ClusterStorageVolume1"
; The Database Engine root data directory.
INSTALLSQLDATADIR="E:"
More about this in my next blogs.
Get the ini files here http://sdrv.ms/12dqaya
