How to change domains for a SQL Server 2000 failover cluster (319016)

SUMMARY

This step-by-step article describes the steps you must use to change domains for an existing SQL Server 2000 Failover Cluster.

Important Before you change the Cluster Domain, take the SQL Server resource offline by using the Cluster Administrator. After you take the SQL Server resource offline, you are ready to move the cluster to a new domain by using the guidelines in the following Microsoft Knowledge Base Article: If you have other clustered servers, you must determine what requirements they have before you move the cluster.

back to the top

Step 1: SQL Server 2000 Setup Program

After you move the Microsoft Cluster Server (MSCS) to the new domain, start the SQL Server 2000 Setup program.

1. In the SQL Server Introduction dialog box, click Next.
2. In the text box that is located on the Computer Name dialog box, type the virtual server name of the Virtual SQL Server you are moving to a new domain. If you have multiple servers, decide which server you want to move first. Click to select the Virtual Server option, and then click Next.
3. In the Installation Selection dialog box, click to select Advanced Options, and then click Next.
4. In the Advanced Options dialog box, Maintain a Virtual Server for Failover Clustering is selected. Click Next.
5. In the Failover Clustering dialog box, click to select the existing IP address. Make sure that the IP address you select is the old one, and then click Remove.
6. In the IP address: text box, type the new IP address for the new domain, and then click Add. Click Next.
   
   Important If your domain move does not require you to change the IP address of the server, you do not have to remove and re-add the current address. Just click Next.
7. Unless you have to modify the Cluster Definition, click Next.
8. In the input text boxes, type the new:
   • User Name
   • Password
   • Domain Name
9. Click Next.
10. Click Finish.

back to the top

Step 2: Cluster Administrator

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

1. Start the Cluster Administrator.
2. Verify that the Virtual SQL Server you reconfigured in step 1 contains only one SQL Server IP Address resource, if the group contains more than one resource:
   1. Verify the resource properties of each IP Address resource.
   2. Delete the resource that is configured for the OLD IP Address.
      
      
      
   3. Run regedt32, do not use regedit, and then navigate to this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster for a default Virtual SQL Server HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\%Instance Name%\Cluster for a Virtual SQL Server with a named instance where %Instance Name% would be the name of the instance being modified.
   4. Modify the ClusterIPAddr value to only contain the current valid IP Address for the Virtual SQL Server
3. While SQL Server 2000 Virtual Server is offline use the Control Panel applet to change the virtual SQL Servers startup accounts to the new domain account for the SQL Server and SQL Agent.
   
   Note Create the SQL Server startup accounts. Make sure that you add the appropriate permissions and user rights to the SQL Server startup accounts. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

   283811 How to change the SQL Server or SQL Server Agent Service account without using SQL Enterprise Manager in SQL Server 2000

4. Bring the Virtual SQL Server you reconfigured in step 1 online.
5. Repeat step 1 and step 2 for any other Virtual SQL Servers that are installed on the cluster.

back to the top