文書番号: 000135444
Article Summary: This article addresses how to perform a server to server migration of the operating system
This article is designed to provide a step by step walkthrough of the migration of a server running Windows Server 2008 R2 with the Active Directory Domain Services (ADDS) role installed and acting as a domain controller to as server running Windows Server 2012 R2. The migration includes migrating the Active Directory (AD) environment, Domain Naming System (DNS) and Dynamic Host Configuration Protocol (DHCP). The migration is designed to migrate everything with zero downtime in the environment allowing clients to continue to operate uninterrupted. The roles will be added and configured on to the server running Windows Server 2012 R2. The goal is to retire the server running Windows Server 2008 R2.
The current environment is configured as follows.
Hardware - Dell PowerEdge 1950
Operating System - Windows Server 2008 R2
Computer Name - W08R2-DC
Roles - ADDS, DNS, DHCP
IP Address - 192.168.0.1
Domain - domain.local
DHCP Scope - Client-Scope
Hardware - Dell PowerEdge R820
Operating System - Windows Server 2012 R2
Computer Name - W12R2-DC
IP Address - 192.168.0.2
This document can be used as a reference for performing a migration in a customer environment. Simply substitute the following information throughout the document.
W08R2-DC = customers' existing domain controller computer name
W08R2-DC IP address = customers' existing domain controller IP address
W08R2-DC DHCP scope = customers' existing DHCP scope
W12R2-DC = customers' new computer name
W12R2-DC IP address = customers' new server IP address
domain.local = customers' forest/domain name
1. Prepare the existing AD environment for the migration to the new server by upgrading the schema using adprep.exe. Log on to W08R2-DC as domain Administrator, open elevated command prompt and perform the following steps.
a. Press the Windows Logo+R, type runas /user:administrator@domain.local where domain.local is replaced by the name of the Active Directory domain and press Enter.
b. Enter the Administrator account password when prompted and press Enter.
c. Type d:\support\adprep\adprep.exe /forestprep and press Enter.
d. Type C to confirm the to upgrade the schema to version 69, Windows Server 2012 R2, and press Enter.
2. Install ADDS on W12R2-DC.
a. Open Server Manager by pressing Windows Logo+R, type servermanager.exe and press Enter. The same task can be accomplished by pressing Windows Logo and selecting Server Manager on the left side of the screen.
b. Click Add roles and features in the Dashboard under Configure this local server.
c. Click Next on Before You Begin.
d. Select Role-based or feature-based installation for Installation Type and click Next.
e. Select W12R2-DC on the Server Selection page and click Next.
f. Click Active Directory Domain Services to install it, click Add Features when prompted and click Next.
g. Click Next on Features.
h. Click Next on ADDS.
i. Click Install on Confirmation.
3. Promote W12R2-DC to a domain controller in the domain.local forest.
a. Click the refresh icon in the top center of the Dashboard in Server Manager and a Post-deployment Configuration notification will appear.
b. Click Promote this server to a domain controller to begin the Active Directory Domain Services Configuration Wizard.
c. Ensure Add a domain controller to an existing domain is checked and type the domain name in Domain:.
d. Click Change... next to Supply the credentials to perform this operation and type Administrator@domain.local where domain.local is the fully qualified domain name (FQDN) of the actual domain. Enter the Administrator password.
e. Type the Directory Restore Mode (DSRM) password, confirm it and click Next on Domain Controller Options.
f. Click Next on DNS Options.
g. Click Next on Additional Options.
h. Click Next on Paths.
i. Click Next on Preparation Options.
j. Click Next on Review Options.
k. Click Install on Installation to complete the wizard. The server will reboot upon completion.
4. Transfer the Domain naming operations master Flexible Single Master Operations (FSMO) role from W08R2-DC to W12R2-DC.
a. Open Server Manager by pressing Windows Logo+R, type servermanager.exe and press Enter. The same task can be accomplished by pressing Windows Logo and selecting Server Manager on the left side of the screen.
b. Click the Tools menu in the upper right of Dashboard in Server Manager and select Active Directory Domains and Trusts.
c. Right-click on Active Directory Domains and Trusts and choose Change Active Directory Domain Controllers. Click on W12R2-DC and click OK.
d. Right-click on Active Directory Domains and Trusts and choose Operations Master.... Click Change, acknowledge Yes to change the Domain naming operations master FSMO to W12R2-DC and click OK to complete the task.
5. Transfer the RID, PDC and Infrastructure FSMO roles to W12R2-DC.
a. Open Server Manager by pressing Windows Logo+R, type servermanager.exe and press Enter. The same task can be accomplished by pressing Windows Logo and selecting Server Manager on the left side of the screen.
b. Click the Tools menu in the upper right of Dashboard in Server Manager and select Active Directory Users and Computers.
c. Right-click on the domain name in Active Directory Users and Computers and choose Change Active Directory Domain Controllers. Click on W12R2-DC and click OK.
d. Right-click on the domain name Active Directory Users and Computers and choose Operations Master.... Click Change on the RID tab, acknowledge Yes to change the RID FSMO role to W12R2-DC and click OK to complete the task. Perform the same task on the PDC and Infrastructure FSMO roles.
6. Transfer the Schema master FSMO role from W08R2-DC to W12R2-DC.
a. Press Windows Logo+R, type regsvr32 schmmgmt.dll and press Enter. Acknowledge the successful registration of the .dll by clicking OK.
b. Windows Logo+R, type mmc and press Enter to open the Microsoft Management Console (MMC).
c. Click File, select Active Directory Schema under Available snap-ins:, click Add and click OK to add the snap-in to the MMC.
d. Right-click on the domain name in the MMC and choose Change Active Directory Domain Controllers. Click on W12R2-DC and click OK. Acknowledge the message.
e. Right-click on the domain name the MMC and choose Operations Master.... Click Change, acknowledge Yes to change the Schema master FSMO role to W12R2-DC and OK to complete the task.
7. Install the DHCP Server role on W12R2-DC. Complete steps a through I in section 2 above and install DHCP Server.
8. Migrate the DNS role from W08R2-DC to W12R2-DC.
a. On W12R2-DC open the Network Connections Control Panel tool by pressing the Windows Logo+R, type ncpa.cpl and press Enter.
b. Right-click on the Network Interface Card (NIC) and click Properties.
c. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
d. Change the Preferred DNS server: to 192.168.0.2 and click OK to complete the change.
e. On W08R2-DC press Windows Logo+R, type dhcpmgmt.msc and press Enter.
f. In DHCP under IPv4 select Server Options and double-click on 006 DNS Server under Option Name.
g. Click Remove under IP Address, change the IP address to 192.168.0.2 and click Add to complete the process. Acknowledge any messages that appear.
h. Perform steps a through d in this section on W08R2-DC.
9. Migrate the DHCP role from W08R2-DC to W12R2-DC. Perform the following steps on W12R2-DC.
a. Press Windows Logo, type Windows PowerShell, right-click on Windows PowerShell and click Run as administrator to open Windows PowerShell.
b. Type md c:\export and press Enterto create a new folder named export on c:
c: Type md c:\export\backup and press Enter to create a new folder named backup on c:\export.
d. Type Export-DhcpServer -ComputerName W08R2-DC.domain.local -Leases -File c:\export\leases.xml -verbose and press Enter to export the leases.
e. Type Import-DhcpServer -ComputerName W12R2-DC.domain.local -Leases -File c:\export\leases.xml -verbose and press Enter to import the leases.
f. Open Server Manager by pressing Windows Logo+R, type servermanager.exe and press Enter. The same task can be accomplished by pressing Windows Logo and selecting Server Manager on the left side of the screen.
g. Click the Tools menu in the upper right of Dashboard in Server Manager and select DHCP.
h. Right-click on DHCP, choose Add Server, click This authorized DHCP server and click OK to add the server.
i. Right-click on W08R2-DC.domain.local, click Unauthorize and acknowledge Yes.
j. Right-click on W12R2-DC.domain.local, click Authorize and acknowledge Yes.
k. Click on W12R2-DC.domain.local, click Action, click All Tasks and click Restart to restart the DHCP service.
10. Run the Active Directory Domain Services Configuration Wizard on W08R2-DC and demote it.
a. Press Windows Logo+R, type dcpromo and press Enter. Acknowledge the global catalog message.
b. Click Next on Delete the Domain.
c. Type the Administrator Password, confirm it and click Next.
d. Click Next on Summary.
e. Click Reboot on completion
11. Remove W08R2-DC from the domain.
a. Log on to the server using the local Administrator account. Press the Windows Logo+R, type sysdm.cpl and press Enter to open System Properties.
b. Click Change....
c. Click Workgroup:, enter a WORKGROUP name and click OK.
d. Click OK to accept the Computer Name/Domain Changes dialog box.
e. Click OK to accept the Computer Name/Domain Changes dialog box.
f. Click Close.
g. Click Restart Now to restart the server.
Microsoft Windows 2012 Server R2, Microsoft Windows 2008 Server R2, Microsoft Windows 2012 Server, DSS 2500, DSS 7500, DSS 8440, DSS 9000J, DSS 9000R, DSS 9600, DSS 9620, DSS 9630, DSS 1500, DSS 1510, DSS 7000, PowerApp 100, PowerApp 110, PowerApp 120, PowerApp 200, PowerApp 220, PowerApp w100 web, Dell vStart 50, Dell vStart v1000, Dell vStart v200, PowerEdge XR2, PowerEdge 1300, PowerEdge 1400SC, PowerEdge SC1420, PowerEdge SC1425, PowerEdge SC1430, PowerEdge SC1435, PowerEdge 1500SC, PowerEdge 1550, PowerEdge 1600SC, PowerEdge 1650, PowerEdge 1655MC, PowerEdge 1750, PowerEdge 1800, PowerEdge 1850, PowerEdge 1855, PowerEdge 1900, PowerEdge 1950, PowerEdge 1955, PowerEdge 2100, PowerEdge 2200, PowerEdge 2300, PowerEdge 2400, PowerEdge 2450, PowerEdge 2500, PowerEdge 2500SC, PowerEdge 2550, PowerEdge 2800, PowerEdge 2850, PowerEdge 2900, PowerEdge 2950, PowerEdge 2970, PowerEdge 300, PowerEdge 300SC, PowerEdge 3250, PowerEdge 350, PowerEdge 400SC, PowerEdge 4100, PowerEdge 4300, PowerEdge 4350, PowerEdge 4400, PowerEdge SP 4__, PowerEdge XE 4__, PowerEdge 500SC, PowerEdge XL 5133-4, PowerEdge 600SC, PowerEdge 6300, PowerEdge 6350, PowerEdge 6400, PowerEdge 6450, PowerEdge 650, PowerEdge 6800, PowerEdge 6850, PowerEdge 6950, PowerEdge 700, PowerEdge 7150, PowerEdge 7250, PowerEdge 750, PowerEdge 800, PowerEdge 830, PowerEdge 840, PowerEdge 8450, PowerEdge 850, PowerEdge 860, PowerEdge C1100, PowerEdge C2100, PowerEdge C410X, PowerEdge C4130, PowerEdge C4140, PowerEdge C5000, PowerEdge C5125, PowerEdge C5220, PowerEdge C5230, PowerEdge C6100, PowerEdge C6105, PowerEdge C6145, PowerEdge C6220, PowerEdge C6220 II, PowerEdge C6300, PowerEdge C6320, PowerEdge C6320p, PowerEdge C6400, PowerEdge C6420, PowerEdge C6525, PowerEdge C8000, PowerEdge EL, PowerEdge External Media System 1434, PowerEdge External Media System 1634, PowerEdge External Media System 753, PowerEdge FC430, PowerEdge FC630, PowerEdge FC640, PowerEdge FC830, PowerEdge FD332, PowerEdge FM120x4 (for PE FX2/FX2s), PowerEdge FX2/FX2s, PowerEdge M1000E, PowerEdge M420, PowerEdge M520, PowerEdge M520 (for PE VRTX), PowerEdge M600, PowerEdge M605, PowerEdge M610, PowerEdge M610x, PowerEdge M620, PowerEdge M620 (for PE VRTX), PowerEdge M630, PowerEdge M630 (for PE VRTX), PowerEdge M640, PowerEdge M640 (for PE VRTX), PowerEdge M710, PowerEdge M710HD, PowerEdge M805, PowerEdge M820, PowerEdge M820 (for PE VRTX), PowerEdge M830, PowerEdge M830 (for PE VRTX), PowerEdge M905, PowerEdge M910, PowerEdge M915, PowerEdge MX5016s, PowerEdge MX7000, PowerEdge MX740c, PowerEdge MX840c, PowerEdge R200, PowerEdge R210, PowerEdge R210 II, PowerEdge R220, PowerEdge R230, PowerEdge R240, PowerEdge R300, PowerEdge R310, PowerEdge R320, PowerEdge R330, PowerEdge R340, PowerEdge R410, PowerEdge R415, PowerEdge R420, PowerEdge R420xr, PowerEdge R430, PowerEdge R440, PowerEdge R510, PowerEdge R515, PowerEdge R520, PowerEdge R530, PowerEdge R530xd, PowerEdge R540, PowerEdge R610, PowerEdge R620, PowerEdge R630, PowerEdge R640, PowerEdge R6415, PowerEdge R6515, PowerEdge R6525, PowerEdge R710, PowerEdge R715, PowerEdge R720, PowerEdge R720xd, PowerEdge R730, PowerEdge R730xd, PowerEdge R740, PowerEdge R740xd, PowerEdge R740xd2, PowerEdge R7415, PowerEdge R7425, PowerEdge R7515, PowerEdge R7525, PowerEdge R805, PowerEdge R810, PowerEdge R815, PowerEdge R820, PowerEdge R830, PowerEdge R840, PowerEdge R900, PowerEdge R905, PowerEdge R910, PowerEdge R920, PowerEdge R930, PowerEdge R940, PowerEdge R940xa, PowerEdge SDS 100 (Storage System), PowerEdge SP 5__, PowerEdge SP 5__-2, PowerEdge SP 51__-2 (ATI Mach64), PowerEdge SP 575-2, PowerEdge T100, PowerEdge T105, PowerEdge T110, PowerEdge T110 II, PowerEdge T130, PowerEdge T140, PowerEdge T20, PowerEdge T30, PowerEdge T300, PowerEdge T310, PowerEdge T320, PowerEdge T330, PowerEdge T340, PowerEdge T40, PowerEdge T410, PowerEdge T420, PowerEdge T430, PowerEdge T440, PowerEdge T605, PowerEdge T610, PowerEdge T620, PowerEdge T630, PowerEdge T640, PowerEdge T710, PowerEdge VRTX, PowerEdge Web Server, PowerEdge XE2420, PowerEdge XE 5__, PowerEdge XE 5__-2, PowerEdge XE 51__-2 (ATI Mach64), PowerEdge XE7100, PowerEdge XE7420, PowerEdge XE7440, PowerEdge 2600, PowerEdge 2650, PowerEdge 6600, PowerEdge 6650, PowerEdge 4600, PowerEdge SC 420, PowerEdge SC 430, PowerEdge SC 440
21 2月 2021
3
Solution