Rebuild Forest Root Domain Controller


N

Nino_1

Hi,

We are planning a rebuild of our Forest Root domain controller, the
FSMO roles have been transferred to another domain controller within
the domain, both domain controllers are running WINS as the only
service so we have redunancy as far as NETBIOS is concerned. The
problem started with the local DNS on the forest root dc not resolving
when set to local within the TCP/IP properties prompting us to
rebuild. My hesitation on this is DNS, when we rebuild the forest root
is DNS going to drop off rendrering the root and child domains
inoperable? the dns zones are all active directory integrated except
for one external DNS residing as a secondary zone. Will this rebuild
go as planned with the given situation?

Many thanks in advance.


Nino
 
Ad

Advertisements

A

Ace Fekay [MVP Direcrtory Services]

Nino_1 said:
Hi,

We are planning a rebuild of our Forest Root domain controller, the
FSMO roles have been transferred to another domain controller within
the domain, both domain controllers are running WINS as the only
service so we have redunancy as far as NETBIOS is concerned. The
problem started with the local DNS on the forest root dc not resolving
when set to local within the TCP/IP properties prompting us to
rebuild. My hesitation on this is DNS, when we rebuild the forest root
is DNS going to drop off rendrering the root and child domains
inoperable? the dns zones are all active directory integrated except
for one external DNS residing as a secondary zone. Will this rebuild
go as planned with the given situation?

Many thanks in advance.


Nino

Your description and what you've done so far is a little too general. We'll
need a little more specifics to help.

Let's disregard WINS for the moment, because it has nothing to do with AD.

First, what OS are you talking about? You've posted in the Win2000 forum. Is
it Win2000?

If you said you've transferred the roles to another DC in the domain, what
about DNS? Was DNS installed on the source (transferred the roles from)? If
so, is DNS installed on the target (the other) DC? Since you've stated the
zone is AD integrated, and if DNS is installed on both DCs, then DNS on the
target DC should be fine.

However, if you've uninstalled DNS on the source, then later installed DNS
on the target DC after the fact, you're starting with a whole new zone.
Also, if you've deleted the zone on the source, then the zone gets deleted
domain wide (or forest wide, depending if it's 2003 and what zone
replication scope the zone was in).

Also, you can't simply 'rebuild' a domain, let alone the forest root domain.
One of the DCs have to exist at all times or the whole forest falls apart
and will be useless.

Simply put, if by 'rebuild' you mean you want to upgrade to new hardware,
the following is a loose guideline:

1. Transfer Roles
2. Make sure the other DC is a GC
3. Make sure DNS is AD integrated and installed on both DNS servers
4. Change the DNS addresses on both DCs to point to the other DC
5. Uninstall DNS on the old DC
6. Demote the old DC
7. Install the OS on the new hardware
8. Promote to a DC
9. Install DNS, then just wait and the zone will auto-appear
10. Make it a GC.
11. Move the DNM, Schema and PDC Emulator role to the new box
12. Allow replication to catch up (3 or more hours depending on how the Site
links, domains, replication frequency and replication partners are
configured)
13. Make the new DC point to its partner as the 1st, and itself as the
second and vice-versa on the other DC.

Now if you're upgrading to 2003 from 2000, make a new step 7a to run adprep
on the existing other DC and allow that to replicate throughout the forest.
If you run into any errors possibly because Exchange 2000 or 2003 is
installed, they will need to be addressed prior to advancing any further.

Maybe you can elaborate a bit.

Keep in mind, this is based on your post. If there is more that I am not
aware of, (if 2003, current replication scopes, Exchange, etc), it will
alter the steps. Also if I missed anything, I hope someone will jump in and
make the necessary suggestions and adjustments.

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations
 
N

Nino_1

Your description and what you've done so far is a little too general. We'll
need a little more specifics to help.

Let's disregard WINS for the moment, because it has nothing to do with AD..

First, what OS are you talking about? You've posted in the Win2000 forum.Is
it Win2000?

If you said you've transferred the roles to another DC in the domain, what
about DNS? Was DNS installed on the source (transferred the roles from)? If
so, is DNS installed on the target (the other) DC? Since you've stated the
zone is AD integrated, and if DNS is installed on both DCs, then DNS on the
target DC should be fine.

However, if you've uninstalled DNS on the source, then later installed DNS
on the target DC after the fact, you're starting with a whole new zone.
Also, if you've deleted the zone on the source, then the zone gets deleted
domain wide (or forest wide, depending if it's 2003 and what zone
replication scope the zone was in).

Also, you can't simply 'rebuild' a domain, let alone the forest root domain.
One of the DCs have to exist at all times or the whole forest falls apart
and will be useless.

Simply put, if by 'rebuild' you mean you want to upgrade to new hardware,
the following is a loose guideline:

1. Transfer Roles
2. Make sure the other DC is a GC
3. Make sure DNS is AD integrated and installed on both DNS servers
4. Change the DNS addresses on both DCs to point to the other DC
5. Uninstall DNS on the old DC
6. Demote the old DC
7. Install the OS on the new hardware
8. Promote to a DC
9. Install DNS, then just wait and the zone will auto-appear
10. Make it a GC.
11. Move the DNM, Schema and PDC Emulator role to the new box
12. Allow replication to catch up (3 or more hours depending on how the Site
links, domains, replication frequency and replication partners are
configured)
13. Make the new DC point to its partner as the 1st, and itself as the
second and vice-versa on the other DC.

Now if you're upgrading to 2003 from 2000, make a new step 7a to run adprep
on the existing other DC and allow that to replicate throughout the forest.
If you run into any errors possibly because Exchange 2000 or 2003 is
installed, they will need to be addressed prior to advancing any further.

Maybe you can elaborate a bit.

Keep in mind, this is based on your post. If there is more that I am not
aware of, (if 2003, current replication scopes, Exchange, etc), it will
alter the steps. Also if I missed anything, I hope someone will jump in and
make the necessary suggestions and adjustments.

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
checkhttp://support.microsoft.comfor regional support phone numbers.

Infinite Diversities in Infinite Combinations- Hide quoted text -

- Show quoted text -

Ace,

thanks for your reply,


OS is Windows Server 2003.

DNS is installed and running on the target DC that now holds the FSMO
roles.

We have not un-installed DNS on the source DC (root dc).

We will not be rebuilding the domain just the DC (just so happens that
this is the 1st domain controller brought online in the parent
domain.)

If I understand correctly, the numbered guidline will work in this
situation.

HTH

Nino
 
Ad

Advertisements

A

Ace Fekay [MVP Direcrtory Services]

On Aug 11, 8:04 pm, "Ace Fekay [MVP Direcrtory Services]"


Ace,

thanks for your reply,


OS is Windows Server 2003.

DNS is installed and running on the target DC that now holds the FSMO
roles.

We have not un-installed DNS on the source DC (root dc).

We will not be rebuilding the domain just the DC (just so happens that
this is the 1st domain controller brought online in the parent
domain.)

If I understand correctly, the numbered guidline will work in this
situation.

HTH

Nino

Nino,

Good to hear it will help. Post back if you have any other questions or
problems.

Ace
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top