I was doing some research before a domain migration at a customer site when I found this great forum post over at the techarena forum. The general steps to migrate from Windows Server 2000 to Windows Server 2008 is almost the same as the steps to migrate from Windows Server 2003 to Windows Server 2008. Scenario: Old server: Windows Server 2000 box New server: Windows Server 2008 box.
Verify that Windows 2000 SP4 have been installed on the old server and Windows Server 2008 SP1 have been installed on the new server. Note: the domain functional level should be in Windows 2000 native mode for the Windows 2000 domain.
Upgrade the Windows 2000 forest schema by running “adprep /forestprep” command on old server. Note: you can copy the adprep folder from the Windows Server 2008 installation disc to the old server to run “adprep /forestprep”. The location is source adprep on the installation disc. Upgrade the Windows 2000 domain schema by running “adprep /domainprep” command on old server. Verify the new server’s TCP/IP configuration has been pointed to existing DNS server. Add new server to existing Windows 2000 domain as a member server. Run dcpromo on new server to promote it as an additional domain controller in existing Windows 2000 domain, afterwards you may verify the installation of Active Directory. Enable Global Catalog on new server and manually Check Replication Topology and afterwards manually trigger replication to synchronize Active Directory database between 2 replica.
Disable Global Catalog on old server. Use NTDSUTIL utility to transfer all the 5 FSMO roles from old server to new server. You’d better transfer FSMO roles via GUI method instead of using NTDSUTIL. Install DNS component on new server and configure it as a new DNS Server(Active Directory Integrated-Zone is preferred). Note: all the DNS configuration need to be transferred from the existing DNS Server. Migrate DHCP service from Windows Server 2000 to Windows Server 2008.
Migrate File Sharing service. You can also use robocopy.exe from the Windows Server Resource kit to copy the files and maintain NTFS permissions. For the shares, the shares definitions and permissions are stored in the following registry key on the server: “HKEYLOCALMACHINE SYSTEM CurrentControlSet Services lanmanserver Shares”. If you export out the whole key and import in the new server, and if you have the files and folders in the same path as in the old server, then you will retain all you shares and share permissions. It’s better to make the old DC offline for several days and check whether everything works normally with the new server online. If so, you may let the old DC online and run DCPROMO to demote it. For more information, please refer to:.
ADPREP is broken down into four stages with Windows Server 2008, instead of the two that most of you may be familiar with when you upgraded to Windows Server 2003. The four steps include Forest Preparation, Domain Preparation, Group Policy Preparation and Read-Only Domain Controller.
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 (This should work on Windows Server 2008). How To Install and Configure DNS Server in Windows Server 2003. How To Convert DNS Primary Server to Active Directory Integrated.
Last Updated on Mon, 18 Apr 2016 If you are upgrading an to include domain controllers running Windows Server 2008, you must run. This command configures permissions so that RODCs are able to replicate DNS application directory partitions. If you are creating a new Active Directory forest that contains only domain controllers running Windows Server 2008, you do not need to run /rodcprep. You can find the adprep command in the cdrom Sources Adprep folder of the Windows Server 2008 installation DVD. Copy the folder to the domain controller acting as the schema master, log on to the schema master as a member of the Enterprise Admins group, open a command prompt, change directories to the Adprep folder, and enter adprep /rodcprep in an elevated command prompt.
DNS application Directory partitions and read-Only DNS When DNS data is stored within AD DS directory databases, it is replicated by default with the directory data with which it is associated. You can also define a custom replication scope for DNS data.
![Windows Server 2008 Adprep Skype Windows Server 2008 Adprep Skype](http://www.bajenlo.com/wp-content/uploads/2008/10/skype_windows.png)
For example, DNS data that belongs to a root domain in a forest must be available to the entire forest, whereas DNS data for a specific domain is required only for that domain. You control DNS data replication scopes through DNS application directory partitions. To support the RODC role, DNS has been updated to provide read-only DNS data for primary zones hosted on the RODC. This further secures the role and ensures that no one can create records from potentially unprotected servers to spoof the network. A DNS server running on an RODC does not support dynamic updates, but clients are able to use the DNS server to query for name resolution. Because the DNS is read-only, clients cannot update records on it.
If, however, a client wants to update its own DNS record, the RODC sends a referral to a writable DNS server. The single updated record will be replicated from the writable DNS server to the DNS server on the RODC. This is a special single object (DNS record) replication that keeps the RODC DNS servers up to date and gives the clients in the branch office faster name resolution.
The Schema Master Role The domain controller holding the is responsible for making any changes to the forest's schema. All other domain controllers hold read-only replicas of the schema. If you want to modify the schema or install an application that modifies the schema, Microsoft recommends you do so on the domain controller holding the schema master role. Otherwise, the changes you request must be sent to the schema master to be written into the schema.