Install Windows Server 2012 R2 - MCSA Windows Server 2012 R2: Installation and Configuration Study Guide - page 19

To convert from a Windows 2012 or Windows Server 2012 R2 Server Core system to
Server with a GUI mode, run this code snippet (a restart is required):
Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart
To convert from Server Core mode to Server with a GUI mode, follow these steps when the
server is initially installed in Server Core mode:
1. Determine the index number for a server with a GUI image (for example, SERVERDATA-
CENTER , not SERVERDATACENTERCORE ) using this cmdlet:
Get-WindowsImage -ImagePath path to wim\install.wim
2. Run this line of code:
Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart
-Source wim: path to wim\install.wim: Index # from step 1
3. Alternatively, if you want to use Windows Update as the source instead of a WIM file,
use this Windows PowerShell cmdlet:
Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart
After you have completed the management tasks, you can switch the server back to Server
Core mode whenever it is convenient (a restart is required) with this Windows PowerShell
cmdlet:
Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -restart
NIC Teaming
NIC Teaming , also known as load balancing and failover (LBFO) , gives an administrator
the ability to allow multiple network adapters on a system to be placed into a team. Inde-
pendent hardware vendors (IHVs) have required NIC Teaming, but until Windows Server
2012, NIC Teaming was not part of the Windows Server Operating System.
To be able to use NIC Teaming, the computer system must have at least one Ethernet
adapter. If you want to provide fault protection, an administrator must have a minimum of
two Ethernet adapters. One advantage of Windows Server 2012 R2 is that an administrator
can setup 32 network adapters in a NIC Team.
NIC Teaming is a very common practice when setting up virtualization. It is one way
that you can have load balancing with Hyper-V.
NIC Teaming gives an administrator the ability to allow a virtual machine to use virtual
network adapters in Hyper-V. The advantage of using NIC Teaming in Hyper-V is that
the administrator can use it to connect to more than one Hyper-V switch. This allows
Hyper-V to maintain connectivity even if the network adapter under the Hyper-V switch
gets disconnected.
An administrator can configure NIC Teaming in either Server Manager or PowerShell.