Replacing Domain Controller

Toggle sidebar Toggle sidebar
G

Gene

Distinguished
Apr 14, 2004
133
0
18,680
Archived from groups: microsoft.public.win2000.general (More info?)

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
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.general (More info?)

> 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.


Was the 2003 server installed while on the network and able to contact the
existing Win 2k server?


hth
DDS W 2k MVP MCSE

"Gene" <Gene@discussions.microsoft.com> wrote in message
news:24F251C3-88C7-40D9-BB7F-B484280D5DB6@microsoft.com...
> 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
>
 
G

Gene

Distinguished
Apr 14, 2004
133
0
18,680
Archived from groups: microsoft.public.win2000.general (More info?)

Yes, it had been online as a member server for a month or so.

"Danny Sanders" wrote:

> > 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.
>
>
> Was the 2003 server installed while on the network and able to contact the
> existing Win 2k server?
>
>
> hth
> DDS W 2k MVP MCSE
>
> "Gene" <Gene@discussions.microsoft.com> wrote in message
> news:24F251C3-88C7-40D9-BB7F-B484280D5DB6@microsoft.com...
> > 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
> >
>
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.general (More info?)

During the dcpromo process it MUST contact your existing Win 2k server in
order to replicate the SAM to the new server. If this does not happen the
new server will create a new SAM. As far as your clients are concerned new
SAM = new domain.


>> > 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.


This sounds like the remote site may be on a separate domain.

Did you run dcpromo on the Win 2k3 server to make it a DC while connected to
your existing network?

hth
DDS W 2k MVP MCSE




"Gene" <Gene@discussions.microsoft.com> wrote in message
news:10742AD7-7EB3-43CC-80DA-76D1F7A6524B@microsoft.com...
> Yes, it had been online as a member server for a month or so.
>
> "Danny Sanders" wrote:
>
>> > 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.
>>
>>
>> Was the 2003 server installed while on the network and able to contact
>> the
>> existing Win 2k server?
>>
>>
>> hth
>> DDS W 2k MVP MCSE
>>
>> "Gene" <Gene@discussions.microsoft.com> wrote in message
>> news:24F251C3-88C7-40D9-BB7F-B484280D5DB6@microsoft.com...
>> > 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 must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom