Re: Changing Windows Domain

Great news; thanks. Like you said, the account is already in Administrators
so that's already done.

"Rodney R. Fournier [MVP]" wrote:

> I just did this last night for a customer. If you are already using the new
> domain's service account, it's pretty easy. I take it your cluster & SQL
> service accounts are already in the local administrators group on each node.
> Take all cluster groups offline. Join one node at a time to the new domain,
> reboot, when both are back up in and in the new domain start the groups.
>
> Cheers,
>
> Rod
>
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> http://msmvps.com/clustering/archive/2005/07/20/58233.aspx NYC Clustering
> class
>
> "CarolinaKB" <CarolinaKB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:CB00A57B-A0E5-450D-9C83-9818B7883595@xxxxxxxxxxxxxxxx
> >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
    ... are you saying to not start SQL through the Services applet as ... opposed to starting it through Cluster Administrator after completing the ... Make sure the service accounts have the ... >> Windows 2003 Active Directory Domain. ...
    (microsoft.public.sqlserver.clustering)
  • Changing Windows Domain
    ... Windows 2003 Active Directory Domain. ... All user and service accounts ... (including SQLServer and SQLServer Agent accounts) ...
    (microsoft.public.sqlserver.clustering)
  • Re: Sql server 2005 clustered service group
    ... I always do this as part of cluster setup (prepoulate the groups with the ... Jasper Smith (SQL Server MVP) ... add accounts to the domain groups. ... needs rights to add the service accounts to the domain group ...
    (microsoft.public.sqlserver.setup)
  • RE: Cluster Service account and domain Migration
    ... How to move a cluster from one Windows 2000 domain to another Windows 2000 ... You'd better rebuild the cluster. ... It is originally for Windows NT 4 cluster server. ... > Identify Service accounts (here is where I find my cluster service ...
    (microsoft.public.windows.server.migration)
  • Re: Cluster File Share cannot be accessed by account on trusted domain
    ... cluster nodes into the new OU and select "Block Policy Inheritance" on the ... Windows NT/2000/2003 Cluster Technologies ... > accounts from a trusted domain in the same forest as the ...
    (microsoft.public.windows.server.clustering)