Change Domains

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Harvey Hall - 02 Dec 2004 23:05 GMT

I need to move a Win2k/SQL2k 2-node cluster to another Domain. I'm
considering two alternatives: (a) a node by node rebuild to a Win2k3/SQL2k
cluster in the new Domain, and (b) migrating MSCS to the new domain per
kb26196: "How to Move a Windows Cluster Server from one domain to another",
and then using SQL Server's Setup program, Cluster Administrator, and
regedt32 to migrate the instances to the new domain, per per kb319016: "How
To: Change Doamins for a SQL Server 2000 Failover Cluster". Any advice?

Reply to this Message

Rodney R. Fournier [MVP] - 03 Dec 2004 03:08 GMT

I had to do this recently. I start from scratch and then attached the
databases. Worked great.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog

>I need to move a Win2k/SQL2k 2-node cluster to another Domain. I'm
> considering two alternatives: (a) a node by node rebuild to a Win2k3/SQL2k
[quoted text clipped - 5 lines]
> "How
> To: Change Doamins for a SQL Server 2000 Failover Cluster". Any advice?

Reply to this Message

Harvey Hall - 03 Dec 2004 17:19 GMT

Thanks for your response. Glad to hear that "from scratch" works well. Do you
have any thoughts about what I call plan (b) below, that is:

(b) migrating MSCS to the new domain per kb26196: "How to Move a Windows
Cluster Server from one domain to another", and then using SQL Server's Setup
program, Cluster Administrator, and regedt32 to migrate the instances to the
new domain, per kb319016: "How To: Change Domains for a SQL Server 2000
Failover Cluster"

Would you recommend one approach over another?

I need to move a Win2k/SQL2k 2-node cluster to another Domain. I'm
considering two alternatives: (a) a node by node rebuild to a Win2k3/SQL2k
cluster in the new Domain, and (b) migrating MSCS to the new domain per
kb26196: "How to Move a Windows Cluster Server from one domain to another",
and then using SQL Server's Setup program, Cluster Administrator, and
regedt32 to migrate the instances to the new domain, per per kb319016: "How
To: Change Doamins for a SQL Server 2000 Failover Cluster". Any advice?

Reply to this Message

Shashank Pawar [MSFT] - 24 Jan 2005 23:49 GMT

Hello Harvey,

With regards to the options I would utilise the option of building from
scratch if this option is available to you as this will gurantee you that
setup is clean, whereas with the migration option using the KB artilces you
have specified you can run into issues which can be caused by objects not
being created during the migration, etc; service account issues, etc.
However the KB articles are tested and proven to work but as is with most
cases if you can start from scratch its always better, especially in a
cluster environment where you want to gurantee a clean environment for high
availability and ease of troubleshooting.

Regards,

Shashank Pawar
SQL Server Support Engineer, Microsoft

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

| Thread-Topic: Change Domains
| thread-index: AcTZXDH2uVyKQNVbSwSq4yvHs8qoUw==
| X-WBNR-Posting-Host: 69.89.128.5
| From: "=?Utf-8?B?SGFydmV5IEhhbGw=?="

<HarveyHall@discussions.microsoft.com>

| References: <F21C09DF-36F2-4AF4-B50A-B71D9ACDDBDF@microsoft.com>
| Subject: RE: Change Domains
[quoted text clipped - 13 lines]
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path:

cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA
03.phx.gbl

| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.clustering:15918
| X-Tomcat-NG: microsoft.public.sqlserver.clustering
[quoted text clipped - 17 lines]
| regedt32 to migrate the instances to the new domain, per per kb319016: "How
| To: Change Doamins for a SQL Server 2000 Failover Cluster". Any advice?

Reply to this Message