Should a beginner choose Server Core or Desktop Experience?

If you are new to Windows Server, choose Server with Desktop Experience. It gives you the familiar graphical desktop, Server Manager and the management consoles, so you can learn by clicking through the tools. Server Core has no desktop and is managed from the command line, SConfig, PowerShell or remotely; it uses fewer resources and has a smaller attack surface, which makes it the production-preferred option, but it is a harder place to start. Whichever you pick, remember you cannot switch between the two later without reinstalling, so decide before you install.

Is Windows Server 2025 free to use in a lab?

Microsoft offers a free evaluation edition of Windows Server 2025 through its Evaluation Center, intended for testing and lab work rather than production. The evaluation runs for 180 days and must be activated over the internet within 10 days of installation or it will begin shutting down on a schedule. It is perfect for the kind of practice setup described here, but it is not a licence to run real workloads, and you should confirm the current terms and time limits on Microsoft's Evaluation Center before you rely on them.

How do I give Windows Server a static IP address?

On Server with Desktop Experience, open Server Manager, click the Ethernet link on the Local Server page to open Network Connections, right-click your adapter, choose Properties, select Internet Protocol Version 4 (TCP/IPv4), click Properties, then select Use the following IP address and enter an address, subnet mask, gateway and DNS server that fit your network. On Server Core, run sconfig and use the Network Settings option to do the same thing from the menu. A static address matters because other machines and roles need to find the server at a predictable address.

Can I convert Server Core to Desktop Experience after installing?

No. Since Windows Server 2016, the installation option you pick is fixed. There is no supported in-place way to add the Desktop Experience to a Server Core installation or to remove it from a Desktop Experience installation. If you install one and later need the other, you must reinstall the operating system. That is why choosing the right install option up front, before you commit, is one of the most important decisions in this whole process.

How to Set Up Windows Server 2025: A Beginner’s Guide

The short version: setting up Windows Server 2025 comes down to five stages. Boot the installer and choose your install option — Server with Desktop Experience (the familiar graphical desktop) or Server Core (command line only). Finish the install and set a strong Administrator password. Do the initial configuration — computer name, static IP address, time zone and updates — from Server Manager. Add your first role with the Add Roles and Features Wizard. Then tidy up basic security: updates on, firewall on, admin account handled properly. This guide walks a beginner through all five as a safe lab exercise, not a hardened production build.

Windows Server looks intimidating, but a first setup is approachable if you treat it as a sandbox. The best way to learn is to build a throwaway server — ideally in a virtual machine — break it, and rebuild it. Everything below assumes a practice box you own, on a network you control, where a mistake costs nothing but a reinstall.

This is a lab guide, not a production checklist

The steps here get you to a working, sensibly secured server you can learn on. A server that holds real data or faces the internet needs far more — domain design, patch and backup policy, least privilege, monitoring, hardening baselines and more. Treat this as your first day, not your last word.

Before you start: what you need

A first lab build needs surprisingly little. The most reliable route is a virtual machine, because you can snapshot it and roll back when an experiment goes wrong.

The Windows Server 2025 installation media. Microsoft publishes a free evaluation edition (Standard and Datacenter) on its Evaluation Center for testing and lab use. The evaluation runs for 180 days and must be activated over the internet within 10 days of install, or it starts shutting down on a schedule. Confirm the current terms on Microsoft's Evaluation Center before you rely on them.
A machine or VM that meets the minimum requirements (see the table below).
A hypervisor if you go virtual — Hyper-V on Windows 11 Pro, or another platform you already know. A VM lets you take a snapshot before each stage.
A network you control for the static IP step, and internet access for updates and activation.

Minimum hardware requirements

These are Microsoft's stated minimums for Windows Server 2025 — an absolute floor for the OS to install, not a recommendation for real work, and every figure below comes from Microsoft's Hardware requirements for Windows Server page. For a comfortable lab, give a Desktop Experience VM more RAM and disk than the bare minimum.

Component	Minimum for Windows Server 2025
Processor	1.4 GHz 64-bit (x64). Windows Server 2025 additionally requires the `SSE4.2` and `POPCNT` CPU instructions, so very old processors are excluded.
RAM	2 GB for Server Core; 2 GB for Desktop Experience (4 GB recommended).
Storage	32 GB minimum system partition (treat this as an absolute floor; give your VM more).
Network	An Ethernet adapter capable of at least 1 Gbps, compliant with PCI Express.
Firmware / security	UEFI with Secure Boot and a TPM 2.0 are required for features such as BitLocker and Secured-core server.

The SSE4.2 / POPCNT requirement is new — check your CPU

Windows Server 2025 will not install on a processor that lacks the SSE4.2 and POPCNT instructions. This trips people up when they try to reuse very old lab hardware or a VM pinned to an ancient virtual CPU. If setup refuses to proceed, an unsupported CPU is a likely cause. You can check a physical CPU's capabilities with Microsoft's Sysinternals Coreinfo tool, whose CPU Features view lists SSE4.2 and POPCNT among the instruction sets it reports on.

Step 1 — Choose Desktop Experience or Server Core at install

Early in setup, after you select edition and accept the licence, the installer asks which installation option you want. This is the single most consequential choice in the whole process, because you cannot change it later without reinstalling.

	Server with Desktop Experience	Server Core
Interface	Full graphical desktop, Server Manager, MMC consoles	No desktop; command line, `SConfig`, PowerShell, or remote tools
Footprint	Larger install, more RAM, more to patch	Smaller, lighter, fewer components to update
Attack surface	Larger (more installed features)	Smaller — a security advantage
Best for	Learning, and roles that expect a GUI	Production, experienced admins, remote management

Beginners should choose Server with Desktop Experience. You get the familiar interface and can learn every tool by clicking through it. Server Core is what many production servers actually run — it is leaner and has less to attack and patch — but with no desktop it is a steeper first climb. Once you are comfortable, building a Server Core box and managing it remotely is a great next exercise.

Core and Desktop Experience are a one-way choice

Since Windows Server 2016, there is no supported way to add or remove the Desktop Experience after installation. If you install Server Core and later decide you want the GUI — or the reverse — you must reinstall the operating system. Microsoft states this plainly in Server Core vs Server with Desktop Experience: you can't convert between the two after installation and need a clean installation instead. Decide deliberately before you click through the installer.

Running the installer

Boot the machine or VM from the Windows Server 2025 media.
Select your language, time and keyboard, then start the install.
Choose the edition (for a lab, the evaluation Standard edition is plenty) and select either Desktop Experience or Server Core. Follow the beginner advice above.
Accept the licence terms, then choose a custom / clean install onto the empty disk.
Let setup copy files and reboot. When it finishes, you are prompted to set the built-in Administrator password.

Set a strong Administrator password now

This is your first and most powerful account. Use a long, unique passphrase and store it in your password manager — locking yourself out of a fresh server is a rite of passage best skipped. On Server Core you set this at the same first-logon prompt; there is just no desktop behind it.

Step 2 — Initial configuration in Server Manager

On Desktop Experience, Server Manager opens automatically after you sign in. Its Local Server page is a single dashboard of the settings you configure first — each is a clickable link. On Server Core, run sconfig to get a numbered menu that does the same jobs from the command line.

