Building a Failover Cluster with Server Core Part 1

During the Dutch Launch event I presented about Windows Failover clustering and I also prepared some demo's. I
build a failover cluster on top of a Server Core. In Part I will briefl! e"plain the s!sprep process because I had to
rebuild all m! #$ with the %&$ version of Windows Server '(().
So first I wanted to create a new set of base vhd's which I will use to install all m! #$'s from* this ma+es the install
process much faster.
I started with the installation of a Windows Server '(() ,, to create m! first base vhd. -fter the installation I added
a few tools* changed some registr! +e!s to ma+e sure some of the tools are running when logging into the bo".
.ow with Windows Server '(() the S!sprep tool is included within the S!stem/' director!. &o s!sprep !ou're
machine !ou need to run the s!sprep tool and select the following options0
-fter the s!sprep process is done the #$ will shutdown automaticall!. .ow +eep this #1D as a base for all !our
new #irtual $achines.
In m! case I needed to start with the installation of a DC and I've used the #1D 2ase* this is what !ou will see when
!ou boot a s!sprepped vhd file0
Select the correct regional settings.
Fill in the product +e!.
Fill in the server name and clic+ start to configure the server* after a while !ou will need to change the password of
the local -dministrator account.
&he server is now read! to be configured* in m! case I will configure the networ+ing and add the -ctive Director!
Domain Services role and finali3e with a dcpromo.
&he ne"t step in this little pro4ect is to install two Windows Server '(() ,nterprise ,ditions 5 Server Core. I also
created a base vhd for this and used them to create SCCL6( and SCL6('.
7nce the base 7S is installed I've configured the server as described in one of m! previous posts * in Part ' I will
e"plain how to configure the iSCSI shared storage and assign it to a server core. In part ' I will install the cluster
and configure a high available file sharing infrastructure

.ote0 &his is one wa! how to create !our base #1D's another option is to use those base #1D files and create
differencing dis+s pointing to the base vhd for each additional #$ !ou need in !our environment.
Building a Failover Cluster with Server Core Part 2
In m! previous post I've tal+ed about how to use base images to 8uic+l! deplo! new servers in m! 1!per5#
environment. In this post we will configure the shared storage based on the microsoft iSCSI target software* in a real
life environment !ou could use either a Windows Storage Server or another iSCSI or FC based storage environment.
2efore actuall! digging into the failover clustering installation I want to briefl! e"plain what I have setup so far to
be able to build a cluster in the first place.
First I have created a Domain Controller and installed the iSCSI target software to be able to emulate a shared
storage environment. I've created two dis+s one which is (($2 in si3e and will be used as a witness dis+ 9used to
be called :uorum dis+; and I have a second dis+ which is is <2 of si3e and will be used as a data dis+.
Secondl! I have installed two Server Core machines and added the to the domain 9read Configuring Windows
Server 2008 Server Core or use the Coreconfigurator tool;. $a+e sure !our Server core machines have at least
two networ+ cards* one for the normal traffic and one for the cluster heartbeat. -fter having configured all basic
things we are now read! to start with the installation and configuration of the clustering software.
Let's do this step b! step0
Step 0 Install the Failover Cluster role
$a+e sure !ou do this on both Server Core machines
Step '0 Configure and Start the iSCSI initiator service
-gain perform this on both machines. .ow the $icrosoft iSCSI initiator service is configured and will start up
during boot time.
Step /0 Connecting the Server Core bo"es to the iSCSI storage bo"
1ere are all steps !ou should ta+e on both Server Core bo"es to connect to the storage.
. iSCSIcli :-dd&argetPortal =Storage 2o"* Portal IP -ddress>
%e8uired to refresh the new target built*
'. iSCSIcli List&argets
?ou should see the i:. of the target created
/. iSCSIcli :login&arget =&arget I:.>
?ou should see a connection and session id
@. iSCSIcli PersistentLogin&arget =targetAi8n> & B B B B B B B B B B B B B B B (
.7&,0 &here are C DspaceE F DBE
?ou do this so !ou can survive a reboot
C. iSCSIcli ListPersistent&argets
?ou should see a target
G. iSCSIcli %eport&arget$appings
?ou should see the target and a L6. " mapping for ever! L6. defined in the target
-t this stage !ou have assigned both dis+s to the server core machines the ne"t step will be to configure the dis+s
Step @0 Configuring the clustered dis+s
2! being <6I less !ou need to do this onto the command line.
First list the dis+s in !our bo"es b! using the dis+part commandline tool0
diskpart
list dis+ 9this will return the dis+s available in !our s!stem in m! case I had dis+ (* and ' with ( being m! 7S dis+
and the other two the dis+s for m! cluster;
select disk 1
attribute disk clear readonl
online disk
create part pri!ar
select part 1
assign letter"#
select disk 2
attribute disk clear readonl
online disk
create part pri!ar
select part 1
assign letter"S
e$it
Format each dis+ b! t!ping format "0 H8 where I is !our drive letter and don't provide an! label name.
&he servers are now completel! configured to form a Windows Failover Cluster* this process will be e"plained in
Part III of this post.
Building a Failover Cluster with Server Core Part %
In the two previous parts of this topic we created the Server Core $achines* connected them to the storage and
added the Failover Clustering Feature. In this last part we are going to configure the Windows Failover Clustering
feature and form a ' .ode cluster. For doing this !ou have two options one is using the cluster.e"e command line
tool and do ever!thing from the command line or b! using the %S-& tools and remotel! create the cluster. I've
chosen for the second and easiest option.
Step 0 7pen Failover Cluster $anagement Console and #alidate the configuration
In m! case I will open up the mmc from m! Domain Controller but with the %S-& tools !ou can now also remotel!
manage failover clusters from an Windows #ista SP bo".
&he first action that needs to be performed prior building the cluster is running the validation tool. &his is not needed
for a test environment but if !ou want to get support from $icrosoft !ou need to run this and +eep the report* !ou
also need to run the validation tool each time !ou ma+e changes to the cluster infrastructure* changes li+e adding an
12- re8uires a new validation report.
&he #alidation tool will run tests to determine whether !our s!stem* storage* and networ+ configuration is suitable
for a cluster. &hese tests include specific simulations of cluster actions* and fall into the following categories0
S!stem Configuration tests* .etwor+ tests and Storage tests.
Clic+ on &'alidate a Configuration& in the action pane.

-dd both nodes to be validated.
%un the tests needed for support and to +now if the cluster config is correct.
-fter all tests have completed !ou will be able to review the report b! clic+ing onto the report button or if !ou want
to open it afterwards we store all reports in the following director!0 Jc0KwindowsKclusterKreportsJ
If the validation tool completes successfull! then !ou can go on with the creation of the cluster. Let's assume
ever!thing is fine and perform the actual cluster creation wi3ard.

Fill in all nodes that will be part of this cluster* this is a huge difference comparing to Windows Server '((/
clustering because now the setup wi3ard is going to configure all nodes at once.
<ive !our cluster a name and IP -ddress in m! case I onl! selected the L'.G).(.(H'@ networ+ because that's m!
public L-. and the second networ+ is onl! used for heartbeat configuration.

-fter this step the setup tool is going to create the cluster and ma+ing configuration changes on both server core
nodes to form a cluster.
&he cluster is now read!.
&he ne"t step !ou need to perform is that the correct Witness dis+ has been used in m! configuration it was not the
case and I had to change Witness dis+ config.
?ou can do that as follows0
In the action pane clic+ on more action and then select the JConfigure Cluster :uorum SettingsJ as can be seen in
the picture below.
In the following Wi3ard !ou are able to change the :uorum configuration model or change the details of the current
:uorum.
In m! case I 4ust clic+ed on ne"t and in the screen that follows !ou will be able to change the dis+ configuration of
the Witness dis+.
&hat is what I've done and now m! cluster is up and running and I can start clustering Services or -pplications
I hope that these three blogposts will help !ou to create a Windows Failover Cluster on a Server Core.