Remote Server Administration Tools (RSAT) are essential for IT professionals who manage Windows Servers from a remote Windows workstation. Selecting the correct RSAT version is crucial to ensure compatibility and avoid potential issues. This guide provides clear recommendations on which RSAT version to use based on your Windows client and server operating systems, along with troubleshooting common problems you might encounter during installation and usage.
RSAT Version Recommendations Based on Your Environment
To streamline your remote server management, it’s vital to match your RSAT version with your operating systems. Here’s a breakdown to guide you:
For Windows 10 (Version 1809 and Later) Managing Windows Server 2019 and Earlier
If you are running Windows 10 October 2018 Update (version 1809) or any subsequent version, and you need to manage Windows Server 2019 or older versions, the recommended approach is to install RSAT Features on Demand (FODs) directly from Windows 10.
This method offers a seamless installation experience and ensures compatibility with the latest Windows 10 features. You can easily install RSAT FODs through the Windows 10 Settings app. For detailed instructions, refer to the “Install Instructions” section within Windows 10 settings by searching for “Manage optional features”.
For Windows 10 (Version 1803 and Earlier) Managing Windows Server, version 1803 or 1709
If your client workstation is running Windows 10 April 2018 Update (version 1803) or an earlier version, and you are managing Windows Server, version 1803 or Windows Server, version 1709, you should download and install the WS_1803 RSAT package.
This specific package is designed for compatibility with these older Windows 10 versions and allows you to effectively manage servers running version 1803 or 1709.
For Windows 10 (Version 1803 and Earlier) Managing Windows Server 2016 and Earlier
Similarly, for those using Windows 10 April 2018 Update (version 1803) or earlier to manage Windows Server 2016 or previous versions, the appropriate solution is to download and install the WS2016 RSAT package.
This package provides the necessary tools to administer older Windows Server environments from your Windows 10 workstation.
Troubleshooting Common RSAT Issues
While RSAT is designed to be robust, users sometimes encounter issues. Here’s a guide to common problems and their resolutions:
RSAT FOD Installation Failure with Error Code 0x800f0954
Impact: This issue primarily affects RSAT FODs on Windows 10 1809 (October 2018 Update) in environments utilizing WSUS (Windows Server Update Services) or SCCM (System Center Configuration Manager).
Resolution: In domain-joined PCs that receive updates via WSUS or SCCM, installing FODs may fail because the system is configured to get updates from an internal source rather than directly from Windows Update. To resolve this, you need to modify a Group Policy setting to enable downloading FODs directly from Windows Update or a designated local share.
For detailed steps on adjusting this setting, consult this Microsoft documentation. This adjustment allows your system to retrieve the necessary FOD installation files.
No Status or Progress Display During RSAT FOD Installation via Settings App
Impact: This is a user interface issue specific to RSAT FODs on Windows 10 1809 (October 2018 Update).
Resolution: When installing RSAT FODs through the Settings app, the installation progress might not be immediately visible on the current page. To check the status, simply click the “Back” button within the Settings app. This will navigate you to the “Manage optional features” page, where the installation status for your RSAT FODs will be displayed.
RSAT FOD Uninstallation via Settings App May Fail
Impact: This issue can occur with RSAT FODs on Windows 10 1809 (October 2018 Update).
Resolution: Uninstallation failures are often due to dependency requirements between RSAT tools. If tool A is dependent on tool B, attempting to uninstall tool A while tool B is still installed will fail. The solution is to first uninstall the dependent RSAT tool (tool B) and then proceed to uninstall tool A. Refer to the list of RSAT FODs including dependencies to understand tool dependencies.
RSAT FOD Uninstallation Appears Successful but Tools Remain Installed
Impact: This is another behavior observed with RSAT FODs on Windows 10 1809 (October 2018 Update).
Resolution: In some instances, even after seemingly successful uninstallation, the RSAT tools might still be present on the system. A simple restart of your PC will finalize the removal process and completely uninstall the tools.
RSAT Missing After Windows 10 Upgrade
Impact: This issue affects any RSAT installations performed using .MSU packages (prior to FODs). These installations are not automatically preserved across Windows 10 upgrades.
Resolution: Due to the delivery method of RSAT .MSU packages as Windows Update packages, they cannot persist through OS upgrades. Therefore, you must reinstall RSAT after upgrading Windows 10. This limitation is a key reason for the shift to FODs starting with Windows 10 1809. RSAT FODs, once installed, will persist across subsequent Windows 10 version upgrades, offering a more seamless experience.
DNS Tools Missing
Impact: This specifically affects users of the WS_1709 RSAT package.
Resolution: If you are using the WS_1709 RSAT package and find DNS Tools missing, the recommended solutions are to upgrade to RSAT FODs, use the WS_1803 or WS2016 RSAT package, or apply the workaround detailed in this Microsoft support article.
Cannot Turn Off Individual RSAT Components
Impact: This limitation affects users of the WS_1803 and WS_1709 RSAT packages on Windows 10 1803/1709 (April 2018 Update/Fall Creators Update).
Resolution: The inability to disable individual RSAT components in these older packages can be overcome by using RSAT FODs or utilizing the WS2016 RSAT package on Windows 10 1607 (Anniversary Update), which offers more granular control over component selection.
Tabs Missing from MMC Properties
Impact: This is an issue for Windows 10 clients older than version 1607 (Anniversary Update).
Resolution: To resolve missing tabs in MMC (Microsoft Management Console) properties, you need to update to the latest version of Windows 10 client and reinstall RSAT. The latest Windows 10 versions include the necessary updates for full MMC functionality.
Shielding Data File Wizard Cannot Create Shielding Data Files
Impact: This issue affects WS_1709 RSAT package users on Windows 10 1709 (Fall Creators Update).
Resolution: To use the Shielding Data File Wizard effectively, you should use RSAT FODs, the WS_1803 RSAT package on Windows 10 1803 (April 2018 Update), or the WS2016 RSAT package on Windows 10 1607 (Anniversary Update). Alternatively, you can use the built-in RSAT tools in Windows Server, version 1709 to create shielding data files for both Windows and Linux shielded VMs.
Template Disks Created from the Template Disk Wizard Do Not Boot
Impact: This issue is experienced by WS_1709 RSAT package users on Windows 10 1709 (Fall Creators Update).
Resolution: Similar to the Shielding Data File Wizard issue, to create bootable template disks, you should use RSAT FODs, the WS_1803 RSAT package on Windows 10 1803 (April 2018 Update), or the WS2016 RSAT package on Windows 10 1607 (Anniversary Update). Another option is to use the built-in RSAT tools in Windows Server, version 1709.
IPAM in Server Manager Prompts to Install Even Though IPAM is Already Installed
Impact: This issue affects IPAM (IP Address Management) users on Windows 10 1803/1709 (April 2018 Update/Fall Creators Update).
Resolution: If Server Manager incorrectly prompts you to install IPAM, even when it’s already installed, the solution is to use RSAT FODs or utilize IPAM from an RSAT package installed on Windows 10 1607 (Anniversary Update) or 1703 (Creators Update). These versions provide a more stable IPAM integration.
By following these recommendations and troubleshooting steps, you can effectively manage your Windows Servers remotely using the correct RSAT version and quickly resolve common issues.
