NT to 2003 migration question

[DantanaSwat]

We currently have an NT domain. Out of 20 servers or so we have 6 left that are NT. Unforunatly our domain controller needs to be replaced. Being that I cant seem to set up a 2003 box to take over domain controller for the PDC I figured Id try a side by side migration. Set up an AD domain and use ADMT 2.0. Too bad that the extent of the documentation I have on doing a side by side migration is the ADMT help file. Everything I pull up by microsoft simply gives the 'upgrade domain controller' route. Is there anywhere I can look for side by side migration documentation?

 

[MasterRacker]

I'm in aposition where I'm going to have to do someting similar to this also. Having no experience yet with 2003, I would also appreciate some good links on info.


Jeff
The future is already here - it's just not widely distributed yet...

 

[newbobbys9]

I am with you on this. I would say about mid stream. I have set up a parallel new domain which will become our new 2003 AD domain. Using ADMT, have pulled in most of the groups, have started with bringing in computers and servers. (Recently got an inexpensive network management tool (Hyena) that has helped with the computers). My dilema now is that some of the other locations (MAN, not WAN) have PDCs that are doing all kinds of stuff--if I kill the NT 4 PDC, I kill all the shares, print servers and apps they are running. I think I can upgrade the PDC into my new domain and ignore the SAM--keep it a member server, but not sure. Most upgrades are to bring into a DC in AD; I only want the other stuff. I have my new DCs and DNS in the new forest that have (or will have) the stuff migrated in. So, my question is, "Can I bring in a BDC (will promote a "clean" BDC to PDC) into my happy 2003 family as a member server to get the apps, shares, etc.?" Any help will be appreciated. Thanks.

 

[ntinlin]

You need a tool called UPromote from Algintech. It will take a BDC or PDC and turn it into a standalone server which you can then rejoin to domain as a member server.

Used it very successfully in moving our resource domain PDC's to both DC's and member servers in AD.