Setup Cluster Bindings

Previous Setup SSIS Cluster	Manual Install	Post-Install Reboot Next

FineBuild performs a number of post-install tasks on a cluster in order to make it more manageable.

FineBuild Setup Cluster Bindings Processing

Automated Setup Cluster Bindings processing is performed by Process Id 2CAM and will always be performed for a Cluster install.

The FineBuild Setup Cluster Bindings processing includes the following items:

• Active Directory Automatic Maintenance
• Cluster Node Management
• Add Node to SSAS Cluster
• Set MSDTC Preferred Owner Node
• Remove NTLMSSP Dependency for SQL 2005

FineBuild also uses the following parameter to help configure Cluster Bindings:

Parameter	Description
/PreferredOwner:	Preferred owner node for the SQL Server Clusters

Top

---

Manual Setup Cluster Bindings

The following steps show what you would have to do to setup Cluster Bindings manually. FineBuild does all of this work for you automatically.

Active Directory Automatic Maintenance

1. Configure tidying of Active Directory Computer objects when Cluster Names deleted.

   Run the following command, replacing Cluster Name with the name of your cluster:

   CLUSTER "Cluster Name" RESTYPE "Network Name" /PRIV DeleteVcoOnResCleanup=1
   

Cluster Node Management

Perform the following process for both the SQL Server DB Cluster and the Analysis Services Cluster Groups.

This processing should only be done for the initial node of the cluster.

1. Configure automatic update of DNS records on Cluster failover.

   Run the following commands:

   CLUSTER "Cluster Name" RESOURCE "SQL Network Name (Cluster Group)" /OFF
   CLUSTER "Cluster Name" RESOURCE "SQL Network Name (Cluster Group)" /PRIV RequireDNS=1
   

2. Allow use of Kerberos security for the cluster name.

   Run the following commands:

   CLUSTER "Cluster Name" RESOURCE "SQL Network Name (Cluster Group)" /PRIV RequireKerberos=1
   

3. Setup Drive Dependencies

   The Microsoft SQL Server Cluster install does not always set dependencies for all the drives used by the SQL Server cluster. This processing is done by FineBuild.

   Run the following command for every drive used by the SQL Server Cluster Group:

   CLUSTER "Cluster Name" RESOURCE "Cluster Group" /ADDDEP:"Volume Label"
   

4. Bind SQL Cluster to MSDTC

   If you are installing on Windows 2008 or above, the SQL Server Cluster Groups should be bound to the appropriate MSDTC Cluster.

   Run the following command:

   MSDTC -tmMappingSet -name "Cluster Group" -service "SQL Instance Name" -ClusterResourceName "MSDTC Cluster Group"
   

5. Set Preferred Owner Node

   FineBuild can set the Preferred Owner node for a Cluster Group and put the Cluster Group online to that node.

   When the install is run on the preferred owner node, run the following commands:

   CLUSTER "Cluster Name" GROUP "Cluster Group" /SETOWNERS:"PreferredOwner"
   CLUSTER "Cluster Name" GROUP "Cluster Group" /MOVETO:"PreferredOwner"
   

Add Node to SSAS Cluster

The Microsoft SSAS Cluster install processing does not add additional nodes as a possible owner of the SSAS Cluster Network Name. This prevents the SSAS Cluster from performing a Failover.

This processing should therefore be done for every node that is added to the Analysis Services Cluster.

1. Run the following commands:

   CLUSTER "Cluster Name" RESOURCE "SQL Network Name (SSAS Cluster Group)" /OFF
   CLUSTER "Cluster Name" RESOURCE "SQL Network Name (SSAS Cluster Group)" /ADDOWNER:"Server"
   CLUSTER "Cluster Name" RESOURCE "SQL IP Address 1 (SSAS Cluster Group)" /ADDOWNER:"Server"
   

Set MSDTC Preferred Owner Node

If you are installing on Windows 2008 or above and are using the FineBuild default of creating a MSDTC cluster for each server node, then the MSDTC cluster can be assigned to a preferred owner node.

1. When the install is run on the preferred owner node, run the following commands:

   CLUSTER "Cluster Name" GROUP "MSDTC Cluster Group" /SETOWNERS:"PreferredOwner"
   CLUSTER "Cluster Name" GROUP "MSDTC Cluster Group" /MOVETO:"PreferredOwner"
   

Remove NTLMSSP Dependency for SQL 2005

SQL Server 2005 Full Text service depends on the NTLMSSP service, which does not exist in Windows 2008 and above. Installation of SQL 2005 Service Pack 2 or above should remove the dependency, but there are many reports that this does not always happen. This dependency should be removed.

1. Start REGEDIT and navigate to the registry key below:

   HKLM\SYSTEM\CurrentControlSet\Services\msftesql\DependOnService
   

2. Edit the DependOnService value and remove the entry for NTLMSSP

3. Close Regedit

Copyright FineBuild Team © 2012 - 2021. License and Acknowledgements

Previous Setup SSIS Cluster	Top	Post-Install Reboot Next