Windows Server 2025 / How to Add and Remove Roles and Features
A Windows Server role provides a major service such as DNS or a website; features include supporting components and administration tools. Server Manager and Install-WindowsFeature can install them, but service configuration and client testing remain separate tasks.
Understand roles, role services, and features
One role can contain several role services. Management tools are also distinct from the service they administer: installing DNS tools on a management PC does not turn it into a DNS server.
| Component | Example or purpose |
|---|---|
| Role | A principal service such as DNS Server |
| Role service | A specific component of a larger role |
| Feature or tool | Windows Server Backup or a role’s management console |
Every additional component adds servicing and management work. Install the item needed for the current lab and review why dependencies are requested instead of selecting every subfeature.
Confirm the target and privileges
Check administrative privileges, server name, OS version, and free space. In a remote management window, the target may differ from the computer where you are signed in. Run these queries in elevated Windows PowerShell on the server:
hostname Get-WindowsFeature | Where-Object Installed | Select-Object Name,DisplayName
Windows clients can have different modules and installation methods. Components whose payload was removed can require Windows Update or matching installation media.
Add a feature through Server Manager
The example installs Windows Server Backup, avoiding premature AD DS or DNS installation that would change later labs. Microsoft’s roles and features guide explains target selection and management tools.
- Open Server Manager → Manage → Add Roles and Features.
- Choose Role-based or feature-based installation and verify the target server name.
- Leave the server roles unchanged and continue to Features.
- Select Windows Server Backup and review the confirmation summary.
- Allow an automatic restart only after assessing the maintenance window and service impact, then install.
Read the success and restart-required results. If a tool is missing, recheck installation state and whether its management component is separate. Core may require command line or remote administration instead of a local graphical console.
Install and verify with PowerShell
If the GUI already installed the feature, query its state rather than treating repeated installation as a required step. Otherwise run Install-WindowsFeature. No automatic -Restart switch is used:
Get-WindowsFeature -Name Windows-Server-Backup Install-WindowsFeature -Name Windows-Server-Backup Get-WindowsFeature -Name Windows-Server-Backup
Check that Install State is Installed. For roles that need management tools, -IncludeManagementTools can include supported tools, but it does not provide unsupported graphical consoles on Core.
An installed role is not a configured service. AD DS still needs promotion; DHCP needs scopes and other settings. Record installation, configuration, and client usability as distinct states.
Review dependencies and data before removal
To undo only the backup feature added in this lab, first review the proposed change. Do not remove it if other work already depends on it:
Uninstall-WindowsFeature -Name Windows-Server-Backup -WhatIf Uninstall-WindowsFeature -Name Windows-Server-Backup
-WhatIf previews an intended action, not every operational consequence. Role removal does not necessarily preserve or clean up accounts, zones, or content as you intend. A domain controller requires proper demotion before removing role binaries.
For source errors, check connectivity and media matching the OS version, language, and edition. Do not point setup at an unrelated ISO or weaken server security just to dismiss the error.









