Deploy RSAT (Remote Server Management Applications ) for Windows 10 v1909 with ConfigMgr and Powershell
Was released to MSDN users a week, and True to convention, I am upgrading my Powershell script, so helping you to set up RSAT for Windows 10 1909 and unattended.
I obtained some feedback in my 1903 script, also thanks I made a few improvements. That includes:
Added test for impending reboots. RSAT, if reboot is pending Features might not install successfully
Added test for setup of WSUS by Group Policy
History shows that, if Group Policy configures WSUS Additional settings might be required for a few surroundings
Installing and empowering remote server Administration Tools With ConfigMgr 2007
It took me a while to figure out something that is Very simple and logical… I couldn’t get different areas of the Remote Server Administration Tools (RSAT) enabled by command-line onto Windows 7 x64… On Windows 7 x86 it’s pretty straight forward, since it could be carried out with the default option DISM commands. But on Windows 7 x64 it is kind of difficult to get it to use the version of DISM.
ConfigMgrClientThis is because the ConfigMgr client is If a 32-bit application wishes to access% windir% \ System32 and 32-bit application, it will be redirected to%windir SysWOW64. I tried everything, even defining the whole path to the DISM executable, but it all didn’t matter… Until I eventually figured out that there is just something named SysNative. WOW64 recognizes SysNative as a special alias used to indicate the file system should not redirect the accessibility. Enable some attributes and I will post my answer here to install RSAT as it had been kind of hard to discover this info. Here really is the batch-file I ended up:
REM SET DISM Directory based on OS Architecture
REM SET RSAT Version predicated on OS Architecture
IF EXIST %WINDIR%\SysNative\dism.exe (
) ELSE (
RSAT to be installed by REM RUN WUSA
Features to be enabled by REM RUN DISM
Percent DISM% /online /enable-feature /featurename:RemoteServerAdministrationTools
REM EXIT Errorlevel
The factors were place by the very first part of the batch-file based on The architecture and the next part will do the actual installing and enabling (in the case it will enable the Hyper-V supervisor ).
Download the Entire installer(s ) ) of Remote Server Administration Tools (amd64fre_GRMRSATX_MSU. Msu and/ or x86fre_GRMRSAT_MSU. msu) here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en.
Copy the code above and create a batch-file.
Create a new Package in ConfigMgr 2007 (Site Database > Computer Management > Software Distribution > Packages) and stage the Data Source into the place where the installer(s) as well as the batch-file are.
Make a New App with the package and use As the title of the batch document.
Make a New Ad of the recently created program and It is all ready to put in and enable!
The script needs rights in Addition to accessibility To the Internet (RSAT is set up via Microsoft Update).
The script is built around Get-WindowsCapability, Add-WindowsCapability and Remove-WindowsCapability.
Yet the script comes with 4 choices:
-All (-All is installing ALL the features within the RSAT bundle)
-ServerManager (-ServerManager Is Simply installing the Server Manager)
-Uninstall (-Uninstall eliminates all RSAT features again)
Below an example of running the script using the
D of running the script with the another instance
Notice the additional logging if WSUS Appears to be configured with Group Policy.
I am placing the Powershell script to use with an application in SCCM. I’ve included a couple snippets of this application below, while this is fairly SCCM.
The installation program:
powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File. \Install-RSATv1809v1903v1909. Ps1 -Fundamental
The uninstall program:
-NonInteractive -NoProfile -WindowStyle Hidden -Document. \Install-RSATv1809v1903v1909. ps1 -Uninstall