Read Windows Server 2008 R2 Unleashed Online
Authors: Noel Morimoto
during the configuration of the Computer Migration Wizard. Then the migrated comput-
16
ers reboot into the new domain with the designated settings migrated.
Migrating Other Domain Functionality
In addition to the Group, User, and Computer Migration Wizards, several other wizards
can be used to migrate specific domain-critical components. These wizards operate using
the same principles as those described in the preceding sections and are straightforward in
their operation. The following is a list of the additional wizards included in ADMT v3.1:
. Security Translation Wizard
. Reporting Wizard
. Service Account Migration Wizard
. Exchange 5.5 Mailbox Translation Wizard
. Retry Task Wizard
. Password Migration Wizard
Virtually all necessary functionality that needs replacing when migrating from one
domain to another can be transferred by using ADMT v3.1. It has proven to be a valuable
tool that gives administrators an additional option to consider when migrating and
restructuring Active Directory environments.
Migrating Server Roles to Windows Server 2008 R2
Migrating server roles, system settings, and data from your 32-bit and older Windows
operating systems to Windows Server 2008 R2 has been made easier with the introduction
516
CHAPTER 16
Migrating from Windows Server 2003/2008 to Windows Server
2008 R2
of the Windows Server Migration Tools, the Printer Migration Wizard, and the
printbrm.exe command-line utility. The following sections go over the installation, setup,
and usage of these tools.
Windows Server Migration Tools
The Windows Server Migration Tools are a Windows Server 2008 R2 feature, installed via
the Add Feature Wizard, that uses PowerShell cmdlets to facilitate the migration of server
roles, system settings, and data from older versions of Windows and 32-bit versions of
Windows to Windows Server 2008 R2. Before the Windows Server Migration Tools can be
used to migrate services from one server to another, the tools need to be installed on both
the source and destination servers. Because the Windows Server Migration Tools are
included with Windows Server 2008 R2, the tool must be packaged and installed on
Windows Server 2003 or Windows Server 2008 systems if the source servers are running
either of these operating systems.
Windows Server Migration Tools source server requirements are as follows:
. Windows Server 2003 SP2 or later
. 25MB of free space to store the Windows Server Migration Tools folder
. Microsoft .NET Framework 2.0
ptg
. Windows PowerShell 1.0 or later
As with any migration, a backup of the system or data being migrated is recommended
prior to using the Windows Server Migration Tools. Prior to decommissioning any
migrated server, confirm the new server is functioning properly.
To prepare the target Windows Server 2008 R2 server for migration, perform the following
steps:
1. On the target server, go to Add Features, click Windows Server Migration Tools, and
then click Next.
2. Click Install and then click Close when installation is complete.
3. On the target server, open a command prompt as an administrator.
4. Type CD %windir%\system32\servermigrationtools, and then press Enter.
5. Type smigdeploy /package /architecture x86 /os ws03 /path
NOTE
If the source server is 64-bit, change x86 to amd64, and if the source server is
Windows Server 2008, change WS03 to WS08. The previous command will create an
appropriately named folder in the path specified.
To prepare the source server for migration, perform the following steps:
Multiple Domain Consolidation Migration
517
1. Copy
2. Open a command prompt, type cd
3. Type .\smigdeploy.exe, and then press Enter.
You have now installed the Windows Server Migration Tools and are ready to start migrating.
Migrating AD and DNS
An Active Directory Domain Services and DNS migration to Windows Server 2008 R2 can
be accomplished quickly and easily. In the following example, we migrate AD Domain
Services and DNS from a legacy domain controller to a Windows Server 2008 R2 system.
These procedures assume the Windows Server 2008 R2 system is a member server and that
you have used adprep.exe to prepare both the forest and domain. If this is not the case,
follow the steps earlier in this chapter before continuing on.
To migrate AD and DNS:
1. On the destination server, click Start, click Run, type DCPROMO, and then click OK.
2. On the Welcome page, check Use Advanced Mode Installation, and then click Next.
3. On the Operating System Compatibility page, click Next.
4. Click Existing Forest, confirm that the Add a Domain Controller to an Existing
ptg
Domain option is selected, and then click Next.
16
5. Type the domain name, and set the administrative credentials that will be used to
perform the installation if you are not already logged on as a domain admin.
6. Select or confirm the correct domain, and then click Next.
7. Select or confirm the correct site, and then click Next.
8. If the source server is a DNS server and a global catalog, leave DNS Server and Global
Catalog checked. If it is not a DNS server or a global catalog, uncheck the corre-
sponding role(s).
9. If prompted regarding delegation for this DNS server cannot be found, click Yes.
10. On the Install from Media page, click Next.
11. Select Use This Specific Domain Controller, select the source domain controller, and
then click Next.
12. Change or accept the default location for the system folders, and click Next.
13. Provide your Directory Service Restore mode administrator password, and click Next.
14. Review the summary and click Next.
15. Click Finish and restart the domain controller when complete.
16. On the source server, open a command prompt and type dnscmd /enumdirectory-
partitions. Note the partitions, as we will be using them on the target server in
the next step.
17. On the target server, open a command prompt and type dnscmd /enumdirectory-
partitions to confirm the same directory partitions exist and are enlisted.
518
CHAPTER 16
Migrating from Windows Server 2003/2008 to Windows Server
2008 R2
18. If either or both partitions are not listed, type dnscmd /enlistdirectorypartition
tition DomainDNSZones.companyabc.com.
19. On the source server, type net stop “dns server”.
20. Export the following Registry keys:
HKLM\System\CurrentControlSet\Services\DNS\Parameters and
HKLM\Software\Microsoft\WindowsNT\CurrentVersion\DNS Server.
21. From a command prompt, type xcopy %windir%\system32\dns C:\export /s.
22. If C:\export does not exist, type d when prompted to create the directory.
23. Delete the Samples folder that was just copied to C:\export as it’s not needed.
24. From a command prompt, type net start “dns server”.
25. On the target server, type Net stop “dns server”. Copy both exported Registry
keys to the target server, and then double-click them both to complete the import.
26. Copy the content of C:\Export from the source server to %windir%\system32\dns.
27. Type net start “dns server”.
NOTE
ptg
At this point, both domain controllers are online and servicing client authentication and
DNS requests. If the source domain controller is holding any FSMO roles, follow the
steps earlier in this chapter to move them to another DC.
NOTE
The next steps, which include migrating the IP configuration, can be done manually or
be done using the Windows Server Migration Tools. The process for installing and con-
figuring the tools on both servers is described in detail previously in this chapter.
28. On the source server, click Start, Administrative Tools, Windows Server Migration
Tools, right-click Windows Server Migration Tools, and click Run as Administrator.
29. Type Export-smigserversetting –ipconfig –path C:\export -verbose.
30. Provide a password when prompted.
31. Type ipconfig /all > C:\export\sourceIP.txt.
32. Copy the export file and sourceip.txt to your destination server.
33. Change the source server’s IP address to a different static IP.
34. On the destination server, click Start, Administrative Tools, Windows Server
Migration Tools, right-click Windows Server Migration Tools, and click Run As
Administrator.
35. Type import-smigserversetting –ipconfig ALL -sourcephysicaladdress
“
“
Multiple Domain Consolidation Migration
519
NOTE
This example assumes one network adapter on the source domain controller. For multi-
ple NICs, add a source and target physical address reference for each. This process is
described in more detail later in the chapter.
NOTE
Use sourceip.txt to get the physical address information from the source server
and use ipconfig /all in a separate command prompt to get it from the destina-
tion server.
36. Provide the password set during export when prompted.
37. Rename the source DC using the following command: netdom renamecomputer
%computername% /newname:
38. Rename the target DC using the same command, but change the
of the source DC’s old name.
39. Restart to complete the migration.
ptg
16
Migrating DHCP
DHCP server migration to Windows Server 2008 R2 can be accomplished quickly and
easily using the Windows Server Migration Tools. In the following example, we use the
Windows Server 2008 R2 Migration Tools to migrate DHCP server settings from a 32-bit
Windows Server 2003 SP2 server. The following steps assume you have already followed
the procedures for installing the Windows Server Migration Tools and have configured
both source and target servers. The overall process of using the Windows Server Migration
Tools to migrate DHCP services is as follows:
1. Verify the DHCP configuration on the source server is current and working correctly.
2. Click Start, Administrative Tools, Windows Server Migration Tools, right-click
Windows Server Migration Tools, and click Run As Administrator.
3. Type stop-service dhcpserver, and press Enter.
4. Type get-smigserverfeature, and press Enter.
NOTE
Get-SmigServerFeature is the command that scans the source computer for roles or
features supported for migration using the Windows Server Migration Tools.
5. Type export-smigserversetting -featureid dhcp –ipconfig –user ALL -group
-path
520
CHAPTER 16
Migrating from Windows Server 2003/2008 to Windows Server
2008 R2
NOTE
The –user and –group switches are optional and only used when migrating the DHCP
Administrators group membership. The –user switch is only used if there are local user
accounts listed as members.
6. Type a password when prompted, and press Enter to start the export.
7. After the export completes, move the export created in
server.
8. Unauthorize the source DHCP server.
9. On the target server, click Start, Administrative Tools, Windows Server Migration Tools.
10. Type import-smigserversetting –featureid dhcp –path
11. Type the password used to create the migration file earlier.
NOTE
The Windows Server Migration Tools installs the required roles and features to com-
plete the migration. In this case, the DHCP server role has been installed.
ptg
12. Confirm Success is marked as True to confirm migration is complete.
13. Type start-service dhcpserver.
14. Authorize the new DHCP server to complete the server migration.
Migrating IP Configuration
The Windows Server Migration Tools can be used to migrate the IP configuration from
your source Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2
server to your target Windows Server 2008 R2 system. The IP configuration migration can
be included in any other service migration by simply adding the –ipconfig switch to the
export-smigserversetting command.
The overall process of using the Windows Server Migration Tools to migrate DHCP services
is as follows:
1. On the source server, click Start, Administrative Tools, Windows Server Migration
Tools, right-click Windows Server Migration Tools, and click Run As Administrator.
2. Type Export-smigserversetting –ipconfig –path
3. Provide a password when prompted.
4. When the export is complete, you can copy the export file to your destination server
and then start the import process.
NOTE
Take a snapshot of your current IPConfig by typing ipconfig /all >
C:\ipconfig.txt. This can be used to verify settings postmigration if needed.
Multiple Domain Consolidation Migration
521
5. On the source server, change the IP address or disconnect it from the network.