We didn’t…I was just mentioning that with regard to having 2000 DC’s co-existing with 2003 DC’s…I didn’t know that it would matter to you that much I replied to your message instead of someone else’s reply.

 

Have a great day!

Rob


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Brunson
Sent: Friday, August 04, 2006 11:34 AM
To: [email protected]
Subject: RE: [ActiveDir] 2003 domain & 2000,

 

Sorry…., how did we get to the topology generator from adprep?

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Williams, Robert
Sent: Friday, August 04, 2006 11:05 AM
To: [email protected]
Subject: RE: [ActiveDir] 2003 domain & 2000,

 

Hey Kevin, I dunno if you’re already aware of this or if it even applies in your environment…but if you have more than one site then the new DC will automatically become the ISTG of the site you put it into.  Whenever a 2003 DC is added to a site, it will assume ISTG ownership if there are no other 2003 DC’s in that site.  Might not even matter for your situation, but the following is a really good read anyway to understand all the cool replication stuff.

 

Here’s a snippet from the following URL:

http://technet2.microsoft.com/WindowsServer/en/library/c238f32b-4400-4a0c-b4fb-7b0febecfc731033.mspx?mfr=true

<SNIP>

ISTG Role Ownership and Viability

The owner of the ISTG role is communicated through normal Active Directory replication. Initially, the first domain controller in the site is the ISTG role owner. It communicates its role ownership to other domain controllers in the site by writing the distinguished name of its child NTDS Settings object to the interSiteTopologyGenerator attribute of the NTDS Site Settings object for the site. As a change to the configuration directory partition, this value is replicated to all domain controllers in the forest.

The ISTG role owner is selected automatically. The role ownership does not change unless:

• The current ISTG role owner becomes unavailable.

• All domain controllers in the site are running Windows 2000 and one of them is upgraded to Windows Server 2003.

If at least one domain controller in a site is running Windows Server 2003, the ISTG role is assumed by a domain controller that is running Windows Server 2003.Robert Williams
</SNIP>

Have a great day!

Robert Williams


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Brunson
Sent: Friday, August 04, 2006 9:32 AM
To: [email protected]
Subject: RE: [ActiveDir] 2003 domain & 2000,

 

They will be able to coexist with no problems, assuming you take all of the appropriate steps before you upgrade.  You will need to run adprep to prepare the forest and domain for the 2003 schema.  Run adprep /forestprep on the schema master, and adprep /domainprep on the infrastructure master.  If you haven’t moved these roles, they will be installed on the first domain controller that was put into place. 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of shereen naser
Sent: Friday, August 04, 2006 8:21 AM
To: [email protected]
Subject: [ActiveDir] 2003 domain & 2000,

 

We have 5 domain controllers all 2000, one forest, now we want to add one more domain controller, and the sever is 2003, if we add 2003 domain controller is there going to be any issues with the 2000? compatibility issues, replicaiton issues, errors that will show? any thing I should be worried about when the 2 domain controllers (2000 and 2003) coexist?

thank you

Reply via email to