11 replies
by parbo
by djackson
by boggie
I am currently doing the Win 2000 cert course at Heald College in Roseville CA.The only way to keep your info we have found in class scenarios would be to setup another Domain Controler as root/primary and replicate the Active Directory this would then become your new root DC and you should be ready to work. You will have to reset primary and secondary DNS for the replication and then back to the one for your NT4.0 local. your new DC can then be switched in and out and your old will hold all the info as a backup.
Humans make mistakes and so does Microsoft...SO Backup-backup-backup
and a little CYA too.
Lonnee Boggs
by djackson
I've just finished the MS 2154 Implementing Directory Services, which stated that you cannot change the domain name without rebuilding the structure, thus loosing AD.
Based on that, sorry geezer.
by shanghai sam
by haig
Take a look into the Active Directory Migration Tool from Microsoft for moving users, groups and computers. You could maybe move them into a temporary OU in the root domain, dcpromo the old DC a couple of times and then move them back after the rename?
Sites are independent of your domain structure, so as long as the Root Domain exists, so should your sites and subnets.
DNS I'm not sure about. If you had zone data you need to keep, make the zone a standard primary and then back up the domain.dns file. You could then use it later? Can you be more specific about DNS?
As salways, test test test before taking anyone's advice!
Haig
by djackson
by umbral-echo
I have done this ten or so times. The key is the SIDHistory feature of Windows 2000 Native Mode domains. Use the Active Directory Migration Tool downloadable from the following link:
http://www.microsoft.com/DirectAccess/Products/win2000.svr/0129admt.asp
The help menus are all you need to get up to speed on what needs to be done, but I can't stress enough that there are plenty of issues that can arise so a more thorough understanding of migration should be pursued before doing anything permanent. Chapter 10 in the Windows 2000 Server Resource Kit - Deployment Planning Guide should do the trick.
by djackson
by djackson
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending