w2k3 domain member server

[gn182]

I'm upgrading an NT4.0 domain to w2k3. Using the standard pdc upgrade process and two new servers. At a remote site is a w2k3 server that is a NT4.0 member server. We want to use it as a DC for that location. Currently the entire network is using WINS. The tcp setting will point to the new DC's for resolution and a WINS server to be safe. Should I
1. Set the full computer name to cname.mydomain.local and dcpromo?
or
2. Set the dns suffix to cname.mydomain.local and dcpromo?
or
3. Rejoin the domain, w/o leaving, then dcpromo?

Any thoughts are appreciated

 

[ntinlin]

When you upgrade your NT servers to DC's AD will become available.
If you reboot the W2003 member it should then know about AD and its full computer name will reflect that.

You can then dcpromo.
Presume you are going to be using AD integrated DNS in case of future WAN problems?

Neill

 

[gn182]

yes, dns will be integrated. matter of fact, i'm trying to clean an ad domain that wasn't. two server's where promoted, everything seemed to go alright but they will not sync, no srv record's.