Changing Windows Domain

I have a 2 node Windows 2000 Active/Passive Cluster running SQL Server 2000
Enterprise Edition. The cluster supports a 24x365, mission critical
application.

The nodes are currently members of a Windows NT4 domain which trusts a
Windows 2003 Active Directory Domain. All user and service accounts
(including SQLServer and SQLServer Agent accounts) are "ADDomain" accounts.

I am planning on using the procedure described in KBs 269196 and 319016 to
move the cluster from "NT4Domain" to the trusted "ADDomain". The TCP/IP
names and addresses will not change, and to reiterate, the user and service
accounts are already logging into the trusted domain "ADDomain", not
"NT4Domain".

When I look at 319016, however, I get the impression that that KB was
written more to address a changed TCP/IP domain as opposed to a changed
Windows domain. My questions are:

1) Does 319016 even apply in this situation?

For example, step 1 of 319016 calls for a rerun of SQLServer setup. Since
1) the TCP/IP address is not changing and 2) the SQL service account is not
changing, do I need to perform step 1? I'm not sure what all setup might be
doing there.

Also, step 2 of 319016 calls for the new TCP/IP address to be entered for
each instance. Again, the IP address is not changing. As info, there is
only the default instance.

2) I think that I need to move both nodes into the new domain and restart
the cluster service on both (with SQLServer resources kept offline) before
any SQL changes. Is that correct?

3) Assuming there are no GP changes, are there other concerns I'm
overlooking? I saw a similar question in which the admin was leaning toward
rebuilding from scratch instead of moving the cluster. That seems like a lot
more work (rebuilding systems, cluster resources, and
reinstalling/configuring applications) than moving as described above.

Thanks for any feedback

.

Relevant Pages

  • Re: Changing Windows Domain
    ... I take it your cluster & SQL ... > service accounts are already in the local administrators group on each node. ... > MVP - Windows Server - Clustering ...
    (microsoft.public.sqlserver.clustering)
  • Re: Thinking of reinstalling Windows...
    ... Those accounts created have always been fully functional ... extensions that windows don't recognize. ... to double click and open them; I received the file type association dialogue ... Default user profile that all new user accounts copy off from. ...
    (microsoft.public.windowsxp.general)
  • Re: Thinking of reinstalling Windows...
    ... Those accounts created have always been fully functional ... | extensions that windows don't recognize. ... | to double click and open them; I received the file type association dialogue ... | Default user profile that all new user accounts copy off from. ...
    (microsoft.public.windowsxp.general)
  • From Tracker....
    ... Remember, we're talking about Windows Platforms 95,98 ... provided with Cable/DSL dial-up accounts. ... Wrong IP no news. ... We aren't talking about News Servers here (at the ...
    (microsoft.public.security)
  • From Tracker....
    ... Remember, we're talking about Windows Platforms 95,98 ... provided with Cable/DSL dial-up accounts. ... Wrong IP no news. ... We aren't talking about News Servers here (at the ...
    (microsoft.public.security.virus)