NOTE NOTE 2008 R If either or both partitions are not listed, type dnscmd /enlistdirectorypartition

Transcription

1 518 CHAPTER 16 Migrating from Windows Server 2003/2008 to Windows Server 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. 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. 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 configuring 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 <sourcephysicaladdress1> -targetphysicaladdress <targetphysicaladdress1> -path <datapath> -verbose.

2 Multiple Domain Consolidation Migration 519 This example assumes one network adapter on the source domain controller. For multiple NICs, add a source and target physical address reference for each. This process is described in more detail later in the chapter. 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 can be accomplished quickly and easily using the Windows Server Migration Tools. In the following example, we use the Windows Server 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: 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. 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.

3 520 CHAPTER 16 Migrating from Windows Server 2003/2008 to Windows Server 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. 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 server to your target Windows Server 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. Take a snapshot of your current IPConfig by typing ipconfig /all > C:\ipconfig.txt. This can be used to verify settings postmigration if needed.

4 Multiple Domain Consolidation Migration 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. 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. The tools at your disposal for this job are the Printer Migration Wizard or the printbrm.exe command-line utility. 16 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. 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.

5 522 CHAPTER 16 Migrating from Windows Server 2003/2008 to Windows Server 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. 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. Summary Although Windows Server 2003/2008 and Windows Server are close cousins in the operating system family tree, there are some compelling reasons to upgrade to Windows Server Active Directory Domain Services. The evolutionary nature of Windows Server makes performing this procedure more straightforward because the upgrade does not require major changes to Active Directory architecture or the operating system design.