Hi all,

Just a little history. We have two domain controllers with DNS, DHCP and
WINS configured (Windows 2k/2003 domain), one in the main office and one in a
remote office.

We wanted to remove the DC from the remote office, a 2000 server and replace
it with a new 2003 server.

We simply took the remote 2000 server off the network and put the new 2003
server on the network and renamed it to the old 2000 server name as well as
changed the IP address of the 2003 server to the old 2000 server IP. We would
then configure DNS, DHCP and WINS.

Due to time constraints, we had to back out, and go back to the original
configurations. Ooops. I think that may have confused our AD database. Now
the remote DC doesn’t show up under “Users and Computers� although it is
actively functioning, remote users don’t show up in our browser list while if
we remote into a remote office workstation, they are in the browser list
there and I imagine there may be other issues yet unknown.

Our logic to this approach was to treat the swap as if the remote DC died
and we wanted to physically replace it and use the old servers IP and machine
name.

I didn’t find any KB or TechNet articles that address this issue.

Any thoughts, articles or ideas would be appreciated. We still need to
replace the remote server but don’t want to create more problems than we
already have.

Many thanks,
Gene

You've enabled NetBIOS over TCP/IP on the new server?
It is supposed to be a DC as well? If so I would introduce
the new server with a different name then setup all services
and remove the old server then rename this paticular server
to match the old server. Although the way you've done it
should work assuming you removed the computer account
from the AD then recreated the computer account when you
join the new server to your domain.

"Gene" <Gene@discussions.microsoft.com> wrote in message news:

Well I would have demoted the old dc first so that active directory was
updated properly and then either reset or remove that computer account. Next
you could have brought the new computer up, renamed it and then promoted it
a dc. How did you handle the dhcp leases that existed on the old dc? Is not
clear to me what condition your active directory is in? I would consider
bringing up the 2003 server with a new computer name and then promote it to
a dc. Next I would find some articles on how to manually remove a dc from
active directory that hasn't been demoted properly.

"Michael Giorgio - MS MVP" <Michael.Giorgio@NoSpam.mayerson.com> wrote in
message news:uclVZ0OUFHA.1432@TK2MSFTNGP09.phx.gbl...