General discussion

Locked

NT 4.0 to Win2k Upgrade in place

By cliffpritchard ·
I am running tests for an upgrade in place for an NT 4.0 domain to Win2k Active Directory. All member servers are already Win2k. I add a BDC to our domain, sync it, pull it to my test and promote it to PDC. SAM and all security caries over fine on upgrade. Problems arise with trying to use existing Win2k server running DNS as the DNS server for the upgraded domain. Other problem is our current domain name is not a fully qualified domain name. When I put FQDN in during upgrade, I run into DNS issues. Anyone have resources I could read on these issues?

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by kmcniff In reply to NT 4.0 to Win2k Upgrade i ...

Ensure that a zone for the FQDN of your new domain exists on the DNS server. I have had problems doing upgrades and new installs and almost always it is a DNS issue. I have found that having DNS up and running with the correct zones already created makes all of the difference. Remember that there are two names by which the domain is named in mixed mode. One is the LANMAN name (old nt4 domain name i.e. MTDOMAIN) and the FQDN (mydomain.com). These names do NOT have to be the same, just makes it easier to remember which is which when you have a number of domains to migrate.

Back to Windows Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums