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 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 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 <folderpath>.
|
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:
1. | Copy <folderpath>\SMT_WS03_x86 from the
target server to the source server.
| 2. | Open a command prompt, type cd
<folderpath>\SMT_WS03_x86, and then press Enter.
| 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.
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 Domain option is selected, and then click
Next.
| 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 corresponding 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
/enumdirectorypartitions. 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
/enumdirectorypartitions to confirm the same directory partitions
exist and are enlisted.
| 18. | If either or both partitions are not listed, type dnscmd
/enlistdirectorypartition <FullyQualifiedDirectoryPartition>,
for example, dnscmd /enlistdirectorypartition
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
The next steps, which
include migrating the IP configuration, can be done manually or be done
using the Windows Server Migration Tools.
| 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 "<sourcephysicaladdress1>"
-targetphysicaladdress "<targetphysicaladdress1>" -path
<datapath> -verbose.
Note
This example assumes one network adapter on
the source domain controller. For multiple NICs, add a source and target
physical address reference for each.
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 destination server.
| 36. | Provide
the password set during export when prompted.
| 37. | Rename the source DC using the following command: netdom
renamecomputer %computername% /newname:<NewName>.
| 38. | Rename the target DC using the same command, but change
the <NewName> to that of the source DC’s old name.
| 39. | Restart to complete the migration.
|
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 <folderpath>
-verbose.
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 <folderpath>
to the target 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
<folderpath> -verbose.
| 11. | Type the password used to create the migration file
earlier.
Note
The Windows Server
Migration Tools installs the required roles and features to complete the
migration. In this case, the DHCP server role has been installed.
| 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
<datapath> -verbose.
| 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.
| 5. | On
the source server, change the IP address or disconnect it from the
network.
| 6. | On the
target server, click Start, Administrative Tools, Windows Server
Migration Tools, right-click Windows Server Migration Tools, and click
Run As Administrator.
| 7. | Type import-smigserversetting –ipconfig ALL
-sourcephysicaladdress
"<sourcephysicaladdress1>","<sourcephysicaladdress2>"
-targetphysicaladdress
"<targetphysicaladdress1>","<targetphysicaladdress2>" -path
<datapath> -verbose.
| 8. | When prompted, provide the password set during export.
Note
You must specify the physical
mapping for each adapter indicated by <sourcephysicaladdress1>
and <targetphysicaladdress1>.
Use the physical address for each adapter where indicated.
| 9. | A restart
is required for some of the settings to take effect.
|
Migrating Print
Services
Migrating printer settings
from an older environment can be accomplished by first exporting print
queues, printer ports, and settings before importing them to Windows
Server 2008 R2. The tools at your disposal for this job are the Printer
Migration Wizard or the printbrm.exe command-line utility.
Note
Migrating printer settings
directly from Windows 2000 servers and older using the Printer Migration
Wizard or the printbrm.exe command-line
tool is not supported. An interim migration to Windows Server 2003 or
2008 is required before migrating to Windows Server 2008 R2.
The Printer Migration
Wizard gives you the graphical user interface that walks you through the
migration process. This is the easiest method of migrating printers.
The steps to migrate print servers are as follows:
1. | Open
Print Management (Start, Administrative Tools).
| 2. | If not already there, add the remote print server using
add/remove servers.
| 3. | Right-click on the remote server and select Export
Printers to a File to launch the Printer Migration Wizard.
| 4. | Review the list of items to be exported, and then click
Next.
| 5. | Browse to
the location on the local server to save the export file, and click
Next.
| 6. | Click
Finish when the export is complete.
| 7. | Still in Print Management, right-click on the
target server, and click Import Printers from a File to launch the
Printer Migration Wizard.
| 8. | Browse to the export file location on the local server,
click Open, and click Next.
| 9. | Review the list of items to be imported, and click Next.
| 10. | Select Import mode, specifying if you want to overwrite
or keep existing printers.
| 11. | Select List in the Directory to specify your preferences
for listing the imported printers in the Active Directory.
| 12. | Check Convert LPR Ports to Standard Port Monitors if
you want to take advantage of the faster Standard Port Monitor.
| 13. | Click Next to start the import.
| 14. | When the import has completed, click Finish.
|
Note
For
in-place-upgrades, use the Printer Migration Wizard to export printer
settings before the upgrade and then import printer settings back to the
same server after the upgrade has completed.
An alternative method of
migrating the printer servers is to use the command-line utility printbrm.exe. This utility is not as “pretty” to use as the Printer
Migration Wizard, but it allows you to automate the migration process
and reduces the number of steps. The steps to migrate using the command
line are as follows:
1. | On the
target server, click Start, All Programs, Accessories, then right-click
Command Prompt and select Run As Administrator.
| 2. | Type CD %Windir%\system 32\spool\tools and
then press Enter.
| 3. | Type printbrm
-s \\<SourceServer>\ -b -f <filename>.printerexport
and then press Enter.
| 4. | Type printbrm -s \\<TargetServer>\ -r -f
<filename>.printerexport and then press Enter.
|
|
