![]() Make sure the BuildLabEx value says you're running Windows Server 2008 R2. You can't have any virtual machines running during the in-place upgrade. You must also Shut down, Quick migrate, or Live migrate any virtual machines currently running on the server. Open the Registry Editor, go to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion hive, and then copy and paste the Windows Server BuildLabEx (version) and EditionID (edition) into the same location as above.Īfter you've collected all of your Windows Server-related information, we highly recommend that you backup your operating system, apps, and virtual machines. Type ipconfig /all into the command prompt, and then copy and paste the resulting configuration information into the same location as above. Open a command prompt, go to c:\Windows\system32, and then type systeminfo.exe.Ĭopy, paste, and store the resulting system information somewhere off of your device. Because this information is intended for use only if your upgrade fails, you must make sure that you store the information somewhere that you can get to it off of your device. Before you begin your in-place upgradeīefore you start your Windows Server upgrade, we recommend that you collect some information from your devices, for diagnostic and troubleshooting purposes. To upgrade to Windows Server 2019, use this topic first to upgrade to Windows Server 2012 R2, and then upgrade from Windows Server 2012 R2 to Windows Server 2019. ![]() This article helps you to move from Windows Server 2008 R2 to Windows Server 2012 R2. An in-place upgrade allows you to go from an older operating system to a newer one, while keeping your settings, server roles, and data intact. If you want to keep the same hardware and all the server roles you've already set up without flattening the server, you'll want to do an in-place upgrade.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |