Deploy RSAT (Remote Server Administration Tools) for Windows 10 v1909 with ConfigMgr and Powershell
Windows 10 v1909 was released to MSDN users and, a week True to tradition, I’m upgrading my Powershell script, helping you to set up RSAT for Windows 10 1909 automatically and unattended.
I obtained some feedback on my 1903 script, also thanks I made a few improvements. That includes:
Additional test for reboots. If reboot is pending, RSAT Features might not install successfully
Added test for setup of WSUS by Group Policy
History shows that if WSUS is configured by Group Policy Additional settings might be required for a few environments
Installing and enabling Remote Server Management Programs Using ConfigMgr 2007
It took me a while to find out something that is Very straightforward and logical… I couldn’t get different parts of the Remote Server Administration Tools (RSAT) enabled by command-line on Windows 7 x64… On Windows 7 x86 it’s pretty straight forward, as it can be carried out with the default option DISM commands. But on Windows 7 x64 it is hard to get it to use the proper version of DISM.
Because the ConfigMgr customer is, configMgrClientThis is If a 32-bit application wants to System32 and application, it is going to be redirected to%windir SysWOW64. I tried everything, actually defining the whole path to the DISM executable, but it didn’t matter… Until I finally figured out that there is just something called SysNative. WOW64 recognizes SysNative as a special alias used to indicate that the file system shouldn’t divert the access. Empower some attributes and I will post my answer here in order to set up RSAT as it had been kind of hard to discover this information. Here is the batch-file I ended up:
REM SET DISM Directory predicated on OS Architecture
REM SET RSAT Version based on OS Architecture
) ELSE (
REM RUN WUSA to install RSAT
REM RUN DISM to Allow features
%DISM% /online /enable-feature /featurename:RemoteServerAdministrationTools
Featurename:remote server AdministrationTools-Roles
REM EXIT Errorlevel
EXIT /b %errorlevel%
The factors were place by the very first part of the batch-file based on The architecture and the next part is going to do the actual installing and enabling (in the example it will permit the Hyper-V supervisor ). To conclude this story, follow the next five measures to set up and enable Remote Server Management Tools with ConfigMgr 2007:
Download the Entire installer(s ) ) of Remote Server 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 (Website hosting > Computer Management > Software Distribution > Packages) and point the Data Source into the place where the installer(s) as well as also the batch-file are.
Make a New App with the package that is newly created and use As command-line the name of the generated, batch document.
Create a new Ad of the program that is newly created and It is all ready to put in and enable!
The script needs rights as well as accessibility To the Internet (RSAT is set up via Microsoft Update).
The script is built around Get-WindowsCapability, Add-WindowsCapability and Remove-WindowsCapability.
Yet again the script includes 4 choices:
-All (-All is installing ALL the features within the RSAT bundle)
-Basic (-Basic is only installing AD DS, DHCP, DNS, Group
-ServerManager (-ServerManager is only installing the Server Manager)
-Uninstall (-Uninstall eliminates all RSAT features again)
Below an example of running the script -Basic parameter on Windows 10 1909
D another example of running the script using the -Uninstall parameter on Windows 10 1909
Notice the logging if WSUS Appears to be configured with Group Policy.
I’m putting the Powershell script to utilize an application in SCCM. I have included a few snippets of the application below, while this is pretty standard SCCM.
The installation program:
-NonInteractive -NoProfile -WindowStyle Hidden -File. \Install-RSATv1809v1903v1909. Ps1 -Fundamental
powershell.exe -ExecutionPolicy Bypass -NoLogo \Install-RSATv1809v1903v1909. ps1 -Uninstall