Remote Server Administration Tools for Windows 7 with Service Pack 1 (SP1) Remote Server Administration Tools for Windows® 7 with SP1 enables IT administrators to manage roles and features that are installed on computers that are running Windows Server® 2008 R2, Windows Server® 2008, or Window. If a language accessory pack is described as having partial localization, some parts of Office may still display in the language of your copy of Microsoft Office. If a language is listed only once, for example German, then that pack includes the tools for all countries/regions that use that language. Administrative Tools is the collective name for several advanced tools in Windows that are used mainly by system administrators. It's available in Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP, and Windows Server operating system.
-->This article describes the tools that are available in Remote Server Administration Tools (RSAT) for Windows.
Original product version: Windows 10, version 1909, Windows 10, version 1903, Windows 10, version 1809. Windows 7 Service Pack 1. Windows Server 2019. Windows Server 2012 R2
Original KB number: 2693643
Introduction
RSAT enables IT administrators to remotely manage roles and features in Windows Server from a computer that is running Windows 10 and Windows 7 Service Pack 1.
You can't install RSAT on computers that are running Home or Standard editions of Windows. You can install RSAT only on Professional or Enterprise editions of the Windows client operating system. Unless the download page specifically states that RSAT applies to a beta, preview, or other prerelease version of Windows, you must be running a full (RTM) release of the Windows operating system to install and use RSAT. Some users have found ways of manually cracking or hacking the RSAT MSU to install RSAT on unsupported releases or editions of Windows. This behavior is a violation of the Windows end-user license agreement.
Installing RSAT is similar to installing Adminpak.msi in Windows 2000-based or Windows XP-based client computers. However, there's one major difference: in Windows 7, the tools aren't automatically available after you download and install RSAT. Enable the tools that you want to use by using Control Panel. To enable the tools, click Start, click Control Panel, click Programs and Features, and then click Turn Windows features on or off.
In the RSAT releases for Windows 10, tools are again all enabled by default. You can open Turn Windows features on or off to disable tools that you don't want to use for Windows 7.
For RSAT in Windows 7, you must enable the tools for the roles and features that you want to manage after you run the downloaded installation package.
Note
You can't do the following changes for RSAT in Windows 8 or later versions.
If you have to install management tools in Windows Server 2012 R2 for specific roles or features that are running on remote servers, you don't have to install additional software. Start the Add Roles and Features Wizard in Windows Server 2012 R2 and later versions. Then, on the Select Features page, expand Remote Server Administration Tools, and then select the tools that you want to install. Complete the wizard to install your management tools.
Download locations for RSAT
RSAT for Windows 10 platform and tools support matrix
| Remote Server Administration Tools Technology | Description | Manages technology in Windows Server 2012 R2 | Manages technology in Windows Server 2016 Technical Preview and Windows Server 2012 R2 |
|---|---|---|---|
| Active Directory Certificate Services (AD CS) tools | AD CS tools include the Certification Authority, Certificate Templates, Enterprise PKI, and Online Responder Management snap-ins. | √ | √ |
| Active Directory Domain Services (AD DS) tools and Active Directory Lightweight Directory Services (AD LDS) tools | AD DS and AD LDS tools include the following tools: - Active Directory Administrative Center - Active Directory Domains and Trusts - Active Directory Sites and Services - Active Directory Users and Computers - ADSI Edit - Active Directory module for Windows PowerShell - Tools such as
| √ | |
| Best Practices Analyzer | Best Practices Analyzer cmdlets for Windows PowerShell | √ | √ |
| BitLocker Drive Encryption Administration Utilities | Manage-bde, Windows PowerShell cmdlets for BitLocker, BitLocker Recovery Password Viewer for Active Directory | √ | √ |
| DHCP Server tools | DHCP Server tools include the DHCP Management Console, the DHCP Server cmdlet module for Windows PowerShell, and the Netsh command-line tool. | √ | √ |
| DirectAccess, Routing, and Remote Access | - Routing and Remote Access management console - Connection Manager Administration Kit console - Remote Access provider for Windows PowerShell - Web Application Proxy | √ | √ |
| DNS Server tools | DNS Server tools include the DNS Manager snap-in, the DNS module for Windows PowerShell, and the Ddnscmd.exe command-line tool. | √ | √ |
| Failover Clustering tools | Failover Clustering tools include Failover Cluster Manager, Failover Clusters (Windows PowerShell cmdlets), MSClus, Cluster.exe, Cluster-Aware Updating management console, Cluster-Aware Updating cmdlets for Windows PowerShell | √ | √ GUI tools support Windows Server 2016 Technical Preview and Windows Server 2012 R2. Only PowerShell tools work in Windows Server 2012. |
| File Services tools | File Services tools include the following tools: - Share and Storage Management tools - Distributed File System tools
- File Server Resource Manager tools
- Services for NFS Administration tools - iSCSI management cmdlets for Windows PowerShell - Work Folders Management tools | √ | √ The Share and Storage Management snap-in is deprecated after the release of Windows Server 2016. Storage Replica is new in Windows Server 2016 Technical Preview, and won't work in Windows Server 2012 R2. |
| Group Policy Management tools | Group Policy Management tools include Group Policy Management Console, Group Policy Management Editor, and Group Policy Starter GPO Editor. | √ | √ Group Policy has some new features in Windows Server 2016 Technical Preview that aren't available on older operating systems. |
| Hyper-V tools | Hyper-V tools include the Hyper-V Manager snap-in and the Virtual Machine Connection remote access tool. | Hyper-V tools aren't part of Remote Server Administration Tools for Windows 10. These tools are available as part of Windows 10. You don't have to install RSAT to use the tools. The Hyper-V Manager console for Windows Server 2016 Technical Preview doesn't support managing Hyper-V servers running Server 2008 or Server 2008 R2. | Hyper-V in Windows 10 can manage Hyper-V in Windows Server 2012 R2. |
| IP Address Management (IPAM) Management tools | IP Address Management client console | √ IPAM tools in Remote Server Administration Tools for Windows 10 can't be used to manage IPAM running in Windows Server 2012 R2. | √ IPAM tools in Remote Server Administration Tools for Windows 10 can't be used to manage IPAM running in Windows Server 2012 R2. |
| Network Adapter Teaming, or NIC Teaming | NIC Teaming management console | √ | √ |
| Network Controller | Network Controller PowerShell module | Not available | √ |
| Network Load Balancing tools | Network Load Balancing tools include the Network Load Balancing Manager, Network Load Balancing Windows PowerShell cmdlets, and the NLB.exe and WLBS.exe command-line tools. | √ | √ |
| Remote Desktop Services tools | Remote Desktop Services tools include: - Remote Desktop snap-ins - RD Gateway Manager - tsgateway.msc- RD Licensing Manager - licmgr.exe - RD Licensing Diagnoser - lsdiag.mscUse Server Manager to administer all other RDS role services except RD Gateway and RD Licensing. | √ | √ |
| Server for NIS tools | Server for NIS tools include an extension to the Active Directory Users and Computers snap-in, and the Ypclear.exe command-line tool | These tools aren't available in RSAT for Windows 10 and later releases. | |
| Server Manager | Server Manager includes the Server Manager console. Remote management with Server Manager is available in Windows Server 2016 Technical Preview, Windows Server 2012 R2, and Windows Server 2012. | √ | √ |
| Simple Mail Transfer Protocol (SMTP) Server tools | SMTP Server tools include the SMTP snap-in. | These tools aren't available in RSAT for Windows 8 and later releases. | |
| Storage Explorer tools | Storage Explorer tools include the Storage Explorer snap-in. | These tools aren't available in RSAT for Windows 8 and later releases. | |
| Storage Manager for Storage Area Network (SAN) tools | Storage Manager for SAN tools include the Storage Manager for SAN snap-in and the Provisionstorage.exe command-line tool. | These tools aren't available in RSAT for Windows 8 and later releases. | |
| Volume Activation | Manage Volume Activation, vmw.exe | √ | √ |
| Windows System Resource Manager tools | Windows System Resource Manager tools include the Windows System Resource Manager snap-in and the Wsrmc.exe command-line tool. | √ WSRM has been deprecated in Windows Server 2012 R2. Tools for managing WSRM aren't available in RSAT for Windows 8.1 and later releases of RSAT. | |
| Windows Server Update Services tools | Windows Server Update Services tools include the Windows Server Update Services snap-in, WSUS.msc, and PowerShell cmdlets. | √ | √ |
References
-->The management tools in Exchange Server 2016 and Exchange Server 2019 include the Exchange Management Shell and the Exchange Toolbox. You can install the management tools on other client computers or servers in the Active Directory domain to help you manage your Exchange organization. The management tools have similar operating system, .NET Framework, and Windows Management Framework (Windows PowerShell) requirements as an Exchange server. The notable exception is: you can install the management tools on client versions of Windows. For more information, see Exchange Server system requirements and Exchange Server prerequisites.
Note
The management tools don't include the Exchange admin center (EAC). The EAC is a web-based console that's hosted on Exchange 2016 Mailbox servers, and like any web site, you can access the EAC from other computers. For more information about the EAC, see Exchange admin center in Exchange Server.
For more information about the Exchange Management Shell, see Exchange Server PowerShell (Exchange Management Shell).
What do you need to know before you begin?
Estimated time to complete: 20 minutes
The computer where you want to install the Exchange management tools requires access to Setup.exe in the Exchange installation files. To download the latest version of Exchange, see Updates for Exchange Server.
For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
Tip
Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.
Use the Exchange 2016 Setup wizard to install the Exchange management tools
In File Explorer on the computer where you want to install the management tools, right-click on the Exchange ISO image file that you downloaded, and then select Mount. In the resulting virtual DVD drive that appears, start Exchange Setup by double-clicking
Setup.exe.The Exchange Server Setup wizard opens. On the Check for Updates? page, choose one of the following options, and then click Next to continue:
Connect to the Internet and check for updates: We recommend this option, which searches for updates to the version of Exchange that you're currently installing (it doesn't detect newer Cumulative Updates). This option takes you to the Downloading Updates page that searches for updates. Click Next to continue.
- Don't check for updates right now
The Copying Files page shows the progress of copying files to the local hard drive. Typically, the files are copied to
%WinDir%TempExchangeSetup, but you can confirm the location in the Exchange Setup log atC:ExchangeSetupLogsExchangeSetup.log.On the Introduction page, click Next to continue.
On the License Agreement page, review the software license terms, select I accept the terms in the license agreement, and then click Next to continue.
On the Recommended Settings page, choose one of the following settings:
Use recommended settings: Exchange automatically sends error reports and information about your computer hardware and how you use Exchange to Microsoft. For information about what's sent to Microsoft and how it's used, click ? or the help links on the page.
Don't use recommended settings: These settings are disabled, but you can enable them at any time after Setup completes.
Click Next to continue.
On the Server Role Selection page, configure the following settings:
Select Management tools.
Automatically install Windows Server roles and features that are required to install Exchange: Select this option to have the Setup wizard install the required Windows prerequisites. You might need to reboot the computer to complete the installation of some Windows features. If you don't select this option, you need to install the Windows features manually.
Note: Selecting this option installs only the Windows features that are required by Exchange. You need to install other prerequisites manually. For more information, see Exchange Server prerequisites.
Click Next to continue.
On the Installation Space and Location page, either accept the default installation location (
C:Program FilesMicrosoftExchange ServerV15), or click Browse to choose a new location. Make sure that you have enough disk space available in the location where you want to install the management tools. Click Next to continue.If this is the first installation of Exchange in your organization (Exchange server or the management tools), you arrive on the Exchange Organization page. On this page, configure the following settings:
Specify the name for this Exchange organization: The default value is First Organization, but you typically use the company name for this value. The organization name is used internally by Exchange, isn't typically seen by users, doesn't affect the functionality of Exchange, and doesn't determine what you can use for email addresses.
The organization name can't contain more than 64 characters, and can't be blank.
Valid characters are A to Z, a to z, 0 to 9, hyphen or dash (-), and space, but leading or trailing spaces aren't allowed.
You can't change the organization name after it's set.
Apply Active Directory split permission security model to the Exchange organization: Most organizations don't need to select this option. If you need to separate management of Active Directory security principals and the Exchange configuration, split permissions might work for you. For more information, click ?.
Click Next to continue.
On the Readiness Checks page, verify that the organization and server role prerequisite checks completed successfully. If they haven't, the only option on the page is Retry, so you need to resolve the errors before you can continue.
After you resolve the errors, click Retry to run the prerequisite checks again. You can fix some errors without exiting Setup, while the fix for other errors requires you to restart the computer. If you restart the computer, you need to start over at Step 2.
When no more errors are detected on the Readiness Checks page, the Retry button changes to Install so you can continue. Be sure to review any warnings, and then click Install to install the management tools.
On the Setup Completed page, click Finish, and then restart the computer.
Use Exchange unattended Setup mode to install the Exchange management tools
Microsoft Administrative Tools
In File Explorer on the computer where you want to install the Exchange management tools, right-click on the Exchange ISO image file that you downloaded, and then select Mount.
To install the Exchange management tools from the command line, use the following syntax in elevated command prompt (a Command Prompt window you opened by selecting Run as administrator):
This example uses the Exchange Setup files on drive E: to install the management tools on the local server
Microsoft Windows Administrative Tools
For more information, see Install Exchange using unattended mode.