i am going to add a windows 2003 standard machine to a windows 2000 domain as a second controler, with the goal of eventually retiring the windows 2000 machine.

are there any special considerations for this subject?

i have replaced many windows 2003 domain controlers with other windows 2003 machines and from what i can tell this would work the same way.

1) add domain controler to network , dcpromo after forestprep.
2) make sure active directory is replicating
3) transfer fsmo roles
4) verify fsmo roles
5) eventually drop windows 2000 from network.


thanks guys in advance
 

Windows 2003 AD Prep
http://www.petri.co.il/windows_2003_adprep.htm

_______________________________________
Great knowledge can be obtained by mastering the Google algorithm.

http://www.google.com/search?sourceid=navclient&ie=UTF-8&rlz=1T4WZPA_enUS315US315&q=upgrading+from+Windows+2000+domain+to+a+windows+2003+domain

_______________________________________
Great knowledge can be obtained by mastering the Google algorithm.

Thanks bro, thats exactly what i was looking for

- also sorry, i thought i responded to this thread earlier!

i am doing this change next week , thanks for the url's and help!
 

if you only have 1 win2000 domain controller do you still have to run adprep on it before adding the 2003 server as a domain controller?

Since you are extending the AD schema to support Windows 2003 Schema changes then yes it is still required

oh ok.

how long does adprep take to complete on 1 server?

couple of minutes...

http://www.samtechconsulting.com
_______________________________________
Great knowledge can be obtained by mastering the Google algorithm.

thanks. i'll be running this today since we have to decommission the win2k box by mid august

For your step 5 above, you will want to gracefully remove the server from the domain.  Make sure that you have transferred DNS, DHCP and WINS and any other services off of the 2000 box first.

When you have removed the server from the domain, make sure it no longer exists in DNS.  Also make sure it is removed from the AD metadata.

I recommend running the script in my FAQ FAQ96-4733: How do I seize FSMO roles or forcefully remove a DC? to verify that the server is not still in metadata.  If it is then you can remove it on the spot with the script, otherwise just cancel out of the script and no action is taken.

I hope you find this post helpful.  

Regards,

Mark

Check out my scripting solutions at http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER.  The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier!  Save time, get more work done, get the Admin Script Pack.

Slight issue. when running adprep  /forestprep on the win 2k domain controller.  I get the following message

" There is a schema conflict with Exchange 2000. The schema is not upgraded. Please resolve the schema conflict before running adprep"

Now the article referenced in the msg is giving confusing information. first it says run

ldifde -i -f inetorgpersonfix.ldf -v -c DC=X "dn path for forest root domain"

where should be extracted to?

it also says to add the snap -in to the mmc and go to operations master and select "operations master" however the box to allow changes to the schema is grayed out. I'm logged in with the domain admin account and still can't do it. that account is a member of the schema admins account. What else should I check?

http://support.microsoft.com/?id=314649

run from Exchange 2003 cd, setup /forestprerp
and setup /domainprep.

http://www.samtechconsulting.com
_______________________________________
Great knowledge can be obtained by mastering the Google algorithm.