Just wondering if someone could help me with the following:
I have a PDC which has a primary domain I now wish to change; the PDC controls three other desktops; therefore I would like some guidance on how to do this effectively.
There's no such thing as a PDC in an Active Directory domain. Everything is just a DC. If you need to replace the server and maintain the domain, simply add another server and run DCPROMO on it. This will allow you to add a second domain controller. Then you need to transfer the FSMO roles (5 Critical services that can only be on one DC - the roles can be split amongst other DCs (making the PDC term inaccurate at best) but there can be only one of each role on the domain).
Since 2000 server isn't sold any more, I suspect you'll be upgrading to 2003. There's a bunch of things you need to check and do before this can be successful. I have a list of some links you might find useful here:
Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain
Hotfixes to install before you run adprep /Forestprep on a Windows 2000 domain controller to prepare the Forest and domains for the addition of Windows Server 2003-based domain controllers
Commodore.ca | Windows | How To Upgrade Windows 2000 Domain to Windows 2003 Server
Quote from the top of this article: "Several glossy Microsoft presenters have stated that all you need to do to complete a Windows 2003 Domain upgrade is run ADPREP and then upgrade away. This may work for very small / simple environments but it is definitely not good advice for most companies. After upgrading five servers in two unrelated domains and installing many fresh copies of 2003 I can say that I personally would not skip a single step in the process I have developed below."
Here are some links that should help you in replacing existing domain controllers and/or transferring services and Active Directory functions to another/new system:
How can I transfer some or all of the FSMO Roles from one DC to another?
How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003
Exchange Considerations:
[If you run Exchange 2000] Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.