How to directly upgrade Win2008 R2 from Win2003 locally

Today, we're talking about issues related to a direct local upgrade from Windows 2003 to Windows Server 2008 R2. First look at Contoso's current architecture topology: Figure 1

At this point, the hardware configuration outdated Server B has been replaced by the new mainstream hardware configuration Server D. However, Server A still assumes such an important role as FSMO. According to the planning of the IT department, and in order to prevent possible upgrade failures, the five FSMO roles are transferred to Server D before upgrading Server A. Tips: The five FSMO roles are: PDC host, RID host, domain naming host, architecture host, and fabric host. They are owned by a single domain controller in the forest and in the domain within a specific forest and within a specific domain. Among them, the schema host and domain naming host are forest-level roles. Therefore, each forest has only one schema host and one domain naming master. RID hosts, PDC hosts, and infrastructure hosts are domain-level roles. Each domain has its own RID host, PDC host, and fabric host. 1. Prepare for the upgrade 1. Transfer 5 operations master roles There are two ways to transfer the FSMO role, one is graphical operation, and the other is to use NTDCUTIL. The command line operates. Here is a description of the transfer using the command line. For graphical operations, refer to Microsoft KB: http://support.microsoft.com/kb/324801/en-us Note: Ntdsutil.exe is a command to provide management facilities for Active Directory. Line tool. Use Ntdsutil.exe to perform database maintenance for Active Directory, manage and control individual host operations, create application directory partitions, and delete metadata left by domain controllers that have been successfully demoted by the Active Directory Installation Wizard (DCPromo.exe) . (1) Click [Start], [Run] in Server D, enter [CMD], and press Enter. (2) At the command prompt, type [ntdsutil] to enter [? 】You can view the help information. (3) As you can see in the help information, the [Roles] command can be used to manage the NTDS role owner token, type [Roles], and press Enter. (4) First connect to the domain controller of Windows Server 2008 R2 that will have the operation master role, type [Connections], enter [connect to server DC2], and enter [quit] to return to the previous menu. Figure 2

(5) Enter the command to transfer the corresponding host role. For example, if you want to transfer the PDC host now, enter [Transfer PDC], press Enter, a confirmation dialog will pop up, click [Yes], ie Start transferring roles. When complete, the location of the five operations master roles will be displayed. The other four characters are transmitted to DC2 in this way. (6) Confirm the operation host position after the transfer, re-run a command prompt, and enter the command [netdom query FSMO] to query the location of the current operation host role. Figure 3

2. Server A Upgrade Prerequisites (1) The operating system on the domain controller is Windows 2003 SP2 or higher. (2) Domain controller hardware exceeds Windows Server 2008 R2 requirements and all software is Windows Server 2008 R2 compliant, including anti-virus software and drivers. (3) There is enough disk free space to perform an upgrade of the operating system and Active Directory. In particular, ensure that the available space is at least twice the size of the Active Directory database, plus the minimum 32GB of space required to install the operating system. (4) The current domain functional level is Windows 2000 native mode or Windows 2003. Users cannot upgrade directly from Windows NT 4.0, Windows 2000 Mixed, or Windows 2003 transition domain controllers. Note: In this scenario, Server A colleagues are responsible for handling DNS and DHCP. The local upgrade will upgrade all DNS and DHCP components to Windows Server 2008 R2.

3. Server A upgrade hardware compatibility According to Microsoft's latest minimum hardware configuration requirements for Windows Server 2008 R2: 1.4GHz 64-bit processor 512MB memory 32GB free disk space 4. Check the application in Server A Compatibility If you find that some critical applications installed on Windows Server 2003 servers do not work properly in Windows Server 2008 R2, you may consider removing or migrating to other servers to avoid migration failures. It is also recommended to install all current critical updates and service packs on Server A. In addition to the application, the operating system version of Server A itself also needs to be considered. Supported and unsupported upgrade scenarios are listed below: Supported upgrade scenarios

Unsupported upgrade scenarios Upgrade from the following operating systems to Windows Server 2008 R2 is not supported: Windows(R) 95, Windows 98, Windows Millennium Edition, Windows XP, Windows Vista(R), Windows Vista Starter, or Windows 7 Windows NT(R) Server 4.0, Windows 2000 Server, Windows Server 2003 RTM, Windows Server 2003 with SP1, Windows Server 2003 Web, Windows Server 2008 R2 M3 or Windows Server 2008 R2 beta Windows Server 2003 for Itanium-based systems, Windows Server 2003 x64, Windows Server 2008 for Itanium-based systems, Windows Server for Itanium-based systems 2008 R2 does not support cross-architecture in-place upgrades (for example, upgrading from x86 to x64). Cross-language in-place upgrades are not supported (for example, upgrading from en-us to de-de). Cross-version upgrades are not supported (for example, from Windows Server 2008 Foundation SKUs to Windows Server 2008 Datacenter SKUs). In-place upgrades across build types are not supported (for example, upgrading from fre to chk). 5. Backup Server A backup is for quick recovery after system upgrade failure, especially in this scenario, you can perform a full system backup. Alternatively, Server A can use the latest virtualization technology P2V to the virtual machine, so that even if the physical machine fails to upgrade, as long as the virtual machine starts normally, it can replace the physical machine to provide services and is easy to maintain.

Second, perform a local upgrade on Server A After checking the necessary conditions for Server A, you can upgrade Server A. (1) Insert the installation CD of Windows Server 2008 R2 into Server A. (2) The installation page will pop up automatically, click [Install Now] (3) Select [Online to get the latest installation update], this will ensure that the installation program has the latest upgrade information. (4) I have multiple versions of the CD media here. According to the previous preconditions, select [Windows Server 2008 R2 Enterprise Full Installation], as shown in Figure 4.

(5) Agree to the license terms and click [Next]. (6) Select [Upgrade] here, as shown in Figure 5.

7) Check the compatibility report, the relevant warning information will be listed, click [Next] to continue. (8) The system then copies the file and restarts as a Windows Server 2008 R2 server. When all the files have been copied, the system is now upgraded to fully functional Windows Server 2008 R2. Figure 6

(9) After the last reboot, the installer will prepare for the first use, and then you can see the familiar Ctrl+Alt+Del unlock login screen. However, at this time Server A has become a domain controller running Windows Server 2008 R2. As shown in Figure 7

So far, Contoso has initially completed the upgrade from Windows 2003 to Windows Server 2008 R2 infrastructure, but not too happy, because there is still DHCP in the current domain to migrate, and The Exchange server needs to reassign the domain controller so that it can provide the service normally, and most importantly, only the functional level of the entire architecture is upgraded to Windows Server 2008 R2 to truly experience the difference in technology. If you want to know the following, please listen to the next decomposition.