Archive for the 'Windows 2000' Category

Mar 25 2010

Migrating Active Directory to a new Forest

When you have the need to migrate Windows Domains to a new named Domain or into a different forest, you can use the free Microsoft Active Directory Migration Tool, which exist in multiple versions.


When the source Domain is built with Windows NT4 (at least with SP4 on the PDC), Windows Server 2000 or Windows Server 2003, you have to use ADMT v3 which can migrate to a target Domain installed with Windows Server 2000 or Windows Server 2003.


ADMT v3 can be installed on any computer capable of running the Windows Server 2003 OS.


You can migrate the following OS versions with the ADMT agent:


  • Windows NT Server 4.0 (with SP4 or higher)
  • Windows 2000 Professional
  • Windows 2000 Server
  • Windows XP
  • Windows Server 2003

For a detailed description and how to use ADMT see the ADMT v3.0 Migration Guide.


————————————————————————————-


When the source Domain is built with Windows Server 2000, Windows Server 2003, or Windows Server 2008, you have to use ADMT v3.1 which can migrate to a target Domain installed with Windows Server 2000 or Windows Server 2003 or Windows Server 2008 or Windows Server 2008 R2. This version will be the last one that will support Windows Server 2000 source or target Domains or Windows Server 2000 Domain controllers.


ADMT v3.1 can be installed on any computer capable of running the Windows Server 2008 OS, unless they are Read-Only domain controllers (RODCs) or in a Server Core configuration.


You can migrate the following OS versions with the ADMT agent:



  • Windows 2000 Professional
  • Windows 2000 Server
  • Windows XP
  • Windows Server 2003
  • Windows Vista
  • Windows Server 2008
  • Windows 7
  • Windows Server 2008 R2

For a detailed description and how to use ADMT see the ADMT v3.1 and 3.2 Migration Guide.


Additional you maybe need the Password Export Server (PES) version 3.1, either for 32bit or 64bit.


————————————————————————————-


When the source Domain is built with Windows Server 2003, or Windows Server 2008, you have to use ADMT v3.2 which can migrate to a target Domain installed with Windows Server 2003 or Windows Server 2008 or Windows Server 2008 R2.


ADMT v3.2 can be installed on any computer capable of running the Windows Server 2008 R2 OS, unless they are Read-Only domain controllers (RODCs) or in a Server Core configuration.


You can migrate the following OS versions with the ADMT agent:


  • Windows XP
  • Windows Server 2003
  • Windows Vista
  • Windows Server 2008
  • Windows 7
  • Windows Server 2008 R2

For a detailed description and how to use ADMT see the ADMT v3.1 and 3.2 Migration Guide


Additional you maybe need the Password Export Server (PES) version 3.1 for 64bit.


Here you’ll find some common installation issues from ADMT v3.2 listed from Ned Pyle at “Ask the Directory Services Team


 


Related Documents about ADMT:


Restructuring Windows NT 4.0 Domains to an Active Directory Forest


Restructuring Active Directory Domains Within a Forest


Restructuring Active Directory Domains Between Forests


Error message when you use ADMT version 3 to migrate computer accounts from one Windows Server 2003 domain to another: “ERR3:7075 Failed to change domain affiliation” KB929493


How to use a SID mapping file with the ADMT tool to perform a resource domain migration to Windows Server 2003 KB835991


Known issues that may occur when you use ADMT 3.1 to migrate to a domain that contains Windows Server 2008 R2 domain controllers KB976659


You cannot uninstall ADMT 3.1 after you perform an in-place upgrade to Windows Server 2008 R2 KB974625


How To Use Visual Basic Script to Clear SidHistory KB295758

2 responses so far

Feb 13 2010

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

!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!


- 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

2 responses so far

Feb 06 2010

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

!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!


If you have installed Exchange 2000 or Exchange 2003 in the domain see the following article first, Exchange requirements otherwise follow the steps below


- 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 installed on a DC)


- run replmon from the run line or repadmin /showreps(only if more then one DC exist), dcdiag and netdiag from the command prompt on the old machine to check for errors, if you have some post the complete output from the command here or solve them first. For this tools you have to install the support\tools\suptools.msi from the 2000 installation disk.


- run adprep /forestprep and adprep /domainprep and adprep /domainprep /gpprep and adprep /rodcprep from the 2008 installation disk against the 2000 schema master(/forestprep) / infrastructure master(/domainprep/rodcprep), with an account that is member of the Schema/Enterprise/Domain admins, to upgrade the schema to the 2008 version (44) or 2008 R2 (47). On the Windows Server 2008 R2 disk are adprep32.exe (32bit) and adprep.exe (64bit) located, so make sure to use the correct version.


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


- you can check the schema version with “schupgr” or “dsquery * cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr objectVersion” without the quotes in a command prompt


- 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.


- Install the new machine as a member server in your existing domain


- configure a fixed ip and set the preferred DNS server to the old DNS server only, if you think about disabling IPv6 as you are not using it or it was recommended to you, keep attention to the UPDATE. Follow (http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspx) to disable it, if really required


UPDATE for IPv6 02.06.2011: Keep in mind that IPv6 will become the future protocol and you should get familiar with it. Also the recommendation from Microsoft is to let IPv6 enabled, as some new features/services or applications already require IPv6 to be enabled. Exchange 2010 and DirectAccess are some examples.


- run dcpromo and follow the wizard to add the 2008 server to an existing domain, make it also Global catalog and DNS server.


- 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 on both domain controllers. For using netdiag.exe on 2008, NOT 2008 R2, you have to download and install (http://www.microsoft.com/downloads/details.aspx?familyid=96A35011-FD83-419D-939B-9A772EA2DF90&displaylang=en), ignore the compatibility warning, or extract netdiag.exe only


- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801) applies also for 2008/2008R2), FSMO should always be on the newest OS DC


- after transfer of the PDCEmulator role, configure the NEW PDCEmulator to an external timesource 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 2008 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


Demoting the old DC(if needed)


- reconfigure your clients/servers that they not longer point to the old DC/DNS server on the NIC


- to be sure that everything runs fine, disconnect the old DC from the network 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 start AD sites and services and delete the old servername under the site, this will not be done during demotion

8 responses so far