Windows Server Core: Managing It Without Losing Your Mind

Server Core is the right default for most Windows Server roles. Smaller attack surface, fewer patches, less to reboot for. The objection is never technical. It is that the first time you log on to a black window with a single command prompt, the muscle memory of twenty years of Server Manager stops being any use.

This guide covers how to actually work with Server Core day to day. The tools, the tasks that trip people up, and the small number of commands that get you out of trouble when remote management is not available.

First fifteen minutes on a new build

Log on and type sconfig. It handles the initial setup without you having to remember a single command, and it is present on every Server Core installation.

That is the point at which you stop using the console and manage it from somewhere comfortable.

The three ways to manage it remotely

Windows Admin Center is the closest thing to a replacement for Server Manager. It is a browser-based tool you install on a management server or your own workstation, and it gives you roles, services, event logs, storage, certificates, registry and a PowerShell console, all against a remote Core box. If you manage more than a couple of servers this is the one to set up.

RSAT and the MMC consoles still work. Install the relevant Remote Server Administration Tools on your Windows workstation and connect the console to the remote server. DNS Manager, DHCP, Failover Cluster Manager, AD Users and Computers all behave normally. This is often the fastest route for a role-specific task.

PowerShell remoting is where the real work happens. It is enabled by default on Windows Server and does not need anything installed on your side.

# One-off command against a remote Core server
Invoke-Command -ComputerName core01 -ScriptBlock { Get-Service W32Time }

# An interactive session, like an SSH login
Enter-PSSession -ComputerName core01

# A persistent session you can reuse
$s = New-PSSession -ComputerName core01
Invoke-Command -Session $s -ScriptBlock { Get-WindowsFeature | Where-Object Installed }

# Several servers at once
Invoke-Command -ComputerName core01,core02,core03 -ScriptBlock { Get-HotFix | Select-Object -Last 1 }

Roles and features without Server Manager

Everything Server Manager did through its wizard is available through two cmdlets. The names are worth committing to memory because they come up constantly.

# What is available, and what is already on
Get-WindowsFeature
Get-WindowsFeature | Where-Object InstallState -eq Installed

# Install a role with its management tools
Install-WindowsFeature -Name DHCP -IncludeManagementTools

# Install remotely
Install-WindowsFeature -Name Web-Server -IncludeManagementTools -ComputerName core01

# Remove one cleanly
Uninstall-WindowsFeature -Name Windows-Defender-GUI -Restart

The -IncludeManagementTools switch matters more on Core than it did on a full install, because without it you get the role and none of the PowerShell modules for managing it.

The tasks that catch people out

Getting a console back. Closing the command prompt window leaves you looking at a blank desktop with nothing on it. Press Ctrl+Shift+Esc for Task Manager, then File, Run new task, and type cmd or powershell. Nobody discovers this calmly the first time.

Copying files. No Explorer, so use the admin share from your workstation. \\core01\c$, or copy over a PowerShell session with Copy-Item -ToSession. The second is more reliable across network boundaries.

Editing a configuration file. Notepad is not present on Server Core. Use notepad.exe from your own machine against the admin share, or edit in place with PowerShell. For quick changes, Get-Content piped through ForEach-Object and back out with Set-Content does the job.

Adding the GUI later. On Server 2012 R2 you could convert between Core and full desktop. On Server 2016 and later you cannot. The choice is made at install time and changing it means a rebuild. Plan accordingly.

Applications that need a GUI. Some agents and installers assume a desktop and either fail or hang silently. Check vendor support for Server Core before committing a role to it, particularly for backup agents and monitoring tools.

Useful commands worth pinning up

# Basic system information
Get-ComputerInfo | Select-Object OsName,OsVersion,CsName,OsUptime

# Network configuration, quickly
Get-NetIPConfiguration
Get-NetIPAddress -AddressFamily IPv4 | Format-Table InterfaceAlias,IPAddress,PrefixLength

# Set a static address
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 10.0.0.20 -PrefixLength 24 -DefaultGateway 10.0.0.1
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 10.0.0.10,10.0.0.11

# Recent errors without Event Viewer
Get-WinEvent -FilterHashtable @{LogName="System"; Level=2; StartTime=(Get-Date).AddDays(-1)} | Select-Object TimeCreated,Id,Message -First 20

# Disk space
Get-Volume | Where-Object DriveLetter | Format-Table DriveLetter,FileSystemLabel,SizeRemaining,Size

# Restart cleanly
Restart-Computer -Force

Is Server Core right for the role?

Glossary

Frequently asked questions

Can I add the GUI to Server Core later?

Not on Windows Server 2016 or later. The Core and Desktop Experience options are separate installations and converting between them is no longer supported. On Server 2012 R2 it was possible, which is why the belief persists.

How do I edit a text file on Server Core?

There is no Notepad. Use PowerShell to read and rewrite the file, or open it from your own workstation over the administrative share. For structured files, the relevant PowerShell module is usually a better answer than editing text at all.

Does Server Core get fewer updates?

Yes, meaningfully. Removing the shell removes a large number of components that would otherwise need patching, which in practice means fewer reboots and a smaller maintenance window.

What if I close the only command prompt?

Press Ctrl+Shift+Esc to open Task Manager, then File, Run new task, and type cmd or powershell. This is the single most useful thing to know before your first Core build.

Is Windows Admin Center a replacement for Server Manager?

For most day-to-day tasks, yes, and it works well against Server Core. Some specialist consoles still need RSAT, so most administrators end up using both.

Disclosure: this post may contain affiliate links. If you buy through one of them, we may earn a small commission at no extra cost to you. We only recommend products we’ve tested or genuinely rate.