Windows Server 2025 / How to Install RSAT on a Windows Management PC
Remote Server Administration Tools (RSAT) let you manage Windows Server roles from a Windows client. Install the tools needed for Active Directory, DNS, or Group Policy on a supported management PC instead of opening a desktop session on every server.
Check the PC and server prerequisites
This lab uses a supported Windows 11 Pro or Enterprise management PC. Do not apply the same procedure to Home without checking support. Microsoft’s RSAT installation guide distinguishes Windows client capabilities from server features.
CLIENT1 can double as the lab management PC. In production, separating everyday browsing from privileged administration helps limit exposure. Installing tools requires local administrative rights; managing a server requires separate rights on that target.
- Confirm network connectivity to the server.
- Provide Windows Update or an approved Features on Demand source.
- For domain administration, prepare working domain DNS and the appropriate domain account.
Install only the required optional features
- Search Start for Optional features and open the Settings result.
- Choose the option to view or add features, then search for RSAT.
- Select the required AD DS and LDS, DNS, or Group Policy tools.
- Wait for installation, verify the installed list, and save work before any required restart.
Settings locations can change with the Windows build, so use its search rather than assuming one fixed path. If installation is unavailable or stalls, check organizational policies for the optional feature source. Installing a smaller set also makes failures easier to isolate.
Check installation with PowerShell
On the management PC, open elevated PowerShell and query the available capability names. Install the AD tool only if its exact name is present. Do not confuse this with Install-WindowsFeature on Windows Server.
Get-WindowsCapability -Online | Where-Object Name -like 'RSAT*' | Select-Object Name,State Add-WindowsCapability -Online -Name 'Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0' Get-WindowsCapability -Online -Name 'Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0'
Installed means the selected tools are present. DNS and Group Policy tools need their own capabilities; find their exact names in the first query instead of assuming the AD package includes every console.
Test console startup separately from server connection
| Tool | How to open |
|---|---|
| Active Directory Users and Computers | dsa.msc |
| DNS Manager | dnsmgmt.msc |
| Group Policy Management | gpmc.msc |
| Server Manager | Search Start for Server Manager |
Before the domain and services exist, a console may open with no usable target. At this stage, verify installation and startup. After configuring the roles, connect to the actual DNS server or domain.
For domain management, the PC must resolve domain records through AD DNS. A console opening successfully does not prove that the current account can change the remote server.
Troubleshoot and remove unused tools
- Download failure: check connectivity, proxy settings, and the optional feature source policy.
- Console startup failure: verify the installed capability and Windows edition.
- Unknown server name: inspect DNS settings and query results.
- Access denied: check the actual account and delegated permissions; obtain only the needed rights.
Remove unused tools through Optional features. Removing a management console does not delete the server role or directory data. Review temporary connections and credential use, and keep an independent server recovery path.









