I would prefer to use a powershell detection script that actually checks for the module status for each module like this: Get-WindowsCapability -Online | Where-Object Name -like 'RSAT*' | Where-Object īut we need to have some user collection based deployments for RSAT, and when you deploy to a user collection, the detection script runs in the context of the logged in user. However, depending on which modules get installed this may or may not be true for a particular install. I'd previously used a detection method for one of the actual deliverable of RSAT, "%Windir%\System32\ServerManager.exe" being present. Most of the time it works fine, but on some machines only some of the modules install.
#INSTALL RSAT TOOLS WINDOWS 10 1809 POWERSHELL USING SCCM INSTALL#
We've been having some issues with our RSAT install on Win 10 (1809+ using the optional feature based installations).
But starting with Windows 10 v.1809 (and newer), Microsoft has introduced a new. Since the tools are version-specific, they’d get uninstalled twice a year when your machine downloaded a Feature Update and upgraded to the latest version of Windows 10. As a general rule, if someone has flair, they almost definitely know what they're talking about. In the past, utilizing RSAT would mean downloading the install files from Microsoft’s site. Microsoft employees typically have MSFT Official flair, and MVPs usually have MSFT Enterprise Mobility MVP with a link to their personal site/blog.Please send mod mail if you qualify and would like flair set for your account. Flair is reserved for Microsoft employees and MVPs.System Center Configuration Manager and Endpoint Protection.Listing of Local ConfigMgr-related User Groups (largely outdated) URL shorteners cause this almost every time, but so do strings of apparent gibberish like WSUS and PXE sometimes.
It might have been caught by the spam filter. Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up?