Windows Server roles and features add specific server capabilities — DNS, DHCP, IIS, Active Directory, Hyper-V, File Services, and many others. They are installed on demand, keeping the base installation lean. Here is how to install roles and features, and what to consider before you do.
Roles vs Features
The distinction matters when navigating the installation wizard:
- Roles are major server functions — the primary purpose of the server. Examples: Active Directory Domain Services, DNS Server, DHCP Server, Web Server (IIS), File and Storage Services, Hyper-V, Remote Desktop Services.
- Features are supporting capabilities, often used alongside roles. Examples: .NET Framework versions, Windows Server Backup, Failover Clustering, RSAT tools, Telnet Client, PowerShell modules.
Many roles require specific features as dependencies — the wizard handles this automatically.
Install Roles and Features via Server Manager
- Open Server Manager and click Manage → Add Roles and Features
- Click Next past the Before You Begin page
- Select Role-based or feature-based installation and click Next
- Select the target server from the server pool and click Next
- Select server roles: tick the roles you want to install. When you tick a role, a popup may appear asking you to add required features — click Add Features to include them.
- Select features: add any standalone features needed
- Follow any role-specific configuration pages (e.g. IIS shows role services to select)
- Review the Confirmation page — tick Restart the destination server automatically if required if the installation needs a reboot
- Click Install
A progress bar shows installation status. Some roles require post-installation configuration — Server Manager will show a yellow warning flag with a link to complete configuration (e.g. “Promote this server to a domain controller” after installing AD DS).
Install Roles and Features via PowerShell
# Install a single role
Install-WindowsFeature -Name Web-Server -IncludeManagementTools
# Install multiple roles/features at once
Install-WindowsFeature -Name DNS, DHCP, Web-Server -IncludeManagementTools
# Install a role with all sub-features
Install-WindowsFeature -Name Web-Server -IncludeAllSubFeature -IncludeManagementTools
# Install and restart if needed
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -RestartCommon Role Names for PowerShell
AD-Domain-Services— Active Directory Domain ServicesDNS— DNS ServerDHCP— DHCP ServerWeb-Server— IIS Web ServerHyper-V— Hyper-V virtualisationFile-Services— File and Storage ServicesRSAT-AD-Tools— Active Directory management toolsWindows-Server-Backup— Windows Server BackupFailover-Clustering— Failover Cluster ManagerNPS— Network Policy Server (RADIUS)
# List all available roles and features
Get-WindowsFeature | Where-Object {$_.InstallState -eq 'Available'} | Select-Object Name, DisplayName
# List all currently installed roles and features
Get-WindowsFeature | Where-Object {$_.InstallState -eq 'Installed'} | Select-Object Name, DisplayNameRemove Roles and Features
Removing unused roles reduces the attack surface and frees resources:
# Remove a role
Uninstall-WindowsFeature -Name Web-Server -IncludeManagementTools
# Remove and restart
Uninstall-WindowsFeature -Name Hyper-V -RestartIn Server Manager: Manage → Remove Roles and Features — follow the same wizard in reverse.
Install Roles on a Remote Server
# Install a role on a remote server
Install-WindowsFeature -Name DNS -ComputerName REMOTESERVER -IncludeManagementToolsIn Server Manager, you can also add the remote server to the server pool (Manage → Add Servers) and then install roles on it without leaving your local console.
Things to Check Before Installing a Role
- Disk space: some roles (especially Hyper-V and RDS) need significant space for VMs and user profile data
- RAM: adding roles consumes memory — a DNS/DHCP server needs little; adding RDS or SQL Server needs substantial RAM
- Reboot requirement: most roles require a restart — schedule it during a maintenance window
- Licence compliance: some roles (RDS, RDS CALs) have additional licensing requirements beyond the base server licence
- Firewall rules: installing a role usually creates firewall rules automatically, but verify that the required ports are open in any external firewalls
