GD Bloggers

This is the blog site for Microsoft Global Delivery Communities focused in sharing the technical knowledge about devices, apps and cloud.
Follow Us On Twitter! Subscribe To Our Blog! Contact Us

Prepare SharePoint Farm – Part 1 Prepare Windows Cluster

Prepare SharePoint Farm – Part 1 Prepare Windows Cluster

  • Comments 4
  • Likes

This part demonstrate how to configure windows cluster for two server, to be used as SQL Cluster. 


Before you start

· You need to have two network adapters on each node, one Public and one Private(for heartbeat communication).

· Shared storage (like SAN storage) should be present and connected to both cluster nodes  with at least:

    • Quorum Disk (5GB)
    • DTC Disk (1GB)
    • SQL data files and log file disk(s)

· domain user account (SPSadmin): add SPSadmin user as administrator on both servers

· Prepare a preserved static IP and Cluster Name to be used.

· Prepare a preserved static IP and DTC Name to be used.


Windows Cluster Configuration

1. Install latest windows updates on all server nodes.

2. Install Application role and IIS role on both SQL DB server nodes


3. Install Fail over clustering feature on both SQL DB server nodes.


4. Provide a Cluster Name and Cluster IP for the database nodes:


Note: make sure that the public network is used here not the private (heartbeat)

5. Below are the servers info


6. Cluster Disk files are configured as the following:


7. Configure DTC as clustered service , this is a pre requisite for SQL Cluster installation


8. DTC cluster configuration


9. Assign the DTC a cluster disk


10. Create SQL Group which is a logical group to include all SQL resources in :




Part 2 - Install and configure SQL Cluster

Part 3 - Install and Configure NLB on WFE

part 4 - Install and configure SharePoint farm (3-tier)


  • You dont need IIS role on the sql db nodes!

  • iIS for SQL reporting services.. If you wish to install SQL reporting on different servers then correct you dont need IIS role here .. It depends on your deployment topology

  • Is the FileServices role necessary to be installed and running on the SQL DB server? I am getting the following error:

    File Server Resource Manager Service error: Unexpected error.

    Error-specific details:

      Error: GetVolumeNameForVolumeMountPoint, 0x80071126, The file or directory is not a reparse point

    Event ID:      8197

    Have been searching around but can't find a solution, so I am thinking of removing the FileServices role on the SQL DB server.

  • No you dont need file services, you can remove this role

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment