Q: I need to move the
domain controller from one windows 2003 server to another. My plan is as
follows:
1. Install the new server as a domain controller following the
recommendations in the following article: "Installing a Domain Controller
in an Existing Domain Using Restored Backup Media" -- http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Operations/5870556f-be04-4345-acb8-60c6c540f690.mspx
1.1 Backup the system state on current DC
1.2 Restore the backed up file on the new server at an alternate location
1.3 Install Active Directory and direct it to use the restored System
State data at the alternate location
1.4 In the active directory wizard make it a global catalog server
2. Demote the old
domain controller and leave the new one serving the DC
My question is -- does my DC restore procedure give the new domain
controller a capability to become the primary controller in the domain? In
other words, would my plan work? I would appreciate any additional
comments or advise.
A:
The way I usually do
this is by simply installing new hardware (don't forget
to include all the latest patches and updates). Now join it to domain and
run
dcpromo
on the server. This will make it a second domain controller in your
environment.
Now what you have to do is:
- move FSMO roles to new serve
- replicate DNS to new server
- click the checkbox so that new server becomes GC.
Pay attention to DNS services. Since IP of DNS server will change, don't
forget to change client's TCP/IP configuration to reflect this change
(preferred DNS server).
Personally I think this is simpler way of getting new DC into environment.
It takes less then half a day.
Note: it is not recommended to have only one domain controller at the time
(you should have at least two).
Note: there are no primary domain controllers since Windows 2000 Active
Directory. All domain controllers are equal (the only exceptions are servers
holding FSMO roles). How to make your new server a FSMO holder is described
above.
Once you have done this, shutdown your old server and see if everything
works (users can logon to their computers and can access file servers
(shares))... If everything works, start the old server up and run dcpromo on
it to remove it from domain.
Can't Add Windows 2000 Computer to
Domain: The Network Path Was Not Found ... How to access
different domain without changing the network settings ... www.chicagotech.net/domainfaqs.htm
A domain controller for the
domain could not be contacted · DNS name does not exist, error
code 0x0000232B RCODE_NAME_ERROR ... www.chicagotech.net/casestudy/adcases.htm
How do I un-synchronize time on my
domain network? Q: I have an isolated Windows 2000/NT domain
for I/O testing. I want to change TIME on one of my W2K ... www.howtonetworking.com/server/domain.htm
-
Similar pages
"The DNS SRV records required to
locate a domain controller for the domain are ...
Situation: The client has a domain network and DC, DNS and
DHCP is on a ... www.howtonetworking.com/casestudy/cannotjoindomain1.htm
-
Similar pages
In this case, you may want to use
nbtstat -c command to find the NetBIOS domain name which
displays like this <DOMAIN><1B>. <DOMAIN><1B>is used
to identify ... www.howtonetworking.com/Windows/domainname1.htm
-
Similar pages
How to promote and demote domain
controllers in Windows 2000 This article describes how to promote or
demote a domain controller to a stand-alone server in ... www.howtonetworking.com/articles/dchowto.htm
-
Similar pages
How to add a Windows Server 2003 to a
Windows 2000 domain. Before adding a Windows Server 2003 to a
Windows Server 2000 domain, make sure you have correct ... www.howtonetworking.com/casestudy/adddc1.htm
