After you plan how the migration will take place and perform initial steps for the migration, you need to perform the actual migration. Like the planning stage, the steps involved in performing the actual migration vary according to the type of migration being performed. This section examines migration scenarios for common roles.
Migrating AD DS and DNS server roles
1. Add the Active Directory Domain Services role to the destination server.
2. Record the DNS settings on the source server using ipconfig /all.
3. Replicate the source server’s DNS settings onto the destination server. Use
the Dns-Service.REG and Dns-Software.REG files, which should be copied to
%windir%\System32\DNS on the destination server.
4. Execute the DNSconvergeCheck.cmd Convergence Verification Script to ensure that all DNS records are replicated between the source and destination servers.
5. Ensure that the Flexible Single Master Operations (FSMO) roles are migrated, if necessary.
6. Migrate IP addresses by changing the source server’s IP to a different IP address and then changing the destination server to the source server’s original IP.
7. Rename the source server and use the netdom renamecomputer command to give the destination server the source server’s original name.
8. Verify that the destination server is operating as the new domain controller.
Migrating File Services roles
1. Freeze configuration on the source server.
2. Migrate settings such as server message block (SMB), Offline Files (also called clientside caching or CSC), DFS Namespaces, DFS Replication, File Server Resource Manager (FSRM), and Shadow Copies of Shared Folders.
3. Export local users and groups. From the Windows Migration Tools PowerShell, use this command:
Export-SmigServerSetting -User All -Group -Path <storepath>
4. Import the users from the source to the destination server:
Import-SmigServerSetting -User All -Group -Path <storepath>
5. Migrate the data.
6. Rename and re-address the source server by changing its name and IP address.
7. Reconfigure the destination server to have the same name and address as the source.
8. Import settings from Step 2 to the destination server.
Migrating Dynamic Host Configuration Protocol (DHCP) server roles
1. Install the DHCP role onto the destination server.
2. Stop the DHCP Server service (Stop-Service DHCP server).
3. Collect data from the source server with the Migration Tool cmdlet Export-SmigServerSetting:
Export-SmigServerSetting –featureID DHCP –User All –Group –IPConfig –path <storepath>
4. Delete the DHCP authorization on the source DHCP server:
Netsh DHCP delete server <server FQDN> <Server IP Address>
5. On the destination server, run the cmdlet Import-SmigServerSetting:
Import-SmigServerSetting -featureID DHCP -User All -Group -IPConfig <All | Global | NIC> -SourcePhysicalAddress <Source IP Address> -TargetPhysicalAddress -Force -path <storepath>
6. Start the DHCP service on the destination server: Start-Service DHCPServer
7. Authorize the destination server (case sensitive):
netsh DHCP add server <Server FQDN> <Server IP Address>
