- Turn the tables on your organization with Adaxes 2018.1’s Web Interface and reporting capabilities - Thu, Sep 20 2018
- Review: Softerra Adaxes – Automating Active Directory management - Thu, Jun 4 2015
- Azure Multi-Factor Authentication – Part 8: Delegating Administration - Tue, Apr 28 2015
Just as in Windows Server 2008 and Windows Server 2008 R2, you can run Windows Server 2012 as a Server Core installation. Opposed to the Server with a GUI installation option, a Server Core installation is stripped of non-essential Windows components, like Internet Explorer and Windows Media Player. It also doesn’t feature the familiar Graphical User Interface (GUI). When you log on for the first time, you won’t see the familiar Task Bar at the bottom of your screen, or any of the desktop items; instead, you will be presented with the following command prompt:
Windows Server 2012 - Server Core Desktop
While this sight might seem daunting at first, a lot of the same tools from the Server with a GUI are available to you by default. Many of the Server Roles and Features are also available. I will cover all that in my next posts, but today I want to discuss why you would want to choose Server Core instead of Server with a GUI.
When you choose Server Core instead of Server with a GUI, you will benefit in the following ways:
Server Core installations have a smaller disk foot print ^
In contrast to a Server with a GUI, a Server Core installation requires less disk space. In Windows Server 2012, compared to Windows Server 2008 and Windows Server 2008 R2, the difference in disk foot print between these two installation options has diminished, but it is still significant.
Although a smaller disk foot print is not a goal in itself, it does mean a smaller attack surface. Also, in today’s virtual world, a Server Core installation is deployed and backed up faster than a Server with a GUI. This makes deploying new servers a breeze.
Server Core installations require less RAM ^
While data deduplication might make the previous argument irrelevant, a Server Core installation also requires less Random Access Memory (RAM) to run. Although any Windows Server 2012 installation needs to be equipped with 512MB of RAM for installation, you can throttle back the amount of RAM toward the actual amount of RAM required. I’ve been running virtual Server Core Domain Controllers with 185MB of RAM. Now imagine what you could do with your virtual environment when you have loads of RAM available.
Server Core installations get fewer updates ^
Because non-essential Windows components are absent, these components do not need to be patched. Microsoft releases updates on the second Tuesday of each month during its “Patch Tuesday,” but many of these updates apply to non-essential components like Internet Explorer instead of the Windows kernel.
Looking at Server Core installations of Windows Server 2008 and Windows Server 2008 R2 in the past four years, many “Patch Tuesdays” passed by uneventfully. Also, when an update applies, more often than not, it does not require a restart on a Server Core installation, whereas a Full Server would need to be restarted after installation. This results in a higher availability.
When you deploy a server, it’s vulnerable to the exploits fixed between the moment the image you’re deploying was created and the moment you’re deploying it.
Not interesting to malware writers ^
You need to know what to do ^
If you don’t know how to work the command line in Windows, you’ll have a hard time getting anything done on a Windows Server 2012-based Server Core installation. Although many blogs and websites will tell you where to click to get something configured or installed, only a handful of websites actually show you how to perform the same steps on the command line. Even in these cases, the equivalent of these command line tools might not be available on your Server Core installation because they were deemed non-essential.
Benefits put to good use ^
Microsoft has thought long and hard on these benefits; they wanted to make sure each one would be useful to the everyday admin. So, when you install Server Core, you’ll see that most of the uses for it are “fire and forget” scenarios, ranging from DHCP Servers to Windows Server Update Servers and from Domain Controllers to Hyper-V hosts.
All of the available roles fall into the category of infrastructure plumbing and offer a higher availability than a Server with a GUI. The Hyper-V host scenario is a scenario where Server Core really shines. When security is an issue, Server Core, again, is the most viable option. If your organization wants to deploy highly secure websites or FTP sites, Server Core should be on the top of your list. For hosting companies or organizations with a large Internet presence, Server Core installations offer the highest density web server capacity of all Windows Server installations.
In the past, Server Core installations of Windows Server 2008 and Windows Server 2008 R2 were limited. Windows Server 2008 Server Core installations, for instance, didn’t offer ASP.Net for websites. In Windows Server 2008 R2, fewer Server Roles were available than we have now in Windows Server 2012.
More than ever, Server Core installations offer an appealing feature set to everyday admins. Its Server Roles have been expanded with Certificate Server, Windows Server Update Server, and Routing and Remote Access. Also, the management and tooling are now on par with full Windows Server 2012 installations, going as far as switching between Server Core, Minimal Server, and Server with a GUI installations without reinstalling.
If you were waiting for version 3 of Server Core, now is the time to pay attention. In this series, I will tell you everything you need to know about Server Core to swap out a lot of those full installations with lean, mean Server Core machines.
In Part 2 I will outline the recommended preparations for Server Core installations.