- Managing shared mailboxes in Office 365 with PowerShell - Thu, May 5 2016
- Managing shared mailboxes in Office 365 with the GUI - Wed, May 4 2016
- Installing and configuring the Enhanced Mitigation Experience Toolkit (EMET) - Wed, Mar 16 2016
If you’ve taken the time to install the latest build of Windows Server Technical Preview 2, you may have noticed that the graphical user interface (GUI) is no longer an option in a default install. When you’re prompted to select the operating system you want to install, you have two options.
Windows Server 2016 – Select the operating system you want to install
The first option, Windows Server Technical Preview 2 (the verbiage will most likely be replaced with Windows Server 2016 when the product is eventually released) is the traditional Server Core install that doesn’t include the GUI.
Windows Server 2016 Server Core
Just to show you how hardcore and serious Microsoft is, the Control+Alt+Delete logon prompt sits in a command prompt box. I wouldn’t be surprised to see this one day go the way of UNIX/Linux and drop the window completely in favor of just straight text.
Ctrl+Alt+Delete logon screen on Windows Server 2016 Server Core
The second option, Windows Server Technical Preview 2 (with local admin tools), is the “MinShell” install that contains a minimal GUI that includes Server Manager and the other GUI administration tools, but no traditional desktop.
Windows Server 2016 running MinShell
Install the GUI on Server 2016 “MinShell”
If you’re running the MinShell version of Windows Server 2016 that includes Server Manager and the other GUI administrative tools, installing the full GUI is rather easy. At the command prompt that you get when you log in, type powershell and press Enter to run PowerShell. Then, run the following command:
Install-WindowsFeature Server-Gui-Shell -Restart
The first part is the Install-WindowsFeature PowerShell cmdlet that tells Windows to install a feature of Windows Server. The second part tells the cmdlet that you want to install the GUI. The last part tells Windows to automatically reboot after installing the feature. The reboot is required to finish the install; just be aware that adding -Restart will force the reboot immediately following the completion of the install.
Install the GUI on Windows Server 2016 “MinShell” using PowerShell
Install the GUI on Server Core
If you decided to install Server Core, you have slightly more work to do to get the GUI installed. If you run the PowerShell command we used in the MinShell version of Windows Server 2016, it will fail and you’ll get a pretty big error message with lots of red error text: “Install-WindowsFeature : The request to add or remove features on the specified server failed. Installation of one or more roles, role services, or features failed. The source files could not be found.”
Error installing the GUI on Windows Server 2016 Server Core
We can dig a little bit by running this PowerShell command:
This will show us the installable GUI options on the server. As you can see in the screenshot below, the Install State is “Removed.” Because this is a Server Core install, options such as the GUI aren’t cached on the disk for quick install. Instead, we’ll have to access the OS install WIM file to install the GUI.
Looking at GUI options on Windows Server 2016 Server Core
In my example, I’m using a Hyper-V VM that has the Windows Server Technical Preview 2 ISO image connected to the DVD drive so I can access the install.wim file. To install the GUI, I run this command:
Install-WindowsFeature Server-Gui-Shell –Restart -Source wim:D:\sources\install.wim:4
Install the GUI on Windows Server 2016 Server Core using PowerShell
After a reboot on Windows Server 2016 MinShell or Server Core, you’ll be greeted by the full graphical user interface.
Windows Server 2016 with GUI enabled
To install the GUI or not?
Most, if not all, organizations still have server-based applications that don’t play well with Server Core and need the full GUI. In many cases, the management tools and agents that we use to manage those servers are the apps that need the GUI. Until more vendors catch up to Microsoft’s philosophy, we’ll still see lots of sysadmins installing the GUI on their servers.
In a perfect world, I’d love to see Microsoft embrace some of the Linux philosophy with respect to GUIs. If the GUI was something that ran only when we needed it, then Windows systems administrators could run the GUI whenever they needed to perform certain administrative functions or use applications that don’t support a pure command-line interface.
Subscribe to 4sysops newsletter!
That would also allow the GUI to remain in an offline mode when it wasn’t needed, and it could be patched without the need to constantly reboot the system for updates. As it stands today, the non-GUI version of Windows Server just looks like a GUI that’s been stripped of the Start menu/screen, Task Bar, File Explorer, and other useful GUI tools other than a few utilities. As for what the future holds for Windows Server, I don’t think the GUI will ever completely go away, but now is the time to start using and learning PowerShell before you’re left in the dust.
Want to write for 4sysops? We are looking for new authors.
Please share me Windows Server 2016 ISO image download path.
Windows Server 2016 Technical Preview 2 can be downloaded from the TechNet Evaluation Center.
I continue to find it ironic how Microsoft used to tout Windows Server as being easier to use because you could do so much with the GUI (e.g., Server 2003/08/08R2) and has backed away from that ever since.
I like PowerShell, but I absolutely *hate* them forcing it on me as the only option. It’s great for scripting, but despite my IT colleagues thinking I have an incredible memory, just using it for every day get-around-the-OS stuff is pretty annoying –and I’m someone who still knows the vast majority of the MS-DOS 5/6 CLI from memory. I continue to feel like Microsoft cares less and less about what the admins who use their products think. At least 2016 hasn’t completely removed the GUI, but they really should make the choice to keep it or not part of the beginning OS install.
I see where you’re coming from, but the ship sailed on this discussion a long time ago. The GUI hasn’t gone away; it simply won’t be available on the server console moving forward as the default option. We’re still somewhat early in the Server 2016 development cycle and Microsoft has promised more has coming… specifically in the way of web-based management tools. If you don’t know Get-Command and Get-Help yet, you should starting playing with those now. Those are the PowerShell equivalent of clicking through all the GUI menus. But, if you don’t start getting comfortable with PowerShell now, you’re going to be left completely behind very soon.
I agree completely with the idea that the GUI should be able to start (like I do on Linux with startx) but not consume CPU cycles.
If I want to deploy Windows Server 2016 on premises, it’s probably in a virtualization environment, or it is the host for a virtualization environment.
Virtualizing a GUI shell and all that crap is a total waste of memory and resources. People who can’t learn command line administration need to find new jobs.
However for a good example of when I will need to have a GUI on a server, take software build automation tasks. I use some development tools that can only be installed using a full Windows GUI, can not be rolled out just by installing some MSIs using some automated command line process, and which must then be configured with a GUI, and must pass through some grotesque activation (anti-piracy) GUI elements. Once I roll a GUI out on a server, I want to be able to turn it off again. Then I can avoid wasting resources, disk, compute, and otherwise, on crap I don’t want in the server image.
Then I can take an image host it on my own Hyper-V Server, and then live-migrate it to other locations as I need it to move.
They removed this option in later versions of Windows 2016 preview. No longer it’s possible to switch between GUI and core. https://redmondmag.com/articles/2015/08/27/windows-server-2016-preview-3.aspx
They removed the GUI and allowed you to manage the systems remotely via Server manager or other tools, people should not be directly using RDC to get into servers unless it is for an installation or problem, your introducing human error to take a system down. I see people still RDC into a AD/DC/DNS server to make changes and add accounts, you should be using the RSA tools for things like that as an example not going direct into a server for it.
We’re now up to Technical Preview 5 and it remains the case that you can no longer move between the GUI and Server Core in Windows Server 2016. The option you pick at install time is permanent.
Yep… and the article is a year old. Here’s the first sentence of the article, “If you’ve taken the time to install the latest build of Windows Server Technical Preview 2…”
I have tried the above commands on TP5 in order to install Gui from shell but it did not work, noticed that the sources directory does not contain a file called ‘install.wim‘.
My workaround was to change directory into the mounted DVD image, and running setup.exe which initiated the installation.
I wish that was the default GUI of Windows 10
How do I uninstall from my computer 2016 server with core interface
GUI features are removed from server 2016 and only exchange which will work on 2016 server is exchange 2016 CU3.Exchange 2016 native without any CU by default will not get installed on latest release of server 2016.
Don’t forget that you can do a lot of management from Server Manager on a remote system that has the GUI installed. You don’t need every server in your farm to have a GUI to perform GUI based management.
I am in a situation that, I have installed Microsoft Hyper-V server 2016, there is no option to select core or GUI mode while installation.
I have downloaded server from this link:
After Installation, I tried to convert Core to GUI, I am not able to do this. Please help on this whether it is possible or not in my case.
Hyper-V Server is the version of Windows that is a stripped down OS for Hyper-V. There is no GUI option for that version.
I just tried to figure this out after a lot of frustration and found that Microsoft removed the option to switch the GUI on and off after installation in the final build of 2016. Ugh.
“Unlike some previous releases of Windows Server, you cannot convert between Server Core and Server with Desktop Experience after installation. For example, if you install Server Core and later decide to user Server with Desktop Experience, you should do a fresh installation (and vice versa).”
This NOTE is at the bottom of the page on the source link.
Source -> https://technet.microsoft.com/en-us/windows-server-docs/get-started/windows-server-2016
Thanks for all of the information above. When I installed Server 2016 standard, All I get is a command prompt. I thought I was just missing the GUI, but it appears that I am missing more? What do I do at that command prompt? please and than you.
If the GUI was something that ran only when we needed it, then Windows systems administrators could run the GUI whenever they needed to perform certain administrative functions or use applications that don’t support a pure command-line interface.
It’s called Windows 3.1 😛
I’m trying to install Windows Server 2106 on Vsphere, but it doesn’t have a gui option, nor does it in the install-windowsfeature it shows that the feature name is not valid: ‘servercore-fullserver, server-gui-shell, server-gui-mgmt. I downloaded this from the volume licensing center.
doesn’t work with Server 2016 1803 image
way out of date. 180* version is the insight that should be at top of search.
Just tried to install SQL server 2016 on a Server 2016 VM what a mission!
No GUI, vague install clues. WTF is Micro$oft doing ???
i have accidently installed windows 2016 server core. i tried to convert it to Full GUI but i couldnt. Is there any way to reinstall Windows 2016 server GUI on the machine?
I need cooperation with the Windows 10 ISO. When I install the ISO with GUI mode, it shows a troll face as the background image? Why is this?