Feb 13 2010

Upgrading an Active Directory Domain from Windows Server 2000 to Windows Server 2003 or Windows Server 2003 R2


– On the old server open DNS management console and check that you are running Active directory integrated zone (easier for replication, if you have more then one DNS server on Domain controller)

– run replmon (GUI version) from the run line or repadmin /showreps (only if more then one DC exist), dcdiag /v and netdiag from the command prompt on the old machine to check for errors. For this tools you have to install the support\tools\suptools.msi from the Windows server 2000 or Windows server 2003 installation disk.

– if the first installed DC in the domain should be removed or replaced with another one, doesn’t matter if new or same OS version, then make sure that you export the recovery agents EFS certificate private key from the DC BEFORE you demote/retire it. Details how to do this are listed in (http://support.microsoft.com/kb/241201) and (http://technet.microsoft.com/en-us/library/cc755157(WS.10).aspx) if you do not save the it, you will not be able to encrypt data in case of problems.

– run adprep /forestprep and adprep /domainprep from the 2003 installation disk against the Windows server 2000, with an account that is member of the Schema admins, to upgrade the schema to version 30

– if you upgrade to Windows server 2003 R2 use adprep from the second disk from the set and go to E:\CMPNENTS\R2\ADPREP, where E: is your disk drive, which will upgrade the schema to version 31

– see here about adprep in detail (http://technet.microsoft.com/en-us/library/cc755958(WS.10).aspx)

– In Windows server 2000 you have sometimes to enable the write access to the schema master (http://support.microsoft.com/default.aspx/kb/285172)

– Install the new machine as a member server in your existing domain and configure a fixed ip address and set the preferred DNS server to the old DNS server only

– run dcpromo and follow the wizard to add the Windows server 2003 to an existing domain

– if you are prompted for DNS configuration choose Yes (also possible that no DNS preparation occur), then install DNS after the reboot without configuration, just wait for AD replication

– for DNS give the server time for replication, at least 15 minutes. Because you use Active directory integrated zones it will automatically replicate the zones to the new server. Open DNS management console to check that they appear

– if the new machine is domain controller and DNS server run again replmon, dcdiag and netdiag on both domain controllers

– if you have no errors, make the new server Global catalog server, open Active directory Sites and Services and then double-click sitename, double-click Servers, click your domain controller, right-click NTDS Settings, and then click Properties, on the General tab, click to select the Global catalog check box (http://support.microsoft.com/?id=313994)

– Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)

– after transfer of the PDCEmulator role, configure the NEW PDCEmulator to an external time source and reconfigure the old PDCEmulator to use the domainhierarchie now. Therefore run on the NEW “w32tm /config /manualpeerlist:PEERS /syncfromflags:manual /reliable:yes /update” where PEERS will be filled with the ip address or server(time.windows.com) and on the OLD one modify the registry key value “Type” to “Nt5Ds” :  HKLM\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ Parameters\  as w32tm wan’t run with Windows 2000 and stop/start the time service on the old one.

– you can see in the event viewer (Directory service) that the roles are transferred, also give it some time

– reconfigure the DNS configuration on your NIC of the 2003 server, preferred DNS itself, secondary the old one

– if you use DHCP do not forget to reconfigure the scope settings to point to the new installed DNS server

– export and import of DHCP database (if needed) (http://support.microsoft.com/kb/325473)

– backup WINS (http://technet.microsoft.com/en-us/library/cc727901.aspx)

– restore WINS (http://technet.microsoft.com/en-us/library/cc727960.aspx)

Demoting the old DC (if needed)

– reconfigure domain machines, that they not longer use to the old DNS server on the NIC

– to be sure that everything runs fine, disconnect the old DC from the network for one or two days and check with clients and servers the connectivity, logon and also with one client a restart to see that everything is ok

– then run dcpromo to demote the old DC, if it works fine the machine will move from the DC’s OU to the computers container, where you can delete it by hand. Can be that you got an error during demoting at the beginning, then uncheck the Global catalog on that DC and try again

– check the DNS management console, that all entries from the machine are disappeared or delete them by hand if the machine is off the network for ever

– also you have to open AD sites and services and delete the old server name under the site, this will not be done during demotion

No responses yet

Trackback URI | Comments RSS

Leave a Reply