Windows Server Installation and Initial Configuration: Step-by-Step Guide (2025/2022)

Sunucun 6 min read

Windows Server is Microsoft’s operating system for servers. It is used to manage users and computers centrally on a company network (Active Directory), host websites and applications (IIS), share files, run virtual machines (Hyper-V) and provide remote desktop services. In this guide we walk through a Windows Server installation from start to finish, from choosing a version to the initial settings and adding the basic roles.

Illustration: Windows

Which Windows Server Version Should You Install?

For new installations the current release is Windows Server 2025; Windows Server 2022 is still widely used. Each release comes in two main editions. According to Microsoft’s pricing and edition comparison pages, the key differences are:

FeatureStandardDatacenter
Virtualization rights2 virtual machines per license (+1 Hyper-V host)Unlimited virtual machines
Core roles (AD DS, DNS, DHCP, IIS, file services, Hyper-V)YesYes
Storage Spaces DirectNoYes
Host Guardian Hyper-V support for shielded VMsNoYes
Network Controller (software-defined networking)NoYes
LicensingCore-based + CALsCore-based + CALs

Standard is usually enough for a single physical server or a few virtual machines; Datacenter is preferred on virtualization hosts that run many VMs. Both editions require a client access license (CAL) for every user or device that accesses the server.

System Requirements

Minimum values from Microsoft’s hardware requirements page (the same for Standard and Datacenter):

ComponentWindows Server 2025Windows Server 2022
Processor1.4 GHz 64-bit; NX/DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW, SLAT; plus SSE4.2 and POPCNT1.4 GHz 64-bit; NX/DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW, SLAT
RAM2 GB (4 GB recommended for Desktop Experience)Server Core 1 GB, Desktop Experience 2 GB
DiskAt least 32 GBAt least 32 GB
NetworkEthernet adapter of at least 1 Gbit/sEthernet adapter of at least 1 Gbit/s

These are the lower limits for the installation to work; real needs depend on the roles you install. Microsoft notes that installing Windows Server 2025 on a virtual machine with the minimum values (1 core, 1,024 MB RAM) fails, and that you should allocate at least 1,280 MB RAM for setup. Some features need TPM 2.0 (for example BitLocker), and Secure Boot needs UEFI 2.3.1c.

Server Core or Desktop Experience?

  • Server Core: No graphical desktop; the server is managed with the command line, PowerShell, the sconfig menu or remote management tools. It uses less disk and memory, and because it contains fewer components there is less to update.
  • Desktop Experience: Comes with the familiar Windows interface and Server Manager. It is easier for beginners and for applications that need a graphical interface.

The installation option can’t be changed later, so make the right choice during setup.

Preparing the Installation Media

  • ISO file: Download the licensed ISO from the channel you bought it through (for example your Microsoft account or reseller). To try it out, you can use the evaluation version from the Microsoft Evaluation Center.
  • Physical server: Write the ISO to a USB drive of at least 8 GB as bootable media with a tool such as Rufus. On enterprise servers you can also mount the ISO as a virtual drive through remote management cards such as iLO or iDRAC.
  • Virtual machine: In Hyper-V, VMware or VirtualBox, simply attach the ISO to the virtual DVD drive.

Installing Windows Server Step by Step

  1. Boot from the media: Insert the USB drive or attach the ISO, restart the server and choose the installation media from the BIOS/UEFI boot menu.
  2. Language and keyboard: Choose the language, time/currency format and keyboard layout, then click Next.
  3. Start setup: Choose to install a new copy of Windows Server.
  4. Product key: Enter your license key. The evaluation version doesn’t ask for one.
  5. Choose the image: Select Standard or Datacenter, with either Server Core or Desktop Experience.
  6. License terms: Read and accept the Microsoft software license terms.
  7. Disk: Select the disk to install on. A new disk shows as “Unallocated space”; selecting it is enough, and Windows creates the required system partitions itself. If the disk doesn’t appear, load the RAID or storage controller driver from this screen.
  8. Installation: Files are copied and the server restarts several times. The time depends on the hardware.
  9. Administrator password: On first boot, set a strong password for the local Administrator account.

Initial Settings After Installation

On Desktop Experience these settings are available in Server Manager > Local Server; on Server Core, use the sconfig menu. The PowerShell equivalents are below.

1. Change the server name (hostname)

Setup assigns a random name such as WIN-XXXXXXX. Give the server a name that is easy to recognize on the network; the change requires a restart:

Rename-Computer -NewName "SRV01" -Restart

2. Set a static IP and DNS

Servers use a static IP so their address doesn’t change. Find the adapter name with Get-NetAdapter and enter your own network details:

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

On a server in a data center or a VDS, the IP details are provided by the provider and this step is often already done.

3. Install updates

Run Windows Update to get the security updates released after your installation media (on Server Core, use the update option in sconfig). It is good practice to finish updating before exposing the server to the internet or adding roles.

4. Configure Remote Desktop and the time zone

If you will manage the server remotely, enable Remote Desktop (RDP) and restrict the firewall so that only the IP addresses you need can connect. Setting the correct time zone matters for log entries and scheduled tasks.

Adding the Basic Roles

Roles are what give Windows Server its functions. On Desktop Experience use the Add Roles and Features wizard in Server Manager; in PowerShell use Install-WindowsFeature:

# Web server (IIS)
Install-WindowsFeature -Name Web-Server -IncludeManagementTools

# Active Directory Domain Services
Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools
  • Active Directory Domain Services (AD DS): Manages users, computers and group policies centrally. After installing the role, the server has to be promoted to a domain controller.
  • DNS and DHCP: DNS translates domain names to IP addresses and is required by Active Directory. DHCP hands out IP addresses to devices on the network automatically.
  • Web Server (IIS): Hosts websites and ASP.NET applications.
  • File and Storage Services: Provides shared folders, NTFS and share permissions, quotas and features such as DFS.
  • Hyper-V: Lets you run virtual machines on the server.
Illustration: Windows

Can You Install a Server on Your Own Computer?

Yes. Windows Server can be installed on a 64-bit computer that meets the requirements above; the easiest way to try it and learn is to install the evaluation version in a virtual machine in Hyper-V or VirtualBox. If the server will be exposed to the internet and run 24/7, however, a home setup runs into issues such as a static IP, uninterrupted power, enough upload speed and firewalling. That is why a server in a data center is usually more practical for websites, applications or remote desktop.

If you want to follow these steps on your own server, you can use a VDS server delivered with Windows Server 2012 R2, 2016, 2019 or 2022 installed and managed over Remote Desktop (RDP) with Administrator rights.

Conclusion

Installing Windows Server starts with choosing the right version and edition, checking the hardware requirements and deciding between Server Core and Desktop Experience. After installation, setting the server name, a static IP and updates, and adding only the roles you need keeps the server both manageable and secure.

Categories

Latest guides