Server 2012 R2 and Windows Server 2012 that installs the operating system without a GUI. With Server Core, you perform management tasks locally from the command line or remotely from another computer. Server Core is the default installation option for Windows Server 2012. Server Core has the following advantages over a traditional deployment of Windows Server 2012 or Windows Server 2012 R2:
MCT USE ONL
Y. STUDENT USE PROHIBITED
Upgrading Your Skills to MCSA Windows Server® 2012 1-9
• Reduced update requirements. Because Server Core installs fewer components, Server Core
deployments require the application of fewer software updates. This reduces the time that is required for an administrator to service Server Core.
• Reduced hardware footprint. Server Core computers require less RAM and less hard disk space. This means that when virtualized, more servers can be deployed on the same host.
Increasing numbers of Microsoft server applications are designed to run on computers that have Server Core installations. You can install Microsoft SQL Server® 2012 on computers running the Server Core
version of Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2.
There are two options for installing the Server Core version of Windows Server 2012 R2 and Windows Server 2012, as described in the following table.
Option Description
Server Core This is the standard deployment of Server Core. By default, all graphical administration components are in a Removed state. This means that Removed components occupy no disk space on the server. Server Core systems are managed locally by using command-line interface only, or can be managed by a remote system by using graphical administration tools.
You can convert to the full version of Windows Server 2012 R2 and Windows Server 2012 that includes the graphical administration components only if you have access to an installation source with all server files, such as a mounted WIM image. Any Server Core component in a Removed state can only be installed by using an installation source.
Server Core with Minimal Interface
This works the same as a deployment of Windows Server 2012 R2 and Windows Server 2012 Server with GUI. With this installation option, the graphical administration components are not in a Removed state. Instead, these components are available (they are located on the server’s disk), but not installed into the OS.
You can convert between Server Core with Minimal Interface and Windows Server 2012 R2 or Windows Server 2012 Server with a GUI by installing the graphical features. Because the component files have already been copied to the server’s disk, there is no need to specify installation media.
On a local connection, you can use the tools described in the following table to manage Server Core installations of Windows Server 2012 R2 and Windows Server 2012.
Tool Function
Cmd.exe Enables you to run traditional command-line utilities, such as Ping.exe and Ipconfig.exe.
PowerShell.exe Enables you to start a Windows PowerShell session on the Server Core deployment. You can then perform Windows PowerShell tasks as usual.
Sconfig.cmd Command-line menu driven administrative tool that enables you to perform most common server administrative tasks.
Notepad.exe Enables you to use the Notepad.exe text editor in the Server Core environment. Registry Editor Provides registry access within the Server Core environment.
Msinfo32.exe Enables you to view system information about the Server Core deployment. Taskmgr.exe Starts the Task Manager.
MCT USE ONL
Y. STUDENT USE PROHIBITED
1-10 Installing and Configuring Windows Server 2012
Note: If you accidentally close the Command Prompt window on a computer running Server Core, you can restore it by using this procedure:
1. Press Ctrl+Alt+Delete.
2. On the menu, click Task Manager.
3. On the File menu, click New Task (Run…). 4. Type cmd.exe and press Enter.
Server Core supports most, but not all, Windows Server 2012 R2 and Windows Server 2012 roles and features. You cannot install the following roles on a computer running Server Core:
• AD FS
• Application Server
• Network Policy and Access Services • Windows Deployment Services
Even if a role is available to a computer running the Server Core installation option, a specific role service associated with that role may not be available.
Note: You can check which roles are not available on Server Core by running the following query: Get-WindowsFeature | where-object {$_.InstallState -eq Removed}
Features on Demand is a feature introduced in Windows Server 2012 that you can use to remove the role and feature files (also termed the payload files) of roles and features that you will not use on a server as a way of conserving disk space. You can remove all payload files for unused roles and features by executing the following Windows PowerShell command:
Get-WindowsFeature | Where-Object {$_.Installed –eq $False} | Uninstall-WindowsFeature - Remove
If you have removed role and feature payload files and determine that you need to install one of the removed roles and features, you can mount the Windows Server 2012 install.wim file by using
Deployment Image Servicing and Management (DISM) and use it as the source location for installing the role or feature.
The Windows Server 2012 R2 and Windows Server 2012 administration model focuses on managing many servers from one console instead of the traditional method of managing each server separately. When you want to perform an administrative task, you are more likely to manage multiple computers running the Server Core operating system from one computer than connecting to each computer individually. You can enable Remote Management of a computer running Server Core by using sconfig.cmd or by executing the following command:
MCT USE ONL
Y. STUDENT USE PROHIBITED
Upgrading Your Skills to MCSA Windows Server® 2012 1-11