migrating the domain controller

Hello,

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/pro...6c540f690.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.

Thanks a lot,
Minas.

Hi,

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.

Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller
http://support.microsoft.com/kb/255504

How to view and transfer FSMO roles in Windows Server 2003
http://support.microsoft.com/?id=324801

How To Create or Move a Global Catalog in Windows 2000 (it is same on
Windows 2003)
http://support.microsoft.com/?kbid=313994

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.

--
Mike
Microsoft MVP - Windows Security

"Minas Hambardzumyan" <(E-Mail Removed)> wrote in message
news:movxf.19882$ya4.3376@trnddc03...
> Hello,
>
> 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/pro...6c540f690.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.
>
> Thanks a lot,
> Minas.
>
>
>