Skip to main content

Switching between Server 2012 Full Installation and Server Core

By

Over the past several years that I have been instructing Windows classes, I have had a lot of raised eye brows when it comes to the topic of Server Core.  Although my classes agrees with the principals of smaller attack foot print and less management, the whole text based interface do not settle well.  With the release of Server Core 2008 R2, we were given the sconfig tool to help make configuration of the server core a bit easier.  It also made it easier to configure the firewall to allow the core to be managed from a GUI machine.

With Windows Server 2012, we have another option.  We can install either Server Core or the Full installation and simply switch between the two of them.  The GUI is now an installable feature that can also be removed.  This will result in a reboot when making the switch and some delay while Windows reboots.  In this scenario, you can run Server Core for daily operations.  If you need to do some work that you would rather do in a GUI, you can add the GUI feature.  Once you have finished with the GUI, remove the GUI feature and reboot.  

Here is the process to convert from a GUI to Server Core.

Log in to Server 2012 as an Administrator.

In Server Manager, click Manage –> Remove Roles and Features

image

On the Before you Begin window, click Next.

image

Select the server that you want to change to a server core and click Next.

At the Remove servers roles window, click Next.

On the Remove Features window, clear the User Interfaces and Infrastructure check box and click Next.

Check the Restart the destination server automatically if required check box if you want to implement this change immediately.

 

Click Yes and then Next.

image

At the confirmation screen, you may have noticed that other roles and features are also removed.  For example, Windows Deployment Server cannot be installed on a Server Core.  If you have WDS installed on this GUI installation, it will be removed if your switch to the core installation.

 

During the shutdown and boot up, you will have to wait for the configuration changes to be made.

image

 

Once the reboot completed, you will be in Server Core implementation.  So, what do you do if you need the GUI back?

Type PowerShell and press Enter.

Type Add-WindowsFeature server-gui-shell and press Enter.

image

Next you need to reboot the server.  Type Shutdown –t 0 –r and press Enter.

This process will cause down time of several minutes for the server.  Also, remember that it may remove functionality from the server when converting to server core if that functionality is only available in the GUI installation.

Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more