tempory second domain controller in network

I'm going to replace a server in our network. I need to copy all data, so I
want to connect the new server to my network while the old server is also
running.
Is it a problem to have tempory 2 domaincontrollers in a network.

I don't want to degrade my old server. It must stay a DC after a disconnect
it from this network.

Kees

In news:(E-Mail Removed),
Keesb <(E-Mail Removed)> typed:
> I'm going to replace a server in our network. I need to copy all
> data, so I want to connect the new server to my network while the old
> server is also running.
> Is it a problem to have tempory 2 domaincontrollers in a network.
>
> I don't want to degrade my old server. It must stay a DC after a
> disconnect it from this network.
>
> Kees

You can have many DCs on the same network. Make this new one a DC and
AD-integrated DNS server (prolly) and a GC (definitely) and make sure it's
working properly. Copy your data over.
Presuming the 'old' box was the first one on the network, you can either
transfer the FSMO roles to the new server (I would) or disconnect the old
server entirely and seize the FSMO roles *from* the new server.

In news:(E-Mail Removed),
Keesb <(E-Mail Removed)> typed:
> I'm going to replace a server in our network. I need to copy all
> data, so I want to connect the new server to my network while the old
> server is also running.
> Is it a problem to have tempory 2 domaincontrollers in a network.
>
> I don't want to degrade my old server. It must stay a DC after a
> disconnect it from this network.
>
> Kees

You say "replace" and then you mention "it must stay a DC". What exactly is
it you're trying to do?

You can definitely have more than one DC in a domain. In fact, it's
recommended.

Basics:
Install W2003, DNS, then dcpromo the box to a domain controller, transfer
FSMO roles & make it a GC, and you're fine.