What is the difference between Windows Server Standard and Datacenter?

Standard allows 2 licensed VMs (OSEs) per core license. Datacenter allows unlimited VMs on the licensed host, includes shielded VMs, Storage Spaces Direct, and software-defined networking. Standard suits physical servers running few VMs. Datacenter suits Hyper-V hosts running many VMs. Essentials is a third option limited to 25 users and no Hyper-V.

What is Server Manager in Windows Server?

Server Manager is the central management console that launches automatically on login. It shows server health, installed roles and features, events, and performance data. From Server Manager you can add roles (like AD DS, DNS, DHCP, File Server), manage multiple servers remotely, and access all administrative tools through the Tools menu.

What is the difference between a role and a feature in Windows Server?

Roles are primary server functions that define what the server does: Active Directory, DNS, DHCP, File Server, Web Server (IIS). Features are supporting components that enhance roles or the server itself: .NET Framework, BitLocker, Failover Clustering, Windows Backup, SNMP. A server typically has 1-3 roles and multiple supporting features.

Should I use Server Core or Desktop Experience?

Server Core (no GUI) is Microsoft's recommendation for production. It has a smaller attack surface, fewer updates, lower resource usage, and can be managed remotely via PowerShell, Windows Admin Center, or RSAT. Desktop Experience (full GUI) is easier for learning and troubleshooting. Start with Desktop Experience while learning, then move to Core for production deployments.

What Windows Server roles should I learn first?

Start with Active Directory Domain Services (AD DS) as it underpins almost everything else. Then learn DNS (required for AD), DHCP (network management), File Server (permissions and shares), and Group Policy (central management). These five roles cover 90% of what Windows Server administrators do daily.

Windows Server Basics: Editions, Roles & Server Manager Guide

Every enterprise environment I’ve walked into over the past 20 years has had Windows Server at its core. Love it or hate it, if you want to work in IT infrastructure, you need to understand Windows Server. It’s not optional.

In this guide, we’ll cover the fundamentals every sysadmin needs: editions and licensing, Server Manager, roles and features, and initial configuration. Whether you’re coming from a Linux background or just starting out, this is your foundation.

What you’ll learn:

Windows Server editions and when to use each
Server Manager: your command center
Roles vs Features (and why it matters)
Initial configuration checklist
Server Core vs Desktop Experience

Career Value: Windows Server skills are non-negotiable for enterprise IT roles. Understanding editions, licensing, and Server Core vs Desktop Experience immediately signals to interviewers that you think about infrastructure from a production perspective – not just following tutorials.

Server Manager: Your central hub for Windows Server administration

Quick Reference

Concept	What It Is	When You’ll Use It
Server Manager	Central management console	Daily – managing roles, features, servers
Roles	Primary server function (DNS, AD, etc.)	When setting up server purpose
Features	Supporting functionality (.NET, Telnet, etc.)	When roles need dependencies
Server Core	No GUI, command-line only	Production servers, reduced attack surface
Desktop Experience	Full GUI	Admin workstations, learning environments

Windows Server Editions

The Three You’ll Actually See

Windows Server Standard

Most common in small-medium environments
Licensed per core (minimum 16 cores)
Includes 2 virtual machine licenses
All the features most organizations need

Windows Server Datacenter

Unlimited virtualization rights
Same features as Standard
Licensed per core
Makes sense when running many VMs on one host

Windows Server Essentials

Limited to 25 users, 50 devices
No virtualization rights
Simplified management
Small business only

Pro Tip: In interviews, know the virtualization licensing difference. “Standard includes 2 VM licenses, Datacenter is unlimited” shows you understand real-world cost considerations.

The Interview Question

Q: “When would you recommend Datacenter over Standard?”

Good Answer: “When the cost of Datacenter licensing is less than licensing Standard for each VM. If you’re running more than 2 VMs per host, do the math – Datacenter’s unlimited virtualization often wins. Also, Datacenter includes extra features like Storage Spaces Direct and Shielded VMs for specific use cases.”

Server Manager: Your Command Center

Server Manager is the first thing you see after logging into a Windows Server with Desktop Experience. It’s your central hub for:

Adding and removing roles/features
Managing multiple servers from one console
Monitoring server health
Accessing administrative tools

The Dashboard

[SCREENSHOT: Server Manager Dashboard with roles listed]

When you open Server Manager, you’ll see:

Welcome tile – Quick setup tasks
Roles and Server Groups – What’s installed and its status
Events – Recent warnings and errors
Services – Status of key services
Performance – Basic resource monitoring

Adding Roles and Features

The wizard you’ll use constantly:

Server Manager → Manage → Add Roles and Features

Before You Begin – Skip this (tick “Skip this page”)
Installation Type – Role-based (99% of the time)
Server Selection – Pick your server
Server Roles – The main function
Features – Supporting components
Confirmation – Review and install

Warning: Some roles require a restart. Always check the confirmation screen and plan accordingly for production servers.

Managing Multiple Servers

Here’s where Server Manager shines in enterprise environments:

Server Manager → Manage → Add Servers

You can add servers by:

Active Directory search
DNS lookup
Direct import

Once added, you manage all servers from one console. This is how you’ll work in environments with dozens or hundreds of servers.

Roles vs Features: What’s the Difference?

This confuses new admins, but it’s simple:

Roles = What the server DOES (its primary purpose)

Active Directory Domain Services
DNS Server
DHCP Server
Web Server (IIS)
File Services

Features = Supporting functionality (tools and capabilities)

.NET Framework
PowerShell
Telnet Client
Windows Backup
Failover Clustering

Real-World Example

Setting up a Domain Controller:

Role: Active Directory Domain Services
Features automatically added: Group Policy Management, Remote Server Administration Tools

Setting up a Web Server:

Role: Web Server (IIS)
Features you might add: .NET Framework, ASP.NET

The Interview Question

Q: “Explain the difference between roles and features in Windows Server.”

Good Answer: “Roles define the server’s primary purpose – like DNS or Active Directory. Features are supporting capabilities that might be needed by roles or for management tasks. When you install a role, it often pulls in required features automatically. For example, installing AD DS automatically adds the Group Policy Management tools.”

Server Core vs Desktop Experience

This is a critical decision that shows maturity in your infrastructure thinking.

Desktop Experience (Full GUI)

Pros:

Familiar Windows interface
Easier for beginners
Some legacy apps require it
Better for jump boxes/admin stations

Cons:

Larger attack surface
More patching required
Higher resource usage
More things that can break

Server Core (No GUI)

Pros:

Smaller attack surface
Fewer patches
Lower resource usage
Forces you to learn PowerShell

Cons:

Steeper learning curve
Some applications don’t support it
Troubleshooting can be harder initially

When to Use Which

Scenario	Recommendation
Production Domain Controllers	Server Core
Production file servers	Server Core
Hyper-V hosts	Server Core
Admin jump boxes	Desktop Experience
Legacy application servers	Desktop Experience (if required)
Learning environment	Desktop Experience (then graduate to Core)

Pro Tip: Microsoft’s direction is clearly toward Server Core. In interviews, mention that you prefer Core for production workloads and can articulate why.

Basic Server Core Commands

When you log into Server Core, you get a command prompt. Essential commands:

# Launch PowerShell
powershell

# Basic configuration tool
sconfig

# Check IP configuration
ipconfig /all

# Check hostname
hostname

# Open Notepad (yes, it works)
notepad

The sconfig tool gives you a menu-driven interface for:

Computer name
Domain/workgroup
Remote management
Windows Update
Network settings

[SCREENSHOT: sconfig menu]

Initial Configuration Checklist

When you first set up a Windows Server, follow this checklist:

1. Set the Computer Name

Rename-Computer -NewName "SVR-DC01" -Restart

Naming convention matters. Common patterns:

SVR-[ROLE]-[NUMBER] (SVR-DC01, SVR-WEB02)
[LOCATION]-[ROLE]-[NUMBER] (LDN-DC01, NYC-WEB01)

2. Configure Static IP

For servers, always use static IPs:

# View adapters
Get-NetAdapter

# Set IP address
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 192.168.1.10 -PrefixLength 24 -DefaultGateway 192.168.1.1

# Set DNS
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 192.168.1.1,8.8.8.8

3. Join Domain (if applicable)

Add-Computer -DomainName "contoso.local" -Credential (Get-Credential) -Restart

4. Enable Remote Management

# Enable Remote Desktop
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name "fDenyTSConnections" -Value 0

# Enable through firewall
Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

# Enable WinRM (for PowerShell remoting)
Enable-PSRemoting -Force

5. Configure Windows Update

For production, use WSUS or SCCM. For standalone:

# Check for updates
Get-WindowsUpdate

# Install updates
Install-WindowsUpdate -AcceptAll -AutoReboot

6. Set Time Zone

Set-TimeZone -Name "GMT Standard Time"

Troubleshooting Common Issues

Problem: Can’t RDP to Server

Symptoms: Connection refused or timeout

Solutions:

# Check if RDP is enabled
Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name "fDenyTSConnections"

# Check firewall
Get-NetFirewallRule -DisplayGroup "Remote Desktop"

# Check RDP service
Get-Service -Name TermService

Problem: Server Manager Won’t Open

Symptoms: Server Manager crashes or hangs

Solutions:

Run as Administrator
Clear the cache: Delete %APPDATA%\Microsoft\Windows\ServerManager
Check WMI: winmgmt /verifyrepository

Problem: Role Installation Fails

Symptoms: Error during Add Roles wizard

Solutions:

Check Windows Update (missing prerequisites)
Check disk space
Review CBS logs: C:\Windows\Logs\CBS\CBS.log
Try PowerShell instead: Install-WindowsFeature -Name [RoleName]

Interview Questions

Q1: “Walk me through setting up a new Windows Server.”

Good Answer: “First, I’d determine if it needs Desktop Experience or if Server Core is appropriate for the workload. Then: set a meaningful hostname following naming conventions, configure a static IP, join it to the domain if applicable, enable remote management, and apply Windows Updates. Before adding any roles, I’d ensure the base configuration is solid and documented.”

Q2: “What’s your preference: GUI or Server Core?”

Good Answer: “For production workloads, I prefer Server Core wherever possible – smaller attack surface, fewer patches, forces infrastructure-as-code practices. I use Desktop Experience for admin jump boxes and legacy applications that require it. The trend is clearly toward Core, and I’m comfortable managing servers entirely through PowerShell and remote tools.”

Q3: “How do you manage multiple Windows Servers?”

Good Answer: “Server Manager can manage multiple servers from one console for basic tasks. For larger environments, I’d use Windows Admin Center or SCCM. PowerShell remoting with Invoke-Command and -ComputerName is essential for automation. For true scale, you need configuration management tools like Ansible, Puppet, or DSC.”

Career Application

On your resume:

“Deployed and configured Windows Server 2019/2022 environments”
“Managed Server Core deployments for reduced attack surface”
“Administered multi-server environments via Server Manager and PowerShell”

In interviews, demonstrate:

Understanding of when to use different editions
Knowledge of Server Core benefits
Awareness of licensing implications
Practical configuration experience

Next Steps

Next in series: Active Directory Essentials – build your first domain
Related: PowerShell Basics – essential for Server Core
Practice: Set up a Windows Server VM, try both Desktop Experience and Server Core

Ready to build on these foundations? Next up: Active Directory – the heart of Windows enterprise environments.

Windows Fundamentals Series

Part 1 of 6

Previous: N/A (This is the first article) | Next: Active Directory Essentials

ReadTheManualTech

ReadTheManual is run, written and curated by Eric Lonsdale.

Eric has over 20 years of professional experience in IT infrastructure, cloud architecture, and cybersecurity, but started with PCs long before that.

He built his first machine from parts bought off tables at the local college campus, hoping they worked. He learned on BBC Micros and Atari units in the early 90s, and has built almost every PC he’s used between 1995 and now.

From helpdesk to infrastructure architect, Eric has worked across enterprise datacentres, Azure environments, and security operations. He’s managed teams, trained engineers, and spent two decades solving the problems this site teaches you to solve.

ReadTheManual exists because Eric believes the best way to learn IT is to build things, break things, and actually read the manual. Every guide on this site runs on infrastructure he owns and maintains.

Enjoyed this guide?

New articles on Linux, homelab, cloud, and automation every 2 days. No spam, unsubscribe anytime.