How to Use Remote Server Administration Tools (RSAT) on Windows Server 2012 R2

How to Use Remote Server Administration Tools (RSAT) on Windows Server 2012 R2

Remote Server Administration Tools (RSAT) for Windows Server 2012 R2 is a collection of MMC snap-ins, command-line tools, PowerShell modules, and management consoles that enable administrators to manage Windows Server 2012 R2 roles and features remotely from a Windows 8.1 workstation or another Windows Server 2012 R2 server. RSAT eliminates the need to physically log in to each server or use Remote Desktop for routine administrative tasks — you manage the server from your workstation as if you were sitting at the server console.

RSAT on Windows Server 2012 R2 can be installed as a Feature on Demand (available through Server Manager or PowerShell) and covers tools for Active Directory, DNS, DHCP, File and Storage Services, Hyper-V, WSUS, Group Policy, and more. This guide covers installing RSAT, configuring the individual tool sets, and using both GUI and PowerShell tools for remote server management.

Prerequisites

– Windows Server 2012 R2 (as management workstation) or Windows 8.1 with RSAT package
– Administrative credentials on both the local machine and target servers
– Target servers must have the corresponding roles installed and WinRM enabled
– Active Directory domain membership (for AD-related tools) or explicit credentials for workgroup servers
– Network connectivity between management host and target servers

Step 1: Install RSAT on Windows Server 2012 R2

On Windows Server 2012 R2 acting as a management server, RSAT components are available as features. Install all RSAT tools:

# Install all RSAT tools at once
Install-WindowsFeature RSAT -IncludeAllSubFeature

# Verify installation
Get-WindowsFeature RSAT* | Where-Object InstallState -eq "Installed" | 
    Select-Object Name, DisplayName | Sort-Object Name

Install only specific RSAT subsets based on need:

# Install individual RSAT components
Install-WindowsFeature RSAT-AD-Tools        # Active Directory tools
Install-WindowsFeature RSAT-DNS-Server      # DNS Manager
Install-WindowsFeature RSAT-DHCP            # DHCP Manager
Install-WindowsFeature RSAT-File-Services   # File Server Resource Manager
Install-WindowsFeature RSAT-Hyper-V-Tools   # Hyper-V Manager
Install-WindowsFeature RSAT-WSUS            # WSUS Administration Console
Install-WindowsFeature GPMC                 # Group Policy Management Console

Step 2: Active Directory Tools

The AD RSAT tools include Active Directory Users and Computers (ADUC), Active Directory Domains and Trusts, Active Directory Sites and Services, and the ADSI Edit advanced interface.

Launch tools from the Administrative Tools folder or via Run:

# Launch Active Directory Users and Computers
dsa.msc

# Launch Active Directory Sites and Services
dssite.msc

# Launch ADSI Edit (low-level AD attribute editor)
adsiedit.msc

Use the Active Directory PowerShell module (part of RSAT-AD-Tools) for scriptable AD management:

Import-Module ActiveDirectory

# Query users in a specific OU
Get-ADUser -Filter * -SearchBase "OU=Staff,DC=domain,DC=com" |
    Select-Object Name, SamAccountName, Enabled, LastLogonDate

# Find disabled accounts
Get-ADUser -Filter { Enabled -eq $false } | Select-Object Name, SamAccountName, DistinguishedName

# Get group members
Get-ADGroupMember -Identity "Domain Admins" | Select-Object Name, SamAccountName, objectClass

# Reset a user's password
Set-ADAccountPassword -Identity "jsmith" -NewPassword (ConvertTo-SecureString "NewPass123!" -AsPlainText -Force) -Reset

Step 3: DNS Management with RSAT

The DNS Server Tools (RSAT-DNS-Server) install the DNS Manager MMC snap-in and the DnsServer PowerShell module:

# Launch DNS Manager
dnsmgmt.msc

# Connect to a specific DNS server in DNS Manager:
# Right-click DNS > Connect to DNS Server > enter server name

Use the DnsServer module for PowerShell-based DNS management:

Import-Module DnsServer

# List all DNS zones on a remote DNS server
Get-DnsServerZone -ComputerName "DNS01" | Select-Object ZoneName, ZoneType, IsDsIntegrated

# Add an A record
Add-DnsServerResourceRecordA -ZoneName "domain.com" -Name "webserver01" -IPv4Address "192.168.1.50" -ComputerName "DNS01"

# View all A records in a zone
Get-DnsServerResourceRecord -ZoneName "domain.com" -ComputerName "DNS01" -RRType A |
    Select-Object HostName, RecordType, @{N="IPAddress"; E={$_.RecordData.IPv4Address}}

# Create a conditional forwarder
Add-DnsServerConditionalForwarderZone -Name "partner.com" -MasterServers "10.1.1.1" -ComputerName "DNS01"

Step 4: DHCP Management with RSAT

Install and use the DHCP console and DhcpServer PowerShell module:

# Launch DHCP Manager
dhcpmgmt.msc

Import-Module DhcpServer

# List all DHCP scopes on a remote server
Get-DhcpServerv4Scope -ComputerName "DHCP01" | 
    Select-Object ScopeId, Name, SubnetMask, State,
    @{N="RangeStart"; E={"$($_.StartRange)"}},
    @{N="RangeEnd";   E={"$($_.EndRange)"}}

# Get scope statistics (leases in use)
Get-DhcpServerv4ScopeStatistics -ComputerName "DHCP01" |
    Select-Object ScopeId, PercentageInUse, AddressesFree, AddressesInUse

# Create a new DHCP scope
Add-DhcpServerv4Scope -ComputerName "DHCP01" `
    -Name "Office Network" `
    -StartRange "192.168.10.100" `
    -EndRange "192.168.10.200" `
    -SubnetMask "255.255.255.0" `
    -State Active

# View all active leases
Get-DhcpServerv4Lease -ComputerName "DHCP01" -ScopeId "192.168.10.0" |
    Select-Object IPAddress, ClientId, HostName, LeaseExpiryTime | Sort-Object IPAddress

Step 5: Group Policy Management

The GPMC (Group Policy Management Console) is one of the most frequently used RSAT tools:

# Launch Group Policy Management Console
gpmc.msc

Import-Module GroupPolicy

# List all GPOs in the domain
Get-GPO -All | Select-Object DisplayName, Id, GpoStatus, CreationTime, ModificationTime | Sort-Object DisplayName

# Get GPO link status on an OU
Get-GPInheritance -Target "OU=Servers,DC=domain,DC=com" | 
    Select-Object -ExpandProperty GpoLinks

# Create a new GPO
New-GPO -Name "Server Security Baseline" -Comment "Security settings for all servers"

# Link a GPO to an OU
New-GPLink -Name "Server Security Baseline" -Target "OU=Servers,DC=domain,DC=com" -Enforced Yes

# Generate an RSoP (Resultant Set of Policy) report for a computer
Get-GPResultantSetOfPolicy -Computer "Server01" -ReportType HTML -Path "C:ReportsRSoP_Server01.html"

Step 6: File Services Management with RSAT

Manage file server resources on remote servers using File Server Resource Manager (FSRM) tools:

# Install FSRM management tools
Install-WindowsFeature RSAT-File-Services

# Launch File Server Resource Manager
fsrm.msc

# List shared folders on a remote server
Get-SmbShare -CimSession (New-CimSession -ComputerName "FileServer01") |
    Where-Object { $_.ShareType -eq "FileSystemDirectory" } |
    Select-Object Name, Path, Description

# View share permissions
Get-SmbShareAccess -Name "Data" -CimSession (New-CimSession -ComputerName "FileServer01")

# Create a new SMB share on a remote server
New-SmbShare -Name "Reports" -Path "D:Reports" -FullAccess "DOMAINServerAdmins" `
    -ReadAccess "DOMAINDomain Users" `
    -CimSession (New-CimSession -ComputerName "FileServer01")

Step 7: Hyper-V Management with RSAT

Manage Hyper-V hosts and virtual machines remotely with RSAT-Hyper-V-Tools:

# Launch Hyper-V Manager
virtmgmt.msc

Import-Module Hyper-V

# List all VMs on a remote Hyper-V host
Get-VM -ComputerName "HV01" | Select-Object Name, State, CPUUsage, MemoryAssigned, Uptime

# Start a VM remotely
Start-VM -Name "WebServer01" -ComputerName "HV01"

# Take a checkpoint (snapshot)
Checkpoint-VM -Name "WebServer01" -ComputerName "HV01" -SnapshotName "PrePatch_$(Get-Date -Format 'yyyyMMdd')"

# Get VM resource usage
Get-VM -ComputerName "HV01" | ForEach-Object {
    $stats = Get-VMMemory $_.Name -ComputerName "HV01"
    [PSCustomObject]@{
        VM            = $_.Name
        State         = $_.State
        CPUPct        = $_.CPUUsage
        MemAssignedMB = [math]::Round($_.MemoryAssigned/1MB)
    }
} | Format-Table -AutoSize

Step 8: Connect RSAT Tools to Remote Servers

Most RSAT MMC consoles support connecting to remote servers. The standard workflow is to open the tool locally and then connect to the remote target. For example, connecting DNS Manager to a remote DNS server:

# DNS Manager: Right-click DNS root > Connect to DNS Server > enter hostname

# Computer Management: Connect to remote computer
# Right-click Computer Management > Connect to Another Computer

# Device Manager: Connect via Computer Management path

# For tools that don't have built-in remote connection, use PowerShell remoting
Invoke-Command -ComputerName "Server01" -ScriptBlock {
    # Run management commands on the remote server
    Get-WindowsFeature | Where-Object InstallState -eq "Installed" | Select-Object Name
}

Step 9: Manage Windows Server Update Services (WSUS) Remotely

RSAT-WSUS installs the WSUS Administration Console for managing Windows update deployments:

# Launch WSUS Administration Console
wsus.msc

# Connect to a remote WSUS server:
# In the console, right-click the root > Connect to Server > enter server name and port

# Using PowerShell to query WSUS update compliance
$wsusServer  = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer("WSUS01", $false, 8530)
$computerGroups = $wsusServer.GetComputerTargetGroups()
$computers  = $wsusServer.GetComputerTargets()
$computers | Select-Object FullDomainName, LastSyncTime, LastSyncResult | Sort-Object FullDomainName | Format-Table -AutoSize

Summary

RSAT on Windows Server 2012 R2 consolidates all role-specific management tools onto a single administrative workstation, dramatically reducing the time needed to manage complex server environments. By installing RSAT components aligned with the roles deployed in your environment — Active Directory, DNS, DHCP, Group Policy, File Services, and Hyper-V — and pairing them with the corresponding PowerShell modules, administrators gain both the familiar GUI consoles and scriptable command-line interfaces for every server role. This dual capability supports both ad-hoc troubleshooting through the GUI and automated operations through PowerShell, making RSAT a foundational component of any Windows Server 2012 R2 management strategy.