Discussion Locked

Upgrade NT 4 domain to W2k domain

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi, everyone:
I work in a school district. We have 4 seperate NT 4 domains ( no w2k DCs ). ABCD.org is the Admin domain. The Admin domain house the WINS and DHCP servers. The DNS server we use is the one at our ISP. The rest of them is just XYZ1, XYZ2, and XYZ3 domains. These are all internal domains using 10.xx.xx.xx addresses. I'm currently upgrading one domain (XYZ1) from NT to W2k to start. I want it to run in mixed mode. I used a BDC & promoted it to PDC then upgraded it to W2k server running AD. I also installed DNS on this server. I selected to make this domain a seperate domain in an existing forest ( XYZ1.ABCD.ORG ). I selected to have pre w2k names. The upgrade of the server was successful. But here are some problems that I am having:
1 - I found the client computers ( 98 & w2k ) can logon to the new domain but takes about 2 to 3 minutes. They can't map the drives that's on other NT 4 servers because they cannot see the NT servers anymore when browse.
2 - On the just upgraded W2k server, I cannot see other NT servers and w2k member server. At the DNS entry, I deleted the "." entry to make it a non root server, now it added the IP of itself and the w2k member server but still cannot see other NT servers. 3 - I am running DCpromote on the w2k member server to make it a second DC. But it does not allow me to go on because it says "the domain name does not exists, if this is a new domain, the domain name may not have registered with the Domain Name Service".

I configured this upgraded DC to have static IP. Use WINS for name resolving names & gave the IP for the WINS server. No DHCP server running on this server. Put in the IP of our ISP's DNS server and this DC in the DNS box.

I gaveall the info here. How can I correct these problems and correctly configure my DNS. Can someone that has the Upgrading experience help me out ! Thanks a million !!!

6 replies

by pan 13 x

one problem you are going to face is the fact that you are using exturnal dns. You should always with windows 2000 , use inturnal dns and configure the dns to forward all other requests to your isp. Without the inturnal dns being the primary and only dns for your domain , you will never be able to see the registered domain controller and client services. If will also spped up your login process. You may also think about setting a win2k dhcp server and verify that active directory is working correctly on the 2k domain controller. Win98 client may need the active directory client install.

by fatuncleal

I installed DNS on the new server, made it a nonroot DNS. configur it to forward all other requests to the ISP DNS. Added host entries on my DNS for other NT4 servers. And the clients logon does go back to normal. Thanks for your help.

by mcse rabbi

In Win2k, about 95% of all problems with AD have to do with DNS/name resolution, so keep that in mind for the future :)

Generally, it's best to let Win2k configure it's own DNS zone when you do DCPROMO. I've found I get that root "." zone about50% of the time when I try and preconfigure a zone, but if I just let the OS create it's own DNS zone during DCPROMO, I don't get that "." zone.

My recommendation is you do an ?Inter-forest? migration from NT to a new Win2k using the Active Directory Migration Tool (ADMT). http://www.microsoft.com/windows2000/downloads/tools/admt/default.asp

ADMT will allow you to move or clone (copy) objects (user and computer accounts) from a source (either NT or Win2k) domain to a target (Win2k) domain. The downside is your target domain has to be running in ?Native? mode (this simply means you can?t be running any NT BDCs).

The process is fairly straightforward. Here?s a step-by-step:

1) Stand up a new Win2k forest (domain). It has to befully functional, with DNS, WINS, and DHCP running. Do this first, that way you don?t have to worry about upsetting your users if something fails in the DCPROMO. I?d recommend setting up two DC?s. Run DNS on one, and WINS and DHCP on the other.
2) After everything is up and running in your new Win2k forest, install the ADMT on one of your DC?s. Setup a two-way trust between your NT domain(s) and your Win2k domain. Add the ?Administrator? account from each domain into the ?Administrators? group in the other domain.

3) In the target (Win2k) domain, create a group called (your NT domain name followed by three dollar signs).

4) Run ADMT, and follow the simple wizard steps.

I?d suggest migrating user accounts in small batches, and having users log into the new Win2k domain after you copy their accounts.

by mcse rabbi

(Thanks to TechRepublic for only giving us 1930 characters.)

Here's a few other tips:

1) Backup everything before you start

2) Test it in a lab

3) Make sure your target domain is up and running and you can add domain controllers, join computers, create user accounts, access the Internet, print to printers in the NT domain, etc, before you start moving/copying user accounts. This will greatly reduce the number of screams..err..calls...to your help desk.

4) Make sure you have theappropriate settings in your DHCP scope (DNS, WINS, Gateway, etc) and clients and get an IP address.

5) Use your DNS for internal name resolution, but set up ?Forwarders? to your ISP?s DNS server so it can do your external name resolution. (Allow DNS to pass through your firewall).

Here?s a good Micro$oft resource on migrations:
http://www.microsoft.com/windows2000/techinfo/planning/pds-cduadtoc.asp

Let me know if you have any follow up questions.

/s/
Stu

This discussion is closed to new replies.