Should I install Windows Server as Core or with Desktop Experience?
Server Core has fewer updates, smaller attack surface and fewer reboots, but no GUI. For DCs, file servers and Hyper-V Core is fine; for third-party apps that demand a UI Desktop is more practical.
Try this first
- 1Inventory what runs on the server: Microsoft roles (DC, DNS, DHCP, Hyper-V, File Server) run fine on Core.
- 2Vendor checks: line-of-business apps often ship a GUI installer or messy dependencies. Read vendor docs for 'Server Core supported'.
- 3Manage Core via Server Manager on a workstation, Windows Admin Center, RSAT or PowerShell remoting. Requires a working admin workflow upfront.
- 4For rarely-touched servers (DCs, file servers) choose Core, saves patch and reboot time long term.
- 5For servers with heavy GUI management (legacy AV console, vendor-specific tool) and no migration path, stick with Desktop Experience.
When to bring us in
On Server 2019/2022/2025 you can no longer add a GUI afterwards (Server 2016 still allowed it). Once Core, always Core. Plan for it or against it.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.