Effectively managing Windows Servers from a Windows 10 environment relies heavily on using the correct version of Remote Server Administration Tools (RSAT). Selecting the appropriate RSAT package ensures compatibility and access to the necessary tools for your specific server infrastructure. This guide provides clear recommendations for RSAT versions based on your Windows 10 and Windows Server configurations, along with troubleshooting common issues you might encounter.
RSAT Version Recommendations for Windows 10
To ensure seamless server management, choose your RSAT version based on your operating systems:
-
For Windows 10 October 2018 Update (1809) and later, managing Windows Server 2019 or older versions: The recommended approach is to install RSAT Features on Demand (FODs) directly from Windows 10. This method is streamlined and integrated within Windows 10. Refer to the official Microsoft documentation for detailed “Install Instructions” on adding RSAT FODs.
-
For Windows 10 April 2018 Update (1803) or earlier, managing Windows Server, version 1803 or Windows Server, version 1709: Download and install the WS_1803 RSAT package. This package is specifically designed for these earlier Windows 10 versions to manage the specified Windows Server releases.
-
For Windows 10 April 2018 Update (1803) or earlier, managing Windows Server 2016 or older versions: Opt for downloading and installing the WS2016 RSAT package. This ensures compatibility when your management tasks involve Windows Server 2016 or earlier iterations.
Troubleshooting Common RSAT Issues on Windows 10
While RSAT tools are essential, users may face certain issues during installation and usage. Here are common problems and their resolutions:
RSAT FOD Installation Errors in WSUS/SCCM Environments
Issue: RSAT FOD installation fails with error code 0x800f0954.
Impact: Occurs with RSAT FODs on Windows 10 1809 (October 2018 Update) within WSUS/SCCM managed environments.
Resolution: This is typically due to Group Policy settings. To resolve, adjust the Group Policy to allow downloading FODs directly from Windows Update or a designated local share. Microsoft’s documentation provides detailed steps on modifying this setting.
No Installation Progress Display in Settings App
Issue: RSAT FOD installation via the Settings app lacks status or progress indicators.
Impact: Affects RSAT FODs on Windows 10 1809 (October 2018 Update).
Resolution: To monitor the installation progress, simply navigate back to the “Manage optional features” page by clicking the “Back” button. The status will be displayed there.
RSAT FOD Uninstallation Failures
Issue: Uninstallation of RSAT FODs via the Settings app might fail.
Impact: RSAT FODs on Windows 10 1809 (October 2018 Update).
Resolution: Dependency conflicts often cause this. If RSAT tool A depends on tool B, uninstalling A will fail if B is still installed. Uninstall the dependent tool (B) first, and then attempt to uninstall tool A. Consult the RSAT FOD dependency list in Microsoft’s documentation for specifics.
RSAT Tools Persist After Uninstallation
Issue: RSAT FOD uninstallation seems successful, but the tools remain installed.
Impact: RSAT FODs on Windows 10 1809 (October 2018 Update).
Resolution: A system restart is usually required to finalize the removal process. Reboot your Windows 10 PC to complete the uninstallation.
RSAT Missing After Windows 10 Upgrade
Issue: RSAT is missing after a Windows 10 upgrade.
Impact: Any RSAT .MSU package installations (pre-FOD era) are not automatically reinstalled.
Resolution: RSAT .MSU packages, being delivered as Windows Updates, do not persist across OS upgrades. Reinstall RSAT after upgrading Windows 10. The shift to FODs in Windows 10 1809 and later addresses this, as RSAT FODs persist across upgrades.
Missing DNS Tools
Issue: DNS Tools are absent.
Impact: Users of the WS_1709 RSAT package.
Resolution: Migrate to RSAT FODs or utilize the WS_1803 or WS2016 RSAT packages. Alternatively, a specific workaround might be applicable as detailed in Microsoft Support article https://support.microsoft.com/en-us/help/4055558/rsat-missing-dns-server-tool-in-windows-10-version-1709.
Inability to Disable Individual RSAT Components
Issue: Cannot turn off individual RSAT components.
Impact: WS_1803 and WS_1709 RSAT package users on Windows 10 1803/1709.
Resolution: Upgrade to RSAT FODs for granular control over component selection. Alternatively, using the WS2016 RSAT package on Windows 10 1607 provides component control.
Missing Tabs in MMC Properties
Issue: Tabs are missing from MMC Properties.
Impact: Windows 10 clients older than 1607 (Anniversary Update).
Resolution: Upgrade to the latest Windows 10 version and reinstall RSAT to resolve this compatibility issue.
Shielding Data File Wizard Issues
Issue: Shielding Data File Wizard cannot create shielding data files.
Impact: WS_1709 RSAT package users on Windows 10 1709 (Fall Creators Update).
Resolution: Utilize RSAT FODs or the WS_1803 RSAT package on Windows 10 1803. The WS2016 RSAT package on Windows 10 1607 can also be used for Windows shielded VMs. Built-in RSAT tools in Windows Server, version 1709 can create files for both Windows and Linux shielded VMs.
Template Disks Created from Template Disk Wizard Fail to Boot
Issue: Template disks created with the Template Disk Wizard do not boot.
Impact: WS_1709 RSAT package users on Windows 10 1709 (Fall Creators Update).
Resolution: Similar to the Shielding Data File Wizard issue, use RSAT FODs, WS_1803 RSAT on Windows 10 1803, or WS2016 RSAT on Windows 10 1607. Windows Server, version 1709 built-in tools can create disks for both Windows and Linux shielded VMs.
IPAM Prompts for Installation in Server Manager Despite Being Installed
Issue: Server Manager’s IPAM prompts for installation even when already installed.
Impact: IPAM users on Windows 10 1803/1709.
Resolution: Use RSAT FODs or IPAM from an RSAT package installed on Windows 10 1607 or 1703 for a consistent experience.
Conclusion
Choosing the correct RSAT version for your Windows 10 and server environment is crucial for effective administration. By following these recommendations and troubleshooting steps, you can ensure a smooth and efficient server management experience. Always refer to the latest Microsoft documentation for the most up-to-date information and best practices regarding Windows Remote Server Administration Tools.