Set the computer name. In Server Manager, open Local Server and click the current (randomly generated) computer name. Give it something meaningful — for example LAB-DC01 — and restart when prompted. On Server Core, use sconfig option for computer name.
```
Server Manager > Local Server > (computer name) > Change > enter name > Restart
```
Assign a static IP address. A server should live at a predictable address so other machines and roles can find it. On Local Server, click the Ethernet link to open Network Connections, right-click the adapter > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties, then choose Use the following IP address and enter an address, subnet mask, gateway and DNS that fit your network. On Server Core, use sconfig > Network Settings. You can also do it in PowerShell:
```
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 192.168.1.10 -PrefixLength 24 -DefaultGateway 192.168.1.1
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 192.168.1.1
```
Use addresses that match your own network — the values above are examples only.
Set the time zone. Click the time-zone link on Local Server and choose yours. Correct time matters more than it looks: authentication and, later, Active Directory are sensitive to clock skew.
Check for and install updates. Click the Last installed updates / Windows Update link, install everything available, and reboot. A brand-new install is always behind on patches. On Server Core, sconfig has a Download and Install Updates option.

Managing a Server Core box without leaving your desk

Once a Server Core machine has a name, an IP and updates, most people stop touching its console and manage it remotely — from Server Manager or the Windows Admin Center on another machine, or with PowerShell remoting. That is the intended workflow, and a good thing to practise early.

Step 3 — Add your first role

A freshly installed server does very little until you give it a role — the job it performs, such as a file server, web server (IIS), DNS or DHCP server, or a domain controller. For a first, low-stakes exercise, the Web Server (IIS) role is a great choice: it installs cleanly, and you can confirm it works by loading a page in a browser.

In Server Manager, click Manage > Add Roles and Features.
On the Before you begin page, click Next.
Choose Role-based or feature-based installation, then Next.
Select your server from the server pool, then Next.
On Server Roles, tick Web Server (IIS). When prompted, click Add Features to include the required management tools, then Next through the following pages.
Review the summary and click Install. When it finishes, browse to http://<your-server-IP>/ from another machine to see the default IIS page.

On Server Core there is no wizard; you add the same role with one PowerShell command:

Install-WindowsFeature -Name Web-Server -IncludeManagementTools

Go easy on the domain controller role at first

Promoting a server to a domain controller (installing Active Directory Domain Services) is a fantastic thing to learn — but it fundamentally changes the machine and your lab network, and it is easy to make a mess of DNS and accounts on the way. Do it deliberately, on a snapshot you can roll back, once the basics above feel comfortable. It is not a good first role.

Step 4 — Basic post-install security

This is lab-grade hygiene, not production hardening — but even a practice server should not be sloppy. Cover these four and you have a sane baseline.

Handle the Administrator account properly. You already set a strong password. As a good habit, create a separate named admin account for day-to-day work and keep the built-in Administrator for break-glass use. In a domain you would manage this centrally; in a standalone lab, at least avoid reusing the same weak password everywhere.
Keep Windows Update on. Patching is the single highest-value security control. Leave automatic updates enabled and check in regularly. Re-run the update step after adding roles, since new components can bring their own updates.
Leave Windows Defender Firewall on. It is on by default — keep it that way. When a role needs a port open (IIS opens HTTP/HTTPS for you), open only what that role needs rather than disabling the firewall. You can review rules under Windows Defender Firewall with Advanced Security.
Rename or disable what you are not using. Do not install roles and features "just in case" — every one you add is more to patch and more attack surface. A lean server is a safer server, which is exactly the logic behind Server Core.

Snapshot before you experiment

If your server is a VM, take a snapshot now — a clean, configured, patched baseline. Every time you are about to try something risky (promoting a domain controller, editing Group Policy, installing a heavy role), snapshot first. Rolling back a broken experiment in seconds is the biggest advantage a lab has over real hardware, and it turns mistakes into cheap lessons.

Where to go next

With a named, addressed, patched server running its first role, you have done the genuinely fiddly part. Good next experiments, each on a fresh snapshot: build a Server Core box and manage it from another machine; stand up Active Directory Domain Services and join a client to the domain; try Windows Admin Center; or explore Hyper-V to nest more lab VMs. For related walkthroughs, browse our How-To Guides; if you are pooling storage on your lab box, our Windows Storage Spaces guide pairs well with a file server role, and the Home Server guides cover the same instincts at home scale.