Windows Forum

Ask something
Discussion Locked

NT4 migration to 2003 Active Directory

0 helpful
3 replies

by rmcintosh

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

I'm doing an upgrade inplace from NT4 to 2003 AD. My plan is to load AD on DC1 to include DNS to create the forest. Then add DC2 to the single domain within the forest.
After the upgrade, with the 4 gig NT4 limitation, I'll have to transfer the 5 master roles to DC2 then remove AD from DC1 then run dcpromo again to rebuild DC1.
I know I'll loose my original DNS load but will I be able to reload dns again while rebuilding DC1 back with a bigger sysvol? What kind of problems could I encounter using this technique?
Thanks in advance.

3 replies

by p.j.hutchison

To make it easier, make DNS Active Directory Integrated which will store DNS in AD rather than a text file. Then when you make DC2 a DNS and AD integrated, then it will pick up DNS settings as well.

by rmcintosh

Thanks for the reply. Are you saying to load DNS while migrating on DC1, then then load DNS on DC2 also and point to DC1's DNS?

Thanks again.

by edrossius

Pay attention to the following remarks:
1) Active Directory NEED DNS to work properly. If you "destroy" your DNS during your migration, you can encounter network resolution problems.
2) W2K and WXP client computers NEED DNS to find Domain Controllers and Global Catalogs servers. If no DNS, you can encounter problems authenticating your users on the domain.

Conclusion: you absolute need to make your DNS ALWAYS available.

It's possible by doing so:
During your in-place upgrade, DNS Server service will be installed on DC1. By default, all DNS zones hosted will be "Active-Directory Integrated". It means every records are stored in Active Directory database rather than in a text file (*.dns). When you'll install DC2 as an additional Domain Controller of an existing domain, also add the DNS Server Service on DC2. You'll be able to configure DNS on DC2 to be authoritative for your domain's zone (DNS MMC). Since you plan to remove DC1 for a while, be sure to configure your client computers and DC2 with the DC2's IP address as primary DNS server in your network configuration.
Then, transfer your 5 master roles and demote DC1.
Perform all necessary tasks to rebuild DC1 from scratch (if necessary) and promote it again as domain controller (don't forget to add the DNS server service and configure it to be authoritative for your domain's zone).

Hope this will help...

This discussion is closed to new replies.