Install RSAT tools on Windows 1809 with SCCM

After installing Windows 10 1809 I needed to reinstall the RSAT tools as the tools are removed every time you upgrade to a newer version of Windows. A quick search of Microsoft’s site yielded nothing! It turns out that starting with 1809, Microsoft is no longer providing the RSAT tools as a separate download. The tools can now be added as an optional feature in the Settings app under Apps and Features.

Unlike previous versions of RSAT where all of the tools were installed as one package, it is now possible to add individual tools. There is however one drawback to installing RSAT using the Settings GUI. You have to install the tools one by one. There is no way to select multiple features at one time.

Using PowerShell to install RSAT tools

PowerShell gives you an easier way to install all of the tools at one time or add the tools one at a time.

Get-WindowsCapability -Online | ? Name -like *RSAT*

The command above displays the available RSAT tools, and you can add them using Add-WindowsCapability.
If you want to install all RSAT tools not yet installed, you can use the following command.


Errors when using a WSUS Server

If you happen to be using your own WSUS server then chances are you will get an error trying to install RSAT via either the Settings app or when using the PowerShell command above.  The reason for this is that the RSAT tools are not included in the Windows 10 1809 installation media or via WSUS.  The tools still have to be downloaded from the internet but unlike previous versions, the tools are downloaded automatically by your machine instead of you downloading them manually from a website.

Currently, the RSAT tools do not seem to be available on WSUS so if you are using one locally you will see an error like the one below when attempting to install RSAT via PowerShell.  If you try via the Setting app the install will just stop after a short wait without any visible error.


Group Policy with the save

If you use WSUS you can allow your machine to get RSAT from Windows Update by modifying a setting in Group Policy. Create or edit the Group Policy of your choice and browse to Computer Configuration > Administrative Templates > System.  Now in the right windows click on “Specify settings for optional component installation and component repair“.

Enable this policy and select the checkbox Download repair content and optional features directly from Windows Update instead of WSUS.  Now run gpupdate /force and try to install RSAT again.  After updating the Group Policy option above the installation of RSAT should work.

Running the PowerShell command again should hopefully work and show output as in the picture below.

Installing RSAT with Configuration Manager

I have four different uses for the RSAT tools so I am going to create four different ways to install it with SCCM.

Method 1

For my first user, I only want to install Active Directory Users and Computers.

powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File RSAT1809.ps1 ADUC

Method 2

For my second user, I am going to install the most common set of tools. (AD DS, DHCP, DNS, Group Policy Management, and Server Manager)

powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File RSAT1809.ps1 Basic

Method 3

For the third user, I am just going to install ServerManager.

powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File RSAT1809.ps1 Servermanager

Method 4

For the fourth user, I am going to install the entire RSAT suite of tools.

powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File RSAT1809.ps1 All


To uninstall everything use the following.

powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File RSAT1809.ps1 Uninstall

I was going to write my own powershell script but I came across these two great scripts by Martin Bengtsson over on Technet and Kevin Street so I used some of their code and added a bunch of my own  You can download Martin Bengtsson’s script at and Kevin Street’s here

You can verify the tools have been installed by looking under Administrative Tools on the start menu.

Configuration Manager
Create a SCCM application and choose “Manually specify the deployment type information”. Once you get to the part asking for install and uninstall information use the following.  Make sure to use the appropriate parameter (ADUC, All, Basic, or ServerManager). I used All in the example below.


Installation program: powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File RSAT1809.ps1 All

Uninstall program: powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File RSAT1809.ps1 Uninstall

I assume you already know how to create a deployment based on a script.  I may post some pictures later.


This script creates different registry keys in HKLM\Software\RSAT1809 for you to use as detection methods. Each method creates its own key so if you have installed one feature such as “Servermanager” you would also be able to run the script again and install another set of features like “Basic”.  The uninstall method removes all features and all registry keys used for detection.

Error Messages

Error code = 0x800f0907

The above error is caused by the following GPO setting Specify settings for optional component installation and component repair under Computer/Administrative Templates/System. Make sure the setting Never attempt to download payload from Windows Update is set to Disabled (No CheckMark)

Error code = 0x800f0954

The above error is caused by the following GPO setting Specify settings for optional component installation and component repair under Computer/Administrative Templates/System. Make sure the setting Download repair content and option features directly from Windows Update instead of Windows Server Update Services (WSUS) is set to Enabled (CheckMark Selected)

Error code = 0x8024500c

If you enable the following policy you will end up with the above error.  Computer/Administrative Templates/Windows Updates/DoNotConnectToWindowsUpdateInternetLocations – Enabled

This setting shows up under the following registry setting.
HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\Servicing\DoNotConnectToWindowsUpdateInternetLocations – Enabled

About The Author

I have worked in the computer repair field since the early 90's. I was a technician and then Coordinator of Computer Repair for Regional Education Service Agency II (RESA 2) for 18 years. I am currently working for Wayne County Schools as a Network Engineer/Technology Specialist. I am responsible for the schools Internet access, Wi-Fi, networks, servers, laptops, desktops, and their operating systems and software.

Related posts


  1. Jimmy

    The “Download repair content and optional features directly from Windows Update instead of WSUS” Group Policy fix does not work on 1909

  2. Carl

    Jimmy, I disagree. At least in my case, flipping the GP setting has worked for me. Could there be other issues affecting yours?


Leave a Reply

Your email address will not be published. Required fields are marked *

fifty nine + = 63