Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Windows Server Installation Options
In this articleApplies To: Windows Server 2012 R2, Windows Server 2012 This document summarizes the differences between the installation options available for Windows Server® 2012, including the features that are installed with each option, the management options available after installation, and how to switch between the installation options during use. It also explains the differences between the Server Graphical Shell and the Minimal Server Interface and how to switch between them. In addition, it discusses how to use Features on Demand to further reduce the disk footprint by including the binary files for only the server roles you actually use. Installation options descriptionWhen you install Windows Server 2012, you can choose between Server Core Installation and Server with a GUI. The “Server with a GUI” option is the Windows Server 2012 equivalent of the Full installation option available in Windows Server 2008 R2. The “Server Core Installation” option reduces the space required on disk, the potential attack surface, and especially the servicing requirements, so we recommend that you choose the Server Core installation unless you have a particular need for the additional user interface elements and graphical management tools that are included in the “Server with a GUI” option. For this reason, the Server Core installation is now the default. Because you can freely switch between these options at any time later, one approach might be to initially install the Server with a GUI option, use the graphical tools to configure the server, and then later switch to the Server Core Installation option. An intermediate state is possible where you start with a Server with a GUI installation and then remove Server Graphical Shell, resulting in a server that comprises the “Minimal Server Interface,” Microsoft Management Console (MMC), Server Manager, and a subset of Control Panel. See the “Minimal Server Interface” section of this document for more information. In addition, after installation of either option is complete, you can completely remove the binary files for server roles and features that you do not need, thereby conserving disk space and reducing the attack surface still further. See the “Features on Demand” section of this document for more information. A server in Minimal Server Interface mode is about 300 MB smaller than the same server in Server with a GUI mode. A server in Server Core mode is about 4 GB smaller than the same server in Server with a GUI mode. For the smallest possible installation footprint, start with a Server Core installation and then completely remove any server roles or features you do not need by using Features on Demand. If you choose the Server Core Installation optionWith this option, the standard user interface (the “Server Graphical Shell”) is not installed; you manage the server using the command line, Windows PowerShell, or by remote methods.
To use Windows PowerShell to convert from a Server Core installation to a Server with a GUI installation
If you choose the Server with a GUI optionWith this option, the standard user interface and all tools are installed. Server roles and features are installed with Server Manager or by other methods.
If you initially install with the Server with a GUI option and then use the above command to convert to a Server Core installation, you can later revert to a Server with a GUI installation without specifying a source. This is because the necessary files remain stored on the disk, even though they are no longer installed. For more information, and for instructions to completely remove the Server with a GUI files from disk, see the “Features on Demand” section of this document. If you convert to a Server Core installation, Windows features, server roles, and GUI management tools that require a Server with a GUI installation will be uninstalled automatically. You can specify the -WhatIf option in Windows PowerShell to see exactly which features will be affected by the conversion. Note If the server has been in Server Core mode and then you switch to Server with a GUI mode, clicking a tile in the Start Screen that starts Internet Explorer will result in an error reading “This app can’t open.” To fix this, go to Internet Options and select Open Internet Explorer Tiles on the Desktop. Minimal Server InterfaceIn Windows Server 2012, you can remove the Server Graphical Shell, resulting in the “Minimal Server Interface.” This is similar to a Server with a GUI installation, but Internet Explorer 10, Windows Explorer, the desktop, and the Start screen are not installed. Microsoft Management Console (MMC), Server Manager, and a subset of Control Panel are still present. Starting with a Server with a GUI installation, you can convert to the Minimal Server Interface at any time using Server Manager. Note When you change any of these options, you will have to restart the server for the change to take effect. See the table below for a summary of which selections to make in Server Manager (or cmdlets to use in Windows PowerShell) in order to get a given installation state:
Features on DemandIn previous versions of Windows, even if a server role or feature was disabled, the binary files for it were still present on the disk, consuming space. In Windows Server 2012, not only can you disable a role or feature, but you can also completely remove its files, a state shown as “removed” in Server Manager or “disabled with payload removed” in Dism.exe. To reinstall a role or feature that been completely removed, you must have access to an installation source. To completely remove a role or feature, use –Remove with the Uninstall-WindowsFeature cmdlet of Windows PowerShell. For example, to completely remove Windows Explorer, Internet Explorer, and dependent components, run the following Windows PowerShell command: Uninstall-WindowsFeature Server-Gui-Shell -Remove To install a role or feature that has been completely removed, use the Windows PowerShell –Source option of the Install-WindowsFeature Server Manager cmdlet. The –Source option specifies a path to a WIM image and the index number of the image. If you do not specify a –Source option, Windows will use Windows Update by default. Offline VHDs cannot be used as a source for installing roles or features which have been completely removed. Only component sources from the exact same version of Windows are supported. For example, a component source derived from the Windows Server Developer Preview is not a valid installation source for a server running Windows Server 2012. To install a removed role or feature using a WIM image, use the steps and Windows PowerShell cmdlets:
For example: Install-WindowsFeature <featurename> -Source wim:d:\sources\install.wim:4 You can also specify a source for servers that are domain members using Group Policy. Navigate to Computer Configuration > Administrative Templates > System > “Specify settings for optional component installation and component repair” Note Permissions might affect the system’s ability to access Windows features for installation over a network. The Trusted Installer process runs within the machine account. If you encounter network access issues, try issuing a net use command (for example, net use * \path\to\network or the cmdlet New-PSDrive -Name Z -PSProvider Filesystem -Root "\path\to\network) to mount the network source and then copy the source locally. Then use the local copy as the installation source. Practical applicationsThese examples give you an idea of how you can choose the installation option that might be most appropriate for your deployment needs:
Reference tableThis table summarizes which features are available locally depending on which installation option you choose.
See alsoFor detailed information about working with a server in Server Core mode, see Configure and Manage Server Core Installations. 1.5 What step should you take before upgrading or migrating to a new operating system?3 Things to do before upgrading to a new operating system. Check application compatibility. Application compatibility can become a problem when migrating to a newer OS. ... . Identify and replace discontinued features. ... . Avoid Extended Security Updates if possible. ... . Plan ahead for the future.. Which edition of Windows 7 contains the same features as Ultimate Edition except that it is used by companies with volume licensing?Ultimate is the no-compromise SKU for those who want all Windows features, including business. It has the same features as the Enterprise Edition but is licensed differently. Customers can buy Ultimate preinstalled from OEMs or as a retail upgrade.
What Windows 7 utility has been added back into Windows 10 to help you migrate data?Transfer via a File History backup
Windows 7 through Windows 10 have a built-in backup utility that lets you restore a PC's folder and files — but not settings or applications. You can use the Windows backup feature to restore files from an old PC to a new one. Windows calls this facility File History.
What essential part of the operating system communicates with the BIOS device drivers resource managers and Apis to coordinate operating system functions?The core of an operating system that coordinates system functions is referred to as the CPU.
|