I have an odd question. We are trying to practice upgrading our Win2000 parent/child domain to Win2003. As such, I have recreated this configuration in a VMware ESX cluster. (I made copies of a DC for both the parent and child, and seized all roles, and cleaned out the metadata for all the missing DCs). That seemed to go well. So my boss turned the next phase of the project - actually DCpromoing a Win2003 server in each domain - to a co-worker.
1. That is the easiest method to go from Win200 to Win2003, AFAIK. Make a Win2003 a member server, and then DCpromo it- will upgrade your domain level to 2003. (after adprep /forestprep, adprep /schemaprep, of course) He reports that he had to first set the Win2000 domain into native mode, and not the mixed mode we run in production. I wouldn't have thought that to be needed. Does that sound right? I think we should be able to go to native mode on production, as we have no old NT/Win9.x clients). 2. We have to DCpromo a Win2003 server in *each domain*, the parent and the child, correct? I can't imagine that it only needs to be done on the parent. I did have him verify that the child domain DNS has all the proper entries for it's reverse zone, and that it is set to forward to the parent DNS server. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
