Complete Step-by-Step Setup Guide
Installing Windows Server 2025 is not difficult. Choosing the wrong installation option, storage layout, or server configuration before clicking Install is where problems usually begin.
A new server may eventually become a domain controller, Hyper-V host, file server, application server, or part of a larger infrastructure. Those workloads have different operational requirements, but the installation process often starts from the same Windows Server Setup screen.
The decisions made during setup matter.
Should you install Server Core or Desktop Experience?
Which Windows Server edition should you select?
Should the server use a static IP address immediately?
When should you rename the server?
And what should be configured before adding Active Directory, Hyper-V, or other production roles?
This guide walks through a clean Windows Server 2025 installation from initial planning to the first post-installation configuration tasks.
The goal is not simply to reach the Windows desktop or command prompt. The goal is to leave the server in a clean, documented state that is ready for its intended role.
If you are still choosing an edition, review our Windows Server 2025 Standard vs Datacenter comparison before starting the installation.
For broader licensing planning, see the Complete Windows Server Licensing Guide.
Table of Contents
- Plan the Server Before Installation
- Check Windows Server 2025 Hardware Requirements
- Prepare Windows Server 2025 Installation Media
- Server Core vs Desktop Experience
- Standard vs Datacenter During Setup
- How to Install Windows Server 2025
- Step 1: Boot from Installation Media
- Step 2: Select Language and Regional Settings
- Step 3: Choose the Windows Server Edition
- Step 4: Accept the License Terms
- Step 5: Choose the Installation Type
- Step 6: Select the Installation Drive
- Step 7: Complete the Installation
- Step 8: Configure the Administrator Account
- First Configuration Tasks After Installation
- Configure a Static IP Address
- Rename the Windows Server
- Install Windows Updates
- Configure Time and Time Zone
- Review Windows Defender Firewall
- Add Server Roles
- Common Installation Mistakes
- Frequently Asked Questions
Plan the Server Before Installation
Before creating installation media, decide what the server is expected to do.
A server described only as “the new Windows Server” is not ready for deployment.
Document its intended role.
For example:
- Domain Controller
- Hyper-V Host
- File Server
- Application Server
- Remote Desktop Session Host
- Backup Server
- Management Server
The role affects later configuration decisions.
A Hyper-V host should generally remain focused on virtualization and host management.
A domain controller requires careful network and DNS planning.
An RDS Session Host introduces Remote Desktop Services configuration and additional licensing considerations.
A file server may require a storage design that separates the operating system from business data.
You do not need to configure every role before installation, but you should know the server’s intended purpose.
A simple deployment note might look like this:
Server name: HV-HOST01
Role: Hyper-V Host
Edition: Windows Server 2025 Datacenter
Installation option: Server Core
Management IP: 192.168.10.20
Storage: RAID 1 OS volume, separate VM storage
Domain: corp.example
This takes a few minutes to prepare and creates a much cleaner starting point for the deployment.
Check Windows Server 2025 Hardware Requirements
Before installation, verify that the physical server or virtual machine meets the Windows Server hardware requirements.
Minimum requirements should be treated as an installation baseline rather than a sizing recommendation for production workloads.
The amount of CPU, memory, and storage a server actually needs depends on its role.
A lightly used management server has very different resource requirements from a Hyper-V host running multiple production virtual machines.
Review:
- Processor architecture and performance
- Installed memory
- Available storage
- Network adapters
- Firmware configuration
- Storage controller support
- TPM and Secure Boot capabilities where required by the planned security features
- Hardware support for the intended server role
If Hyper-V will be installed, virtualization hardware and firmware requirements should also be reviewed.
For detailed pre-installation hardware planning, see our Windows Server 2025 System Requirements Guide.
Do not size a production server around the minimum installation requirement.
Size the hardware around the workload.
Prepare Windows Server 2025 Installation Media
Windows Server can be installed from appropriate installation media, such as a bootable USB drive or DVD.
Before preparing the media, confirm that you have the correct Windows Server 2025 installation source for your licensing and deployment channel.
Do not use an unknown or modified ISO image from an unverified download source.
For evaluation and testing, Microsoft provides Windows Server 2025 installation downloads through the Microsoft Evaluation Center.
For production deployments, use installation media appropriate to the organization’s licensing channel and deployment rights.
Once you have the ISO image, create bootable installation media using a suitable USB preparation tool or the organization’s standard deployment process.
Before starting the installation, confirm:
- The ISO download is complete.
- The correct Windows Server release is being used.
- The target server can boot from the selected installation media.
- Required storage or network drivers are available if the hardware needs them.
- Existing data on the target installation disk has been backed up.
A clean installation can remove existing partitions and data.
Do not assume the installation disk is empty simply because the server is being repurposed.
Server Core vs Desktop Experience
This is one of the most important choices in the Windows Server 2025 installation process.
Windows Server Setup provides installation options for Server Core and Server with Desktop Experience.
The difference is not simply visual.
The installation option affects how the server is managed and which local graphical components are available.
Server Core
Server Core installs Windows Server without the standard desktop graphical interface.
Local management is primarily performed with tools such as:
- PowerShell
- Command Prompt
- SConfig
- Remote management tools
Server Core has a smaller installation footprint and is Microsoft’s recommended installation option unless the additional graphical interface and local GUI management tools are required.
Typical Server Core scenarios may include:
- Hyper-V hosts
- Domain controllers
- Infrastructure servers
- Remotely managed server environments
The exact choice still depends on the server role and the tools required by the organization.
Server with Desktop Experience
Desktop Experience installs the standard graphical user interface and local graphical management tools.
Administrators who prefer Server Manager and GUI-based local administration may find Desktop Experience easier to work with.
It may also be appropriate when a server application or management workflow depends on graphical components that are not available in a standard Server Core installation.
Can You Switch from Server Core to Desktop Experience Later?
No.
Windows Server 2025 does not support converting an existing Server Core installation into Server with Desktop Experience, or converting Desktop Experience into Server Core.
Changing the installation option requires a clean installation.
This is why the choice should be made before deploying production workloads.
Do not select Server Core simply because it has a smaller footprint if the server application later requires Desktop Experience.
Likewise, do not automatically install the full GUI on every infrastructure server because it feels more familiar.
Choose based on the role and management model.
Standard vs Datacenter During Setup
Windows Server Setup may present Standard and Datacenter editions along with their available installation options.
Choose the edition that matches the planned deployment and licensing.
Do not select Datacenter during setup simply because it appears to be the “higher” edition.
Standard and Datacenter are designed for different infrastructure scenarios.
Standard is commonly evaluated for physical or lightly virtualized environments.
Datacenter provides broader virtualization rights and advanced datacenter capabilities.
The number of planned Windows Server virtual machines can materially affect the edition decision.
If the server will become a Hyper-V host, review the Windows Server Hyper-V Licensing Guide before finalizing the edition.
For physical-core calculations, see our Windows Server Core Licensing Guide.
The edition selected during installation should match the organization’s deployment plan.
How to Install Windows Server 2025
The following steps describe a clean Windows Server 2025 installation using installation media.
The exact boot menu and firmware interface depend on the physical server or virtualization platform.
Step 1: Boot from the Windows Server Installation Media
Insert or attach the Windows Server 2025 installation media.
For a physical server, this may be:
- a bootable USB drive,
- DVD media,
- or virtual media presented through the server’s remote management interface.
For a virtual machine, attach the Windows Server ISO to the virtual DVD drive.
Restart or power on the server.
Open the system boot menu if necessary and select the installation media.
The server should load Windows Setup.
If the server repeatedly boots into the existing operating system, review the firmware boot order or manually select the installation device.
Step 2: Select Language and Regional Settings
Windows Setup displays the initial regional configuration screen.
Select the appropriate:
- Language to install
- Time and currency format
- Keyboard or input method
Review the keyboard layout carefully.
An incorrect keyboard layout can become frustrating when entering the Administrator password after installation, particularly when the password contains special characters.
Continue to the installation screen and select Install now.
Step 3: Choose the Windows Server Edition
Setup displays the available Windows Server editions and installation options included in the installation media.
The list may include options such as:
- Windows Server 2025 Standard
- Windows Server 2025 Standard with Desktop Experience
- Windows Server 2025 Datacenter
- Windows Server 2025 Datacenter with Desktop Experience
Read the complete edition name before continuing.
If you select an edition without Desktop Experience in the name, you are selecting the Server Core installation option.
This choice cannot simply be changed later by installing the GUI.
Confirm:
- Standard or Datacenter
- Server Core or Desktop Experience
Then continue.
Step 4: Accept the License Terms
Review the applicable Microsoft Software License Terms presented during Setup.
Select the option to accept the terms if you agree and want to continue with the installation.
The installation cannot continue without accepting the applicable terms.
Step 5: Choose the Installation Type
For a clean Windows Server installation, select the custom installation option.
A clean installation is appropriate when:
- deploying a new physical server,
- creating a new virtual machine,
- rebuilding an existing server,
- or intentionally replacing the current operating system installation.
An in-place upgrade is a different deployment scenario and should be planned separately.
Do not use a clean installation on an existing production server until required data, configuration information, application dependencies, and recovery options have been reviewed.
This guide focuses on a new clean deployment.
Step 6: Select the Installation Drive
Windows Setup displays the available disks and partitions.
This is the point where administrators should slow down and verify the target disk.
On a new server, you may see:
- one local disk,
- several physical disks,
- a logical RAID volume,
- or storage presented by the virtualization platform.
Select the storage intended for the Windows Server operating system.
For a simple deployment, Setup can create the required system partitions automatically from unallocated space.
For larger production servers, storage may already be designed around separate volumes for:
- the operating system,
- application data,
- virtual machines,
- databases,
- or backup staging.
Do not create a complicated partition layout during Setup without a reason.
Storage architecture should follow the server workload.
Before deleting or formatting an existing partition, confirm that the disk does not contain required data.
Once the correct target is selected, continue with the installation.
Step 7: Complete the Windows Server Installation
Windows Setup copies files and installs the operating system.
The server may restart several times.
Do not remove the installation media too early if the deployment process still requires it.
However, after the first restart, make sure the server does not begin the installation process from the start again because the boot order still prioritizes the USB or DVD media.
The installation time depends on:
- server hardware,
- storage performance,
- installation option,
- and deployment environment.
When Setup finishes, Windows Server proceeds to the initial account configuration.
Step 8: Configure the Administrator Account
Create a password for the built-in Administrator account.
Use a strong password that follows the organization’s credential policy.
Avoid:
- company names,
- server names,
- predictable year combinations,
- reused administrator passwords,
- or passwords stored in deployment notes as plain text.
In a managed environment, privileged credentials should be handled according to the organization’s administrative access and password management process.
After configuring the password, sign in to Windows Server.
What appears next depends on the installation option.
Desktop Experience displays the graphical Windows Server environment.
Server Core opens its command-line-focused management environment, where SConfig and PowerShell can be used for initial configuration.
The operating system is installed.
The server is not yet ready for production.
First Configuration Tasks After Installation
One of the most common deployment mistakes is installing Windows Server and immediately adding the main server role.
For example:
Installation complete. Now promote it to a domain controller.
A cleaner process is to establish the server’s base configuration first.
Before installing production roles, review:
- Server name
- Network configuration
- Time and time zone
- Windows updates
- Driver and firmware requirements
- Remote management
- Firewall configuration
- Activation and edition status
- Event logs
- Server documentation
The exact order may vary, but the base operating system should be reviewed before the server becomes infrastructure that other systems depend on.
Configure a Static IP Address
Many Windows Server roles require predictable network configuration.
Domain controllers, DNS servers, Hyper-V management interfaces, and infrastructure servers should not be deployed with an accidental dynamic address simply because DHCP worked during installation.
Before assigning a static IP address, confirm the network plan.
Document:
- IP address
- Subnet prefix or mask
- Default gateway
- Preferred DNS server
- Alternate DNS server where appropriate
DNS configuration deserves particular attention.
Do not automatically enter a public DNS resolver on a server that will participate in an Active Directory environment without understanding the intended DNS architecture.
For a new domain controller deployment, DNS planning should be part of the Active Directory design.
After configuring the address, verify:
- local network connectivity,
- gateway reachability,
- DNS resolution,
- and access to required management services.
Rename the Windows Server
Default Windows Server computer names are not useful for long-term infrastructure management.
Rename the server before installing major roles when possible.
A naming convention might identify the server’s purpose and location.
Examples:
- DC01
- FILE01
- HV-HOST01
- RDSH01
- APP01
Avoid names that are too generic, such as:
- SERVER
- NEW-SERVER
- TEST
- WINDOWS2025
Also avoid embedding information in the name that is likely to change.
A server called ACCOUNTING-SERVER may eventually host another workload.
A structured infrastructure naming convention is easier to scale.
After renaming the server, restart it when required.
Install Windows Updates
Before deploying production roles, check for available Windows updates.
A newly installed ISO may not include every update released after the installation media was created.
Install applicable updates according to the organization’s patch management process.
After updates are installed:
- restart the server when required,
- check for updates again,
- and review whether additional servicing or driver updates are needed.
For production infrastructure, updates should eventually move into the organization’s normal maintenance and patching process.
The initial deployment is also a good time to confirm that update management is working before the server becomes critical.
Configure Time and Time Zone
Incorrect server time can cause problems that initially appear unrelated to the clock.
Authentication, logs, certificates, scheduled tasks, and distributed systems all depend on accurate time.
Confirm:
- the correct time zone,
- current date and time,
- and the intended time synchronization configuration.
This is especially important before deploying Active Directory roles.
Do not ignore a small clock difference during server setup.
Time configuration is infrastructure configuration.
Review Windows Defender Firewall
Do not disable Windows Defender Firewall as a general troubleshooting step during deployment.
Server roles and applications may require specific network communication.
Document the required ports and rules.
When a service does not work, identify the communication requirement rather than permanently turning off the firewall.
For example, an application server may require communication with:
- database servers,
- domain controllers,
- management systems,
- backup infrastructure,
- or client devices.
Firewall configuration should follow the intended traffic flow.
A server that works only when the firewall is completely disabled is not fully configured.
Verify Drivers, Firmware, and Hardware Health
For physical servers, review the hardware platform after Windows Server installation.
Check:
- Device Manager or the relevant management tools
- Network adapter status
- Storage controller status
- Vendor management agents
- Firmware requirements
- RAID health
- Hardware event logs
Enterprise server platforms may use dedicated remote management interfaces and vendor update tools.
The operating system installation completing successfully does not automatically confirm that every hardware component is using the preferred production driver or firmware version.
For virtual machines, install or verify the appropriate virtualization integration components and confirm that the virtual hardware configuration matches the workload.
Verify Windows Server Edition and Activation Status
Before adding production roles, confirm that the installed Windows Server edition matches the deployment plan.
Verify whether the server is running:
- Standard
- Datacenter
- Evaluation
- or another applicable installation and licensing state
This is particularly important when installation media contains several edition options.
Microsoft documents supported edition and license-type conversion paths, but not every edition or installation-option conversion is available in every direction.
For example, Server Core and Desktop Experience cannot be converted into one another after installation.
It is better to identify an incorrect edition or installation choice before the server hosts production workloads.
Add Windows Server Roles Only After the Base Configuration Is Ready
Once the base server configuration is complete, install the roles required for the server’s intended purpose.
Examples include:
- Active Directory Domain Services
- DNS Server
- DHCP Server
- Hyper-V
- File and Storage Services
- Remote Desktop Services
Do not install roles simply because they are available in Server Manager.
Each role should have a reason to exist on that server.
For example, if the system is intended to become a dedicated Hyper-V host, review the Windows Server Hyper-V Licensing Guide before finalizing the virtualization environment.
If the server will provide Remote Desktop Services, our Windows Server RDS CAL Licensing Guide explains the additional CAL model and RD License Server considerations.
A server role should be part of the architecture plan, not an experiment on a production system.
Common Windows Server 2025 Installation Mistakes
Selecting Server Core Without Understanding the Management Model
Server Core is a strong option for many infrastructure roles, but administrators should be prepared to use PowerShell, SConfig, and remote management tools.
Do not select Core and assume the full desktop GUI can be added later.
Selecting Desktop Experience by Habit
The opposite mistake is installing Desktop Experience on every server because it feels familiar.
Evaluate whether the server actually requires local graphical tools.
Choosing the Wrong Edition
Standard and Datacenter have different virtualization rights and capabilities.
Review the deployment before selecting the edition in Setup.
Installing to the Wrong Disk
Servers may contain multiple local or logical storage volumes.
Verify the target disk before deleting partitions or starting the installation.
Using DHCP Without Reviewing the Server Role
A temporary DHCP address may be acceptable during installation, but many infrastructure server roles require planned and predictable network configuration.
Adding Roles Before Updating the Server
Complete the base operating system review and update process before making the server a critical infrastructure component.
Disabling the Firewall
Turning off the firewall may hide a missing application or network configuration requirement.
Configure required communication rules instead.
Using the Physical Hyper-V Host for Unrelated Workloads
If the server will become a Hyper-V host, keep the physical operating system focused on hosting and managing virtual environments where the architecture and licensing plan depend on that host-use model.
Ignoring Licensing Until After Deployment
Installation and licensing are different processes, but they should be planned together.
Core count, edition, virtualization, CALs, and RDS access may all affect the final server design.
Windows Server 2025 Installation Checklist
Before considering the installation complete, verify:
- Correct Windows Server edition installed
- Correct Server Core or Desktop Experience option selected
- Administrator credential configured securely
- Server renamed
- Network configuration documented
- Static IP configured where required
- DNS settings reviewed
- Time zone and time synchronization checked
- Windows updates installed
- Required drivers and firmware reviewed
- Firewall enabled and configured
- Activation and edition status verified
- Event logs reviewed for obvious hardware or operating system issues
- Remote management tested
- Server role documented
- Backup and recovery plan identified
Only then move on to the production server role.
Frequently Asked Questions About Installing Windows Server 2025
Can I install Windows Server 2025 from a USB drive?
Yes. Windows Server installation media can be prepared on a bootable USB drive and used to install the operating system on compatible hardware.
Should I choose Server Core or Desktop Experience?
Server Core is generally recommended unless the additional graphical interface or local GUI management tools are required. The correct choice depends on the server role, application compatibility, and management model.
Can I add Desktop Experience to Server Core later?
No. Windows Server 2025 does not support converting between Server Core and Server with Desktop Experience after installation. Changing the installation option requires a clean installation.
What happens if I choose Windows Server Standard instead of Datacenter?
The installed edition affects features and virtualization rights. Review the intended infrastructure before choosing Standard or Datacenter.
Should a Windows Server use a static IP address?
Many infrastructure server roles require predictable network configuration. Domain controllers, DNS servers, and other critical services should be deployed according to a planned network design.
Should I install Active Directory immediately after Windows Server Setup?
It is better to complete the base server configuration first. Review networking, server name, time, updates, and operating system health before promoting a server to a domain controller.
Can I disable Windows Defender Firewall during installation?
The firewall should not be permanently disabled as a general deployment step. Configure the required network rules for server roles and applications.
Can Windows Server 2025 be installed in a virtual machine?
Yes. Windows Server 2025 can be deployed as a virtual machine on a supported virtualization platform when the virtual hardware and licensing requirements are addressed.
Do I need a product key during installation?
The requirement can depend on the installation media, edition, and licensing channel. Confirm that the installed edition and activation state match the organization’s deployment and licensing plan.
Can I change from Standard to Datacenter later?
Microsoft documents supported edition conversion paths, including certain Standard-to-Datacenter scenarios. Review the current conversion requirements for the installed edition and licensing type before making changes.
Final Thoughts
A successful Windows Server 2025 installation is not measured by how quickly the server reaches the login screen.
The installation is only the beginning of the deployment.
Choose Server Core or Desktop Experience based on the management and application requirements.
Select Standard or Datacenter based on the planned infrastructure.
Install Windows Server on the correct storage.
Then establish the server’s base configuration before adding production roles.
Rename the server.
Configure networking.
Review DNS.
Install updates.
Check time configuration.
Verify hardware health.
Keep the firewall enabled and configure the communication the server actually requires.
Once that foundation is stable, add the server role the system was designed to provide.
If you are still planning the physical hardware, continue with our Windows Server 2025 System Requirements Guide.
For virtualization deployments, read the Windows Server Hyper-V Licensing Guide.
For licensing calculations, see the Windows Server Core Licensing Guide and the broader Complete Windows Server Licensing Guide.
The next guide in this Windows Server series covers Windows Server 2025 system requirements, hardware planning, memory sizing, storage considerations, and compatibility checks before deployment.