16.0k views
3 votes
The IT Department already has been testing Windows Server 2012 R2, and some time ago purchased licenses to convert all of its Windows Server 2008 Enterprise Edition servers to Windows Server 2012 R2 Enterprise Edition. Two of the servers are running the Server Core installation of Windows Server 2008. Two other servers are running the 32-bit edition of Windows Server 2008. Management wants all servers to run the Server with a GUI installation. a. Explain the general process the IT department must follow to convert to Windows Server 2012 R2. Include any caveats or problems they might encounter.

1 Answer

6 votes

Final answer:

To convert to Windows Server 2012 R2, the IT department must perform either an in-place upgrade or a clean installation, depending on server setup. They must back up data, check compatibility, and potentially update hardware. Post-upgrade actions include driver updates, service packs, and restoring configurations.

Step-by-step explanation:

To convert from Windows Server 2008 to Windows Server 2012 R2, the IT department needs to perform an upgrade or a clean installation. For servers running the Server Core installation or those running a 32-bit edition, a clean install is mandatory since an in-place upgrade is not supported for a change from a core to GUI version or from 32-bit to 64-bit.

Here is a general process outline:

  1. Backup all data and server configurations.
  2. Check system and software compatibility with Windows Server 2012 R2.
  3. Obtain necessary hardware updates if required.
  4. For servers eligible for an in-place upgrade, run the Windows Server 2012 R2 setup and select ‘Upgrade’.
  5. For servers requiring clean installation, create bootable media, boot from this media, and follow the installation prompts to install the Windows Server with a GUI option.
  6. Post-installation, update all device drivers and validate the installation. Install all necessary service packs and updates.
  7. Restore data and server configurations from backups.

Caveats to consider include potential incompatibility of applications with the new operating system, the requirement for new device drivers, and the necessity to review licensing arrangements post-upgrade. Additionally, any custom settings or roles from the previous installation will need to be manually reconfigured after a clean install.

User Ralight
by
6.2k points