Hello, I'm planning a migration from an old NT domain with obsolete server to a new Win2003 domain with new servers. I've learnt that there are 2 possible ways to do that: 1) UPGRADE the PDC from NT to Win 2003 then raise domain's functional level to Win 2003 2) Create a new W2003 domain then MIGRATE the old one by means of ADMT. In my environment, I think that the upgrade solution would better suite my needs, so I should install NT to the new server, promote it to be the PDC, then upgrade it to Win2003. This way, however, I can encounter driver compatibility issues when installing NT to the new server. So I was wondering if a third solution was possible, that is: Install w2003 on the new server, make it a BDC in the old domain, upgrade it to a PDC, then raise domain's functional level to Win 2003.

The recommended method for upgrading is as follows: If you have a PDC and at least one BDC, ensure replication has been forced between the two before begining. Then, take your PDC offline and promote the BDC to PDC. Completely remove the original PDC (which you've shut down) from the network. This is your fallback should the upgrade fail (you can quickly return to your NT domain by removing the failed 2003 server and bringing your original PDC back up). Then perform the upgrade on the new PDC. If you don't have a PDC and a BDC your best bet might very well be to install NT 4.0 on the new server and make it a BDC. Allow replication to happen and then follow the above steps (ie: add it as a BDC then promote it to PDC and then perform the upgrade to 2003 then dcpromo the 2003 server to a DC). I don't believe you can make a 2003 server a BDC in an NT 4.0 domain. I may be wrong on this count, but I know you couldn't in 2000.

"If you don't have a PDC and a BDC your best bet might very well be to install NT 4.0 on the new server and make it a BDC." To be honest, I'd do the migration path instead. I don't see the point in doing the above in that situation. Go get the Active Directory Migration Tool 3.0. "I don't believe you can make a 2003 server a BDC in an NT 4.0 domain." You are correct. "Install w2003 on the new server, make it a BDC in the old domain, upgrade it to a PDC, then raise domain's functional level to Win 2003." What are you gaining from this? I can tell you the problem with this: You're doing an OS upgrade instead of a fresh install. Almost sounds like this is a one DC environment at the end of this. Do you really want your sole DC to be an OS install upgraded from NT4? I sure as heck wouldn't. "Milk was a bad choice!"

I would upgrade a NT DC to 2003. Then dcpromo it to a 2003 DC. Then bring in the new server and an additional DC. Then xfer the fsmo roles and GC to the new server. The preserves the sam transfer from NT to 2003. I would keep the converted NT box as a DC until you can bring on another on newer hardware. Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

Thanks for the replies, I think I'll go with the migration by means of ADMT.

here's the third solution: MOVING CORE SERVICES 1. add the win2k3 to the nt domain 2. migrate all services off NT to the new win 2k3 server 3. set dhcp on old nt box (i hope you got one to refresh to 1 day) 4. set dhcp service to 30 days (new 2k3) with different ip range so they can run concurently 5. on a friday - turn off dhcp on old nt - monday everyne gets new dhcp setting INSTALLING AD 6. install nt server on "respectable" workstation and promote to pdc, and allow sync - keep it running for a few days 7. run dcpromo on workstation to AD 8. run dcpromo on win2k3 server 9. run dcpromo on workstation to remove ad 10. once ad is runnign on 2k3 - do what ever you wnat with the old NT boxes basic trial and error troubleshooting